Closed p5pRT closed 13 years ago
This bug report is for Building/Configuring Perl 5.8.0 on HPUX 11.00.
Using
Configure -s -Duselargefiles -Dusethreads -Duse64bitint
Seems to add +DD64 to the cflags in the configure process\, attempting to create LP64 a.out's. These don't execute under 32bit HPUX 11.00\, and I don't want an LP64 perl.
I've been looking at hpux's hints file and haven't figured out yet what is specifically triggering that flag to be added. Without -Duse64bitint\, it seems to behave ok.
On Thu 03 Oct 2002 19:18\, "Richard J. Rauenzahn" (via RT) \perlbug@​perl\.org wrote:
This bug report is for Building/Configuring Perl 5.8.0 on HPUX 11.00.
Using
Configure \-s \-Duselargefiles \-Dusethreads \-Duse64bitint
Seems to add +DD64 to the cflags in the configure process\, attempting to create LP64 a.out's. These don't execute under 32bit HPUX 11.00\, and I don't want an LP64 perl.
This is inherent to the way HP-UX compilers work. The coice is to go either all the way - and use 64bitall - (something that the hint file promotes your use64bitint flag to)\, or 32bit. This is the same reason why you need two different gcc compilers for 32bit and 64bit.
I've been looking at hpux's hints file and haven't figured out yet what is specifically triggering that flag to be added. Without -Duse64bitint\, it seems to behave ok.
Didn't it give a warning?
It's here:
--8\<--- hints/hpux.sh
156 ### 64 BITNESS
157
158 # Some gcc versions do native 64 bit long (e.g. 2.9-hppa-000310 and gcc-3.0)
159 # We have to force 64bitness to go search the right libraries
160 gcc_64native=no
161 case "$ccisgcc" in
162 $define|true|[Yy])
163 echo 'int main(){long l;printf("%d\\n"\,sizeof(l));}'>try.c
164 $cc -o try $ccflags $ldflags try.c
165 if [ "`try`" = "8" ]; then
166 cat \<\
-- H.Merijn Brand Amsterdam Perl Mongers (http://amsterdam.pm.org/) using perl-5.6.1\, 5.8.0 & 633 on HP-UX 10.20 & 11.00\, AIX 4.2\, AIX 4.3\, WinNT 4\, Win2K pro & WinCE 2.11. Smoking perl CORE: smokers@perl.org http://archives.develooper.com/daily-build@perl.org/ perl-qa@perl.org send smoke reports to: smokers-reports@perl.org\, QA: http://qa.perl.org
On Fri\, Oct 04\, 2002 at 08:09:00AM -0000\, H.Merijn Brand (via RT) wrote:
On Thu 03 Oct 2002 19:18\, "Richard J. Rauenzahn" (via RT) \perlbug@​perl\.org wrote:
This bug report is for Building/Configuring Perl 5.8.0 on HPUX 11.00.
Using
Configure \-s \-Duselargefiles \-Dusethreads \-Duse64bitint
Seems to add +DD64 to the cflags in the configure process\, attempting to create LP64 a.out's. These don't execute under 32bit HPUX 11.00\, and I don't want an LP64 perl.
This is inherent to the way HP-UX compilers work. The coice is to go either all the way - and use 64bitall - (something that the hint file promotes your use64bitint flag to)\, or 32bit. This is the same reason why you need two different gcc compilers for 32bit and 64bit.
Umm... no\, I don't think so. Unless you only mean gcc\, which I'm not as familiar with.
HP's ANSI-C compiler has an -Ae option to add a 'long long' datatype which is 64bits. +DD64 turns the a.out into LP64. You don't have to be LP64 to have the 'long long' type enabled. That's what I was trying to accomplish.
I've been looking at hpux's hints file and haven't figured out yet what is specifically triggering that flag to be added. Without -Duse64bitint\, it seems to behave ok.
Didn't it give a warning?
During Configure? I got some errors about 'try' not working\, which was because it was trying to do a +DD64 try\, which won't run on my 32bit 11.00 install.
It's here: --8\<--- hints/hpux.sh
Yeah\, I read it -- it just didn't make sense to me. And I'm not using gcc. The comments seemed only to apply to gcc.
156 ### 64 BITNESS [...]
Rich
Patch available here: http://perl5.git.perl.org/perl.git/ commit/50cf7679884399fed31c7f7db3f8e3093b1008d9
patches are available and committed as
http://perl5.git.perl.org/perl.git/ commit/064b70ffe2beced36b4693cdd2a8e2cbd2139b47 http://perl5.git.perl.org/perl.git/commit/ fd8c3383aea40326a20c5e582ecf50ee7d7bfcb9
@tux - Status changed from 'open' to 'resolved'
Migrated from rt.perl.org#17736 (status was 'resolved')
Searchable as RT17736$