From: "John David Anglin" <dave@hiauly1.hia.nrc.ca>
To: sje@cup.hp.com (Steve Ellcey)
Cc: aoliva@redhat.com, rittle@labs.mot.com,
binutils@sources.redhat.com, gcc-patches@gcc.gnu.org
Subject: Re: Add hppa*64* support to libtool in binutils
Date: Mon, 15 Jul 2002 10:25:00 -0000 [thread overview]
Message-ID: <200207151655.g6FGtWln024676@hiauly1.hia.nrc.ca> (raw)
In-Reply-To: <200207151615.JAA16249@hpsje.cup.hp.com> from "Steve Ellcey" at Jul 15, 2002 09:15:43 am
> > This is a first cut at adding hppa64 support to libtool in binutils.
> > The same needs to done in gcc and in the libtool source. Unfortunately,
> > the binutils and gcc sources are somewhat out of sync, so it seems
> > separate patches will be needed in each case.
>
> David, I verified that if my GCC libtool patch
> (http://gcc.gnu.org/ml/gcc-patches/2002-07/msg00527.html) is applied to
> GCC then your binutils patch
> (http://gcc.gnu.org/ml/gcc-patches/2002-07/msg00397.html) can be applied
> to GCC with out any changes. I put both patches to my local tree
> (binutils and GCC) over the weekend and tested on PA32, PA64, and IA64
> HP-UX and had no problems. This would leave Loren Rittle's GCC libtool
Thanks for for testing this.
Dave
--
J. David Anglin dave.anglin@nrc.ca
National Research Council of Canada (613) 990-0752 (FAX: 952-6605)
next prev parent reply other threads:[~2002-07-15 16:58 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-15 9:51 Steve Ellcey
2002-07-15 10:25 ` John David Anglin [this message]
2002-07-15 19:28 ` Loren James Rittle
-- 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-29 4:17 ross.alexander
2002-07-29 14:07 ` John David Anglin
2002-08-12 10:46 ` Jeff Law
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=200207151655.g6FGtWln024676@hiauly1.hia.nrc.ca \
--to=dave@hiauly1.hia.nrc.ca \
--cc=aoliva@redhat.com \
--cc=binutils@sources.redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=rittle@labs.mot.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).