diff options
| author | Ken Raeburn <raeburn@cygnus> | 1993-10-08 21:27:13 +0000 |
|---|---|---|
| committer | Ken Raeburn <raeburn@cygnus> | 1993-10-08 21:27:13 +0000 |
| commit | 5357f1287d574310c08a9e54e8b903f9571d4129 (patch) | |
| tree | e08ae8ad1649dadce6f8c2000c4e6e39c5918b2f /.Sanitize | |
| parent | a8c789c4b87accd2eba1f9c3644066656212e3d5 (diff) | |
| download | fsf-binutils-gdb-5357f1287d574310c08a9e54e8b903f9571d4129.zip fsf-binutils-gdb-5357f1287d574310c08a9e54e8b903f9571d4129.tar.gz fsf-binutils-gdb-5357f1287d574310c08a9e54e8b903f9571d4129.tar.bz2 | |
configure.in: Put {start,end}-sanitize-for-fsf around code that removes some
programs based on host or target; this silent failure to configure isn't
appropriate for the separate one-tool releases FSF puts out.
.Sanitize: Remove that code if "for-fsf" is on command line; remove just the
markers if it isn't.
Diffstat (limited to '.Sanitize')
| -rw-r--r-- | .Sanitize | 26 |
1 files changed, 26 insertions, 0 deletions
@@ -179,6 +179,32 @@ else done fi +if ( echo $* | grep for\-fsf > /dev/null ) ; then + if [ -n "${verbose}" ]; then + echo Cleaning up configure.in for FSF release... + fi + sed '/start\-sanitize\-for\-fsf/,/end\-sanitize\-for\-fsf/d' < configure.in > new + if [ -n "${safe}" -a ! -f .Recover/$i ]; then + if [ -n "${verbose}" ]; then + echo Caching configure.in in .Recover... + fi + mv configure.in .Recover + fi + mv new configure.in +else + if [ -n "${verbose}" ]; then + echo Removing sanitize-for-fsf markers from configure.in... + fi + grep -v sanitize-for-fsf < configure.in > new + if [ -n "${safe}" ]; then + if [ -n "${verbose}" ]; then + echo Caching configure.in in .Recover... + fi + mv configure.in .Recover + fi + mv new configure.in +fi + for i in * ; do if test ! -d $i && (grep sanitize $i > /dev/null) ; then echo '***' Some mentions of Sanitize are still left in $i! 1>&2 |