public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: "John David Anglin" <dave@hiauly1.hia.nrc.ca>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: bootstrap/9989: [HPUX 11.00, gcc 3.3] fixing of stdio.h fails
Date: Mon, 10 Mar 2003 15:46:00 -0000 [thread overview]
Message-ID: <20030310154600.6140.qmail@sources.redhat.com> (raw)
The following reply was made to PR bootstrap/9989; it has been noted by GNATS.
From: "John David Anglin" <dave@hiauly1.hia.nrc.ca>
To: stefan.rupp@inform-ac.com (Stefan Rupp)
Cc: danglin@gcc.gnu.org, gcc-bugs@gcc.gnu.org, nobody@gcc.gnu.org,
struppi@acm.org, gcc-gnats@gcc.gnu.org
Subject: Re: bootstrap/9989: [HPUX 11.00, gcc 3.3] fixing of stdio.h fails
Date: Mon, 10 Mar 2003 10:41:39 -0500 (EST)
> Is there any patch ID you can provide? I am unfamiliar with HPUX.
I have PHCO_26111 installed. You can get patches via anonymous ftp at
ftp.itrc.hp.com. The ftp site has a catalog in each patch directory
which is useful for locating relevant patches. Web access is at
<http://us-support3.external.hp.com/common/bin/doc.pl/distrib_redir=2+1047309820|*>.
You will need to create an account but you don't need a service
contract to download individual patches. When you get patches via the
web, dependent patches will automatically be included in your download
and a script is included to build a depot containing all the downloaded
patches.
Read the hpux section in the installation documentation. You probably
also need the latest sed, make and linker patches. I always use GNU
make for my builds.
Dave
--
J. David Anglin dave.anglin@nrc-cnrc.gc.ca
National Research Council of Canada (613) 990-0752 (FAX: 952-6605)
next reply other threads:[~2003-03-10 15:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-10 15:46 John David Anglin [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-05-09 23:06 Dara Hazeghi
2003-03-10 9:56 Stefan Rupp
2003-03-08 1:51 danglin
2003-03-07 14:36 struppi
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=20030310154600.6140.qmail@sources.redhat.com \
--to=dave@hiauly1.hia.nrc.ca \
--cc=gcc-prs@gcc.gnu.org \
--cc=nobody@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).