Document PTR2XX and INT2PTR.

[p5sagit/p5-mst-13.2.git] / hints / dec_osf.sh

diff --git a/hints/dec_osf.sh b/hints/dec_osf.sh
index 31b0513..c110d1e 100644 (file)
--- a/hints/dec_osf.sh
+++ b/hints/dec_osf.sh
@@ -67,28 +67,36 @@ cc=${cc:-cc}
 case "`$cc -v 2>&1 | grep cc`" in
 *gcc*) _gcc_version=`$cc --version 2>&1 | tr . ' '`
        set $_gcc_version
-       if test "$1" -lt 2 -o \( "$1" -eq 2 -a "$2" -lt 95 \); then
+       if test "$1" -lt 2 -o \( "$1" -eq 2 -a \( "$2" -lt 95 -o \( "$2" -eq 95 -a "$3" -lt 2 \) \) \); then
            cat >&4 <<EOF
 
-Your cc seems to be gcc and its version seems to be less than 2.95.
-This is not a good idea since old versions of gcc are known to produce
-buggy code when compiling Perl (and no doubt for other programs, too).
-
-Therefore, I strongly suggest upgrading your gcc.  (Why don't you
-use the vendor cc is also a good question.  It comes with the operating
-system and produces good code.)
-
-Note that as of gcc 2.95 (19990728) and Perl 5.6.0 (end of March 2000)
-if the said Perl is compiled with the said gcc the lib/sdbm test will 
-dump core.  As this doesn't happen with the vendor cc, this is
-most probably a lingering bug in gcc.  Therefore unless you have
-a better gcc you are still better off using the vendor cc.
+*** Your cc seems to be gcc and its version seems to be less than 2.95.2.
+*** This is not a good idea since old versions of gcc are known to produce
+*** buggy code when compiling Perl (and no doubt for other programs, too).
+***
+*** Therefore, I strongly suggest upgrading your gcc.  (Why don't you
+*** use the vendor cc is also a good question.  It comes with the operating
+*** system and produces good code.)
 
 Cannot continue, aborting.
 
 EOF
            exit 1
        fi
+       if test "$1" -eq 2 -a "$2" -eq 95 -a "$3" -le 2; then
+           cat >&4 <<EOF
+
+*** Note that as of gcc 2.95.2 (19991024) and Perl 5.6.0 (March 2000)
+*** if the said Perl is compiled with the said gcc the lib/sdbm test
+*** dumps core (meaning  that the SDBM_File is unusable).  As this core
+*** dump doesn't happen with the vendor cc, this is most probably
+*** a lingering bug in gcc.  Therefore unless you have a better gcc
+*** you are still better off using the vendor cc.
+
+Since you explicitly chose gcc, I assume that you know what are doing.
+
+EOF
+       fi
         ;;
 *)     # compile something small: taint.c is fine for this.
        # the main point is the '-v' flag of 'cc'.