From: Brian Ford <ford@vss.fsi.com>
To: erik.de.smet@philips.com
Cc: gcc@gcc.gnu.org
Subject: Re: gcc for HP-UX 11.00
Date: Thu, 30 Sep 1999 18:02:00 -0000 [thread overview]
Message-ID: <Pine.GSO.4.10.9909100953150.20727-100000@eos> (raw)
Message-ID: <19990930180200.3wQ12Yw4K-4DItBPgJJBW_B_O1VyD7iHLe8_qWmQ9lQ@z> (raw)
In-Reply-To: <0056900003783163000002L032*@MHS>
On Fri, 10 Sep 1999 erik.de.smet@philips.com wrote:
> Now I need the source code for gcc2.8.1, but I only find these for 10.20.
>
> Is gcc2.8.1 available for 11.X ?
>
I don't know for sure, but I do not think so. I would suggest gcc 2.95.1
since it has many bug fixes from 2.8.1 and it says on:
http://egcs.cygnus.com/gcc-2.95/buildstat.html
that its build status is:
hppa2.0-hp-hpux11.00
Successful
hppa2.0w-hp-hpux11.00
Successful
Good luck.
--
Brian Ford
Software Engineer
Vital Visual Simulation Systems
FlightSafety International
Phone: 314-551-8460
Fax: 314-551-8444
next prev parent reply other threads:[~1999-09-30 18:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-09-10 2:26 erik.de.smet
1999-09-10 8:00 ` Brian Ford [this message]
1999-09-30 18:02 ` Brian Ford
1999-09-30 18:02 ` erik.de.smet
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.GSO.4.10.9909100953150.20727-100000@eos \
--to=ford@vss.fsi.com \
--cc=erik.de.smet@philips.com \
--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).