From: Jarkko Hietaniemi <jhi@iki.fi>
Date: Sun, 8 Jan 2006 11:38:34 +0000 (+0200)
Subject: hints/dec_osf.sh (Re: blead@26701 compilation warning from tru64 cc)
X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=commitdiff_plain;h=b6c2855378a705b6278bd4e260febb2b484b9fcd;p=p5sagit%2Fp5-mst-13.2.git

hints/dec_osf.sh (Re: blead@26701 compilation warning from tru64 cc)
Message-ID: <43C0DD9A.9080809@gmail.com>

p4raw-id: //depot/perl@26707
---

diff --git a/hints/dec_osf.sh b/hints/dec_osf.sh
index fbdf624..2a2bf61 100644
--- a/hints/dec_osf.sh
+++ b/hints/dec_osf.sh
@@ -126,17 +126,23 @@ EOF
 	# If it is, we can use it for being nauseatingly C99 ANSI --
 	# but even then the lddlflags needs to stay -std1.
 	# If it is not, we must use -std1 for both flags.
+	#
        	case "`cc -c99 try.c 2>&1`" in
-	*"-c99: Unknown flag"*)		_ccflags_strict_ansi="-std1"  ;;
+	*"-c99: Unknown flag"*)
+		_ccflags_strict_ansi="-std1"
+		;;
 	*)	# However, use the -c99 only if compiling for
 		# -DPERL_MEM_LOG, where the C99 feature __func__
 		# is useful to have.  Otherwise use the good old
 		# -std1 so that we stay C89 strict, which the goal
 		# of the Perl C code base (no //, no code between
-		# declarations, etc).
+		# declarations, etc).  Moreover, the Tru64 cc is
+		# not fully C99, and most probably never will be.
+		#
 		# The -DPERL_MEM_LOG can be either in ccflags
 		# (if using an old config.sh) or in the command line
 		# (which has been stowed away in UU/cmdline.opt).
+		#
 		case "$ccflags `cat UU/cmdline.opt`" in
 		*-DPERL_MEM_LOG*)	_ccflags_strict_ansi="-c99"  ;;
 		*)			_ccflags_strict_ansi="-std1" ;;
@@ -144,6 +150,9 @@ EOF
 		;;
 	esac
 	_lddlflags_strict_ansi="-std1"
+	# -no_ansi_alias because Perl code is not that strict
+	# (also gcc uses by default -fno-strict-aliasing).
+	_ccflags_strict_ansi="$_ccflags_strict_ansi -no_ansi_alias"
 	# Cleanup.
 	rm -f try.c try.o
 	;;