pastebin - collaborative debugging tool
nrubsig.kpaste.net RSS


nfstest_gcc_build.ksh93
Posted by Anonymous on Tue 6th Feb 2024 12:36
raw | new post
view followups (newest first): nfstest_gcc_build.ksh93 by Anonymous
modification of post by Anonymous (view diff)

  1.  
  2. #!/usr/bin/ksh93
  3.  
  4. #
  5. # nfstest_gcc_build.ksh93
  6. #
  7. # Simple NFSv4 torture test by building gcc in parallel
  8. # on a NFS filesystem
  9. #
  10. set -o xtrace
  11. set -o errexit
  12.  
  13. #
  14. # source checkout
  15. #
  16.  
  17. #git -c checkout.workers=8 clone -b 'releases/gcc-13.2.0' git://gcc.gnu.org/git/gcc.git
  18. git -c checkout.workers=8 clone -b 'releases/gcc-13.2.0' https://github.com/gcc-mirror/gcc.git
  19.  
  20. cd $PWD/gcc/ || { sync ; sleep 5 ; cd gcc ; }
  21.  
  22. PATH="/usr/ast/bin:/opt/ast/bin:$PATH"
  23.  
  24. #
  25. # patch sources and configure build
  26. #
  27.  
  28. # Cygwin: workaround for configure using cp -p where ln -s should be used
  29. # (this is an automake/autoconf issue, they should trust Cygwin and not use
  30. # ancient workarounds for issues which no longer exists)
  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) )
  32. ksh93 ./configure
  33. # workaround for $ cp -p # failing with "Function not implemented"
  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) )
  35.  
  36. #
  37. # build gcc
  38. #
  39. ksh93 -c 'export SHELL=/bin/ksh93 ; (yes | make -j16 all)'
  40. echo $?
  41.  
  42. echo "#Done."

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