From: ross.alexander@uk.neceur.com
To: Ben Elliston <bje@redhat.com>
Cc: binutils@sources.redhat.com,
"John David Anglin" <dave@hiauly1.hia.nrc.ca>,
Albert Chin <binutils@lists.thewrittenword.com>,
Jeff Law <law@porcupine.slc.redhat.com>
Subject: Re: Patch to config.guess (2002-07-03) to detect 64bit HPUX compiler
Date: Wed, 21 Aug 2002 05:09:00 -0000 [thread overview]
Message-ID: <OFF1BAA8AD.1A891EB1-ON80256C1C.0039A956@uk.neceur.com> (raw)
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
next reply other threads:[~2002-08-21 12:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-21 5:09 ross.alexander [this message]
2002-08-21 8:58 ` John David Anglin
2002-08-23 2:40 ross.alexander
2002-08-23 14:29 ` John David Anglin
2002-11-29 22:05 ` Ben Elliston
2002-12-03 7:50 ` John David Anglin
[not found] <no.id>
2002-12-03 8:31 ` John David Anglin
2002-12-03 16:51 ` John David Anglin
2002-12-04 1:53 ` Ben Elliston
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=OFF1BAA8AD.1A891EB1-ON80256C1C.0039A956@uk.neceur.com \
--to=ross.alexander@uk.neceur.com \
--cc=binutils@lists.thewrittenword.com \
--cc=binutils@sources.redhat.com \
--cc=bje@redhat.com \
--cc=dave@hiauly1.hia.nrc.ca \
--cc=law@porcupine.slc.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).