From: Jack Cummings <jack@needle.mudshark.org>
To: Alexandre Oliva <aoliva@redhat.com>
Cc: gcc-help@gcc.gnu.org
Subject: Re: hppa64-hp-hpux11.00
Date: Wed, 05 Sep 2001 00:10:00 -0000 [thread overview]
Message-ID: <20010905000828.A855@needle.mudshark.org> (raw)
In-Reply-To: <or1ylm4jo9.fsf@localhost.localdomain>
On Tue, Sep 04, 2001 at 08:31:50PM -0300, Alexandre Oliva wrote:
> > I take it binutils-2.11.2 doesn't cut it? Which version should I be using?
> Perhaps the CVS version of binutils? That's what Markus Werle used to
> get a 64-bit GCC on HP-UX 11.00, in a recent message sent to
> gcc-help.
I got it to work with the HPUX ld. Is there any problems with me posting
binaries, to save others the tedium of building a cross compiler?
--Jack
--
John ( Jack ) Cummings http://mudshark.org/jack
Key fingerprint: 945A 89EB CA2D 6D93 7F15 5C97 1028 194E 5E7A 62DD
next prev parent reply other threads:[~2001-09-05 0:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-30 18:02 hppa64-hp-hpux11.00 Jack Cummings
2001-09-04 19:25 ` hppa64-hp-hpux11.00 Alexandre Oliva
2001-09-05 0:10 ` Jack Cummings [this message]
2001-09-05 0:44 ` hppa64-hp-hpux11.00 Alexandre Oliva
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=20010905000828.A855@needle.mudshark.org \
--to=jack@needle.mudshark.org \
--cc=aoliva@redhat.com \
--cc=gcc-help@gcc.gnu.org \
/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).