From: ross.alexander@uk.neceur.com
To: "John David Anglin" <dave@hiauly1.hia.nrc.ca>
Cc: aoliva@redhat.com, binutils@sources.redhat.com,
binutils-owner@sources.redhat.com, gcc-patches@gcc.gnu.org,
sje@cup.hp.com, libtool@sources.redhat.com
Subject: Re: Add hppa*64* support to libtool in binutils
Date: Mon, 29 Jul 2002 04:17:00 -0000 [thread overview]
Message-ID: <OFA15CDC33.853DE7E3-ON80256C05.0038EA84@uk.neceur.com> (raw)
David,
I'm currently looking at revising libtool-1.4e to add HPUX64 support. I've
got a
couple of questions.
1) Should the mode be determined from $cpu_host or by checking __LP64__
in the cc defines. Given that the config.guess returns
hppa2.0w-hp-hpux??.??
and we assume that is 32bit then do we assume the user knows what they
are doing and assume they only want 64bit when the target is hpux64.
Should
libtool check that they match correctly.
I'll use the values you used in your patch. I assume these are pretty much
the default values for ELF environments. Any hints would be appreciated.
Many thanks
Ross
---------------------------------------------------------------------------------
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"
next reply other threads:[~2002-07-29 10:58 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-29 4:17 ross.alexander [this message]
2002-07-29 14:07 ` John David Anglin
2002-08-12 10:46 ` Jeff Law
-- strict thread matches above, loose matches on Subject: below --
2002-08-13 8:54 ross.alexander
2002-08-13 9:40 ` John David Anglin
2002-08-13 10:42 ` Jeff Law
2002-08-13 11:39 ` John David Anglin
2002-08-14 8:09 ` Jeff Law
2002-08-14 10:52 ` John David Anglin
2002-08-13 13:07 ` John David Anglin
2002-07-15 9:51 Steve Ellcey
2002-07-15 10:25 ` John David Anglin
2002-07-15 19:28 ` Loren James Rittle
2002-07-10 14:40 Steve Ellcey
2002-07-10 15:22 ` John David Anglin
2002-07-09 11:16 John David Anglin
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=OFA15CDC33.853DE7E3-ON80256C05.0038EA84@uk.neceur.com \
--to=ross.alexander@uk.neceur.com \
--cc=aoliva@redhat.com \
--cc=binutils-owner@sources.redhat.com \
--cc=binutils@sources.redhat.com \
--cc=dave@hiauly1.hia.nrc.ca \
--cc=gcc-patches@gcc.gnu.org \
--cc=libtool@sources.redhat.com \
--cc=sje@cup.hp.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).