From: Wade <neroz@ii.net>
To: "J.A. Magallon" <jamagallon@able.es>
Cc: linux-kernel@vger.kernel.org
Subject: Re: gcc-3.3.1 breaks kernel
Date: Sat, 12 Jul 2003 16:46:20 +0800 [thread overview]
Message-ID: <3F0FCADC.7090102@ii.net> (raw)
In-Reply-To: <20030712004301.GE2791@werewolf.able.es>
J.A. Magallon wrote:
> On 07.12, Christian Kujau wrote:
>
>>J.A. Magallon wrote:
>>
>>>Hi all...
>>>
>>>Any brave soul there is using a prerelease of gcc-3.3.1 to build kernels ?
>>>(don't know if RawHide or SuSE beta or any other have that, apart from
>>>MandrakeCooker).
>>
>>yes, 2.4.2x and 2.5.7x build properly with Debians gcc-3.3.1 here (x86).
>>
>
>
> Plz, can you tell me the exact version of gcc (date of snapshot or the
> like). My cooker gcc is:
gcc version 3.3.1 20030626 (Debian prerelease) in sid as of a couple
days ago.
> - Update to 3.3-hammer branch as of 2003/07/03
>
> Perhaps I can dig the gcc changelogs to look for something.
>
> This is really strange...
>
next prev parent reply other threads:[~2003-07-12 8:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <8avk.6lp.3@gated-at.bofh.it>
2003-07-11 23:45 ` gcc-3.3.1 breaks kernel Christian Kujau
2003-07-12 0:43 ` J.A. Magallon
2003-07-12 1:02 ` Daniel Jacobowitz
2003-07-12 8:46 ` Wade [this message]
2003-07-14 13:14 ` Martin Schlemmer
2003-07-11 17:59 J.A. Magallon
2003-07-11 18:51 ` Jeff Garzik
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=3F0FCADC.7090102@ii.net \
--to=neroz@ii.net \
--cc=jamagallon@able.es \
--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