From: Paul Clements <Paul.Clements@SteelEye.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: gcc bug causing problem in kernel builds
Date: Thu, 23 Aug 2001 16:04:50 -0400 [thread overview]
Message-ID: <3B8561E2.DE166AD8@SteelEye.com> (raw)
In-Reply-To: <E15a0eY-0004U3-00@the-village.bc.nu>
Alan Cox wrote:
> gcc 2.96-54 had plenty of bugs, 2.96-75+ should be perfectly fine for
> all uses.
Uh oh... the gcc 2.96 I'm using is:
# rpm -q gcc
gcc-2.96-81
> If you have a 2.96 RH problem please report it in Red Hat
> bugzilla
Will do.
Thanks,
Paul
Paul.Clements@SteelEye.com
next prev parent reply other threads:[~2001-08-23 20:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-23 19:40 gcc bug causing problem in kernel builds Paul Clements
2001-08-23 20:00 ` Alan Cox
2001-08-23 20:04 ` Paul Clements [this message]
2001-08-23 20:55 ` Jakub Jelinek
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=3B8561E2.DE166AD8@SteelEye.com \
--to=paul.clements@steeleye.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.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