pastebin - collaborative debugging tool
nrubsig.kpaste.net RSS

Difference between
modified post 45d757f64d by Anonymous on Tue 6th Feb 2024 12:36
original post de436 by Anonymous on Tue 6th Feb 2024 11:35
Download diff
Show old version | new version | both versions

    
1-
#!/usr/bin/ksh93
21
2+
#!/usr/bin/ksh93
53
6-
#git clone -b 'releases/gcc-13.2.0' -c checkout.workers=8 git://gcc.gnu.org/git/gcc.git
4+
#
7-
git clone -b 'releases/gcc-13.2.0' -c checkout.workers=8 https://github.com/gcc-mirror/gcc.git
5+
# nfstest_gcc_build.ksh93
6+
#
812
13+
#
1016
17+
#git -c checkout.workers=8 clone -b 'releases/gcc-13.2.0' git://gcc.gnu.org/git/gcc.git
1219
20+
cd $PWD/gcc/ || { sync ; sleep 5 ; cd gcc ; }
2021
21-
ksh93 -c 'export SHELL=/bin/ksh93 ; (yes | make -j24 all)'
22+
PATH="/usr/ast/bin:/opt/ast/bin:$PATH"
2423
25-
24+
#
26-
25+
# patch sources and configure build
27-
26+
#
2827
29-
28+
# Cygwin: workaround for configure using cp -p where ln -s should be used
30-
29+
# (this is an automake/autoconf issue, they should trust Cygwin and not use
31-
30+
# ancient workarounds for issues which no longer exists)
32-
31+
(set -o xtrace ; sed -i "s/as_ln_s='cp -pR'/as_ln_s='ln -s'/g;s/\/bin\/sh/\/bin\/ksh93/g" $(find . -name configure) )
33-
32+
ksh93 ./configure
34-
33+
# workaround for $ cp -p # failing with "Function not implemented"
35-
34+
(set -o xtrace ; sed -i -r 's/(cp.*)([[:space:]]+-p[[:space:]]+)/\1\2 -A pt /g;s/\/bin\/sh/\/bin\/ksh93/g' $(find . -name Makefile -o -name Makefile.in) )
3635
37-
36+
#
38-
37+
# build gcc
39-
38+
#
40-
39+
ksh93 -c 'export SHELL=/bin/ksh93 ; (yes | make -j16 all)'
41-
40+
echo $?
4241
43-
42+
echo "#Done."
4443

Submit a correction or amendment below (click here to make a fresh posting)
After submitting an amendment, you'll be able to view the differences between the old and new posts easily.

Syntax highlighting:

To highlight particular lines, prefix each line with {%HIGHLIGHT}




All content is user-submitted.
The administrators of this site (kpaste.net) are not responsible for their content.
Abuse reports should be emailed to us at