From: Russ Allbery <rra@stanford.edu>
To: gcc <gcc@gcc.gnu.org>
Subject: Re: Support
Date: Mon, 31 Jan 2000 22:31:00 -0000 [thread overview]
Message-ID: <yld7qhtowk.fsf@windlord.stanford.edu> (raw)
In-Reply-To: <org0ve2cjn.fsf@garnize.lsd.ic.unicamp.br>
Alexandre Oliva <oliva@lsd.ic.unicamp.br> writes:
> Nope. No gcc release prior to 2.96 or 2.97 or 3.0 or however the next
> release ends up being called supports HP/UX 11.
Could someone clarify (or point me at the clarification) of just what this
means? I'm surprised by this, given that it compiles cleanly out of the
tarball and compiles Perl with no test suite failures.
amyimage:~> gcc -v
Reading specs from /usr/pubsw/lib/gcc-lib/hppa2.0n-hp-hpux11.00/2.95.1/specs
gcc version 2.95.1 19990816 (release)
amyimage:~> uname -a
HP-UX amyimage B.11.00 A 9000/780 2005717121 two-user license
amyimage:~> cat > hello.c
#include <stdio.h>
int main(void) { printf("Hello world!\n"); }
amyimage:~> gcc -o hello hello.c
amyimage:~> ./hello
Hello world!
--
Russ Allbery (rra@stanford.edu) <URL: http://www.eyrie.org/~eagle/ >
next prev parent reply other threads:[~2000-01-31 22:31 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-01-31 12:44 Support Galloway, Greg (ISSAtlanta)
2000-01-31 12:48 ` Support Alexandre Oliva
2000-01-31 22:31 ` Russ Allbery [this message]
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
-- 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-30 21:41 Support N8TM
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=yld7qhtowk.fsf@windlord.stanford.edu \
--to=rra@stanford.edu \
--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).