From: frankj@open-it.com
To: John David Anglin <dave@hiauly1.hia.nrc.ca>
Cc: gcc@gcc.gnu.org, borgar@osc.no
Subject: Re: Successfull gcc-3.4.4 build on hppa1.1-hp-hpux10.20
Date: Thu, 01 Sep 2005 05:47:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.63.0509010742520.10817@localhost.localdomain> (raw)
In-Reply-To: <200509010237.j812bJjX003470@hiauly1.hia.nrc.ca>
On Wed, 31 Aug 2005, John David Anglin wrote:
>> Used full distribution + make bootstrap. Used egcs-2.91.57 and binutils-2.11.2 to compile gcc.
>
> If you are interested in much improved C++ support, upgrade binutils to
> 2.16 or later and rebuild GCC with the new binutils. This provides
> one-only support under HP-UX 10.20. You also need the latest (last)
> HP linker patch for 10.20.
Thanks! Do you know if this includes pthreads support in C++?
-Frank.
next prev parent reply other threads:[~2005-09-01 5:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-01 2:37 John David Anglin
2005-09-01 5:47 ` frankj [this message]
2005-09-01 13:23 ` John David Anglin
-- strict thread matches above, loose matches on Subject: below --
2005-08-04 6:56 frankj
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=Pine.LNX.4.63.0509010742520.10817@localhost.localdomain \
--to=frankj@open-it.com \
--cc=borgar@osc.no \
--cc=dave@hiauly1.hia.nrc.ca \
--cc=gcc@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).