From: Joe Buck <jbuck@synopsys.com>
To: Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at>
Cc: gcc@gcc.gnu.org
Subject: Re: gcc3.2.1 compilation failure on FreeBSD 5.0
Date: Tue, 28 Jan 2003 03:35:00 -0000 [thread overview]
Message-ID: <20030127175831.A669@synopsys.com> (raw)
In-Reply-To: <Pine.BSF.4.51.0301280231550.97245@acrux.dbai.tuwien.ac.at>; from pfeifer@dbai.tuwien.ac.at on Tue, Jan 28, 2003 at 02:38:27AM +0100
On Tue, Jan 28, 2003 at 02:38:27AM +0100, Gerald Pfeifer wrote:
> This is because FSF GCC lacks the patch below on the 3.2 release branch
>
> Gaby, this patch is most critical for 3.2.2 on FreeBSD 5; without it, GCC
> won't build at all. Would you mind applying it?
Is there a PR for this issue? Might be nice to make one even if we immediately
close it, just so the release notes can point to it and people can read
about the issue that was fixed.
next prev parent reply other threads:[~2003-01-28 1:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-27 17:14 Karel Gardas
2003-01-28 3:01 ` Gerald Pfeifer
2003-01-28 3:35 ` Joe Buck [this message]
2003-01-28 19:40 ` Gerald Pfeifer
2003-01-28 5:00 ` Gabriel Dos Reis
2003-01-28 14:04 ` Gerald Pfeifer
2003-01-28 14:07 ` Gabriel Dos Reis
2003-01-28 14:13 ` Karel Gardas
2003-01-28 7:35 ` Karel Gardas
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=20030127175831.A669@synopsys.com \
--to=jbuck@synopsys.com \
--cc=gcc@gcc.gnu.org \
--cc=pfeifer@dbai.tuwien.ac.at \
/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).