From: Andy Dougherty Date: Thu, 20 Nov 2003 09:38:05 +0000 (-0500) Subject: Re: [perl #24439] 64 bit build failure on Solaris 9 X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=commitdiff_plain;h=0ceffaa6d1b6322a2acc72496461c007b2bc1d17;p=p5sagit%2Fp5-mst-13.2.git Re: [perl #24439] 64 bit build failure on Solaris 9 Date: Thu, 20 Nov 2003 09:38:05 -0500 (EST) Message-ID: and : Date: Fri, 21 Nov 2003 09:36:24 -0500 (EST) Message-ID: p4raw-id: //depot/perl@21780 --- diff --git a/hints/solaris_2.sh b/hints/solaris_2.sh index d1c1a06..7ffc53c 100644 --- a/hints/solaris_2.sh +++ b/hints/solaris_2.sh @@ -513,14 +513,13 @@ EOM loclibpth="/usr/lib/sparcv9 $loclibpth" ccflags="$ccflags -mcpu=v9 -m64" if test X`getconf XBS5_LP64_OFF64_CFLAGS 2>/dev/null` != X; then + # This adds in -Wa,-xarch=v9. I suspect that's superfluous, + # since the -m64 above should do that already. Someone + # with gcc-3.x.x, please test with gcc -v. A.D. 20-Nov-2003 ccflags="$ccflags -Wa,`getconf XBS5_LP64_OFF64_CFLAGS 2>/dev/null`" fi - # no changes to ld flags, as (according to man ld): - # - # There is no specific option that tells ld to link 64-bit - # objects; the class of the first object that gets processed - # by ld determines whether it is to perform a 32-bit or a - # 64-bit link edit. + ldflags="$ldflags -m64" + lddlflags="$lddlflags -G -m64" ;; *) ccflags="$ccflags `getconf XBS5_LP64_OFF64_CFLAGS 2>/dev/null`"