public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: N8TM@aol.com
To: rahul.parasnis@creditlyonnais.fr, gcc@gcc.gnu.org
Subject: Re: Support
Date: Sun, 30 Jan 2000 21:41:00 -0000	[thread overview]
Message-ID: <77.1214a01.25c67a77@aol.com> (raw)

In a message dated 1/30/2000 8:41:59 PM Pacific Standard Time, 
rahul.parasnis@creditlyonnais.fr writes:

> I have downloaded the gcc-2_95_2_tar software I am not sure wheather it 
will 
>  work on HPUX11.0 !!
>  
>  Could  you please give some advice on how to find gcc on HPUX 11.0 

gcc-2.95.2 doesn't support HPUX 11 (it won't build "out of the box.")  
gcc-2.96 (the current development version) supports HPUX 11 but the warning 
about "instability" of development egcs should be heeded.  As I myself have 
discontinued work with HPUX, I don't know the current quality of that port.  
gcc-2.96 will be found on ftp://gcc.cygnus.com/pub/egcs/snapshots and its 
mirrors with roughly weekly versions.

Tim
tprince@computer.org

             reply	other threads:[~2000-01-30 21:41 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-01-30 21:41 N8TM [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-12-09  9:32 Support rajrao
2000-02-01  7:06 Support Galloway, Greg (ISSAtlanta)
2000-02-01  1:37 Support Rahul Parasnis
2000-02-01  8:57 ` Support Joe Buck
2000-02-01 20:08 ` Support Alexandre Oliva
2000-01-31 12:44 Support Galloway, Greg (ISSAtlanta)
2000-01-31 12:48 ` Support Alexandre Oliva
2000-01-31 22:31   ` Support Russ Allbery
2000-01-31 16:12 ` Support Jeffrey A Law
2000-02-01 20:03   ` Support Alexandre Oliva
2000-02-01 20:20     ` Support Jeffrey A Law
2000-01-30 20:40 Support Rahul Parasnis
2000-01-30 20:59 ` Support 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=77.1214a01.25c67a77@aol.com \
    --to=n8tm@aol.com \
    --cc=gcc@gcc.gnu.org \
    --cc=rahul.parasnis@creditlyonnais.fr \
    /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).