This is the mail archive of the
binutils@sources.redhat.com
mailing list for the binutils project.
Re: Patch to config.guess (2002-07-03) to detect 64bit HPUX compiler
- From: ross dot alexander at uk dot neceur dot com
- To: Ben Elliston <bje at redhat dot com>
- Cc: binutils at sources dot redhat dot com, "John David Anglin" <dave at hiauly1 dot hia dot nrc dot ca>, Albert Chin <binutils at lists dot thewrittenword dot com>, Jeff Law <law at porcupine dot slc dot redhat dot com>
- Date: Wed, 21 Aug 2002 13:08:19 +0100
- Subject: Re: Patch to config.guess (2002-07-03) to detect 64bit HPUX compiler
Ben,
There is currently a philosophical problem with hppa*64* at the moment.
At the moment, HPUX has three possible versions for PA2.0 capable
systems, that is hppa2.0, hppa2.0n and hppa2.0w. Now hppa2.0 == hppa2.0n
but hppa2.0w indicates the OS can *execute* 64bit code. This has nothing
to do with the current build environment. Now the 2.0N vs 2.0W comes from
both the .level in PA assembly and more importantly the architecture flags
in cc (ie CC +DA2.0N vs CC +DA2.0W). However, to go back and stay hppa2.0w
== 64 build
environment rather than hppa2.0w == 64 capable OS may potentially break a
very large amount of code, and it would have to cleared though the gcc and
binutils groups.
How about the following (example)
cpu_host=`if echo "__LP64__" | $CC -E - | grep -q __LP64__; then echo
hppa2.0n; else echo hppa2.0w; fi`
---------------------------------------------------------------------------------
Ross Alexander "He knows no more about his
MIS - NEC Europe Limited destiny than a tea leaf knows
Work ph: +44 20 8752 3394 the history of East India Company"
Ben Elliston
<bje@redhat.com> To: ross.alexander@uk.neceur.com
cc:
20/08/2002 22:04 Subject: Re: Patch to config.guess (2002-07-03) to detect 64bit HPUX compiler
>>>>> "ross" == ross alexander <ross.alexander@uk.neceur.com> writes:
ross> Config.guess will return hppa64-hp-hpux??.?? if $CC produces
ross> 64bit output, ie 64bit gcc or CC +DA2.0W.
ross> (See attached file: config.guess.diff)
I am really resisting patches that use the nasty inline shell fragment
`$set_cc_for_build'. It is a constant source of frustrations. I am
loathe to use it more -- is there any way you can use other system
facilities to discover the same information?
If you look at some of the Linux detection code, there are some nice
tricks there that employ pipelines through cpp, if that's what you
need.
Ben