public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: ro@gcc.gnu.org To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org, olle@cb.uu.se, ro@gcc.gnu.org Subject: Re: other/9671: gcc.3.2.2 do not build on a HP Tru64 Unix v5.1B system Date: Thu, 20 Feb 2003 12:55:00 -0000 [thread overview] Message-ID: <20030220125501.18185.qmail@sources.redhat.com> (raw) Synopsis: gcc.3.2.2 do not build on a HP Tru64 Unix v5.1B system Responsible-Changed-From-To: unassigned->ro Responsible-Changed-By: ro Responsible-Changed-When: Thu Feb 20 12:55:01 2003 Responsible-Changed-Why: Mine. State-Changed-From-To: open->feedback State-Changed-By: ro State-Changed-When: Thu Feb 20 12:55:01 2003 State-Changed-Why: As explained in PR other/9670, building with a copy of gcc from a different O/S release cannot generally work. Please try bootstrapping with the vendor cc instead. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=9671
next reply other threads:[~2003-02-20 12:55 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-02-20 12:55 ro [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-02-24 18:57 ro 2003-02-12 7:46 olle
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=20030220125501.18185.qmail@sources.redhat.com \ --to=ro@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ --cc=gcc-gnats@gcc.gnu.org \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@gcc.gnu.org \ --cc=olle@cb.uu.se \ /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: linkBe 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).