From: "J.A. Magallon" <jamagallon@able.es>
To: Adrian Bunk <bunk@fs.tum.de>
Cc: "Justin M. Forbes" <kernelmail@attbi.com>,
marcelo@conectiva.com.br, linux-kernel@vger.kernel.org
Subject: Re: 2.4.19-rc2 compile fail
Date: Thu, 18 Jul 2002 00:18:37 +0200 [thread overview]
Message-ID: <20020717221837.GA2390@werewolf.able.es> (raw)
In-Reply-To: <Pine.NEB.4.44.0207171902230.16056-100000@mimas.fachschaften.tu-muenchen.de>; from bunk@fs.tum.de on Wed, Jul 17, 2002 at 19:11:49 +0200
On 2002.07.17 Adrian Bunk wrote:
>On Wed, 17 Jul 2002, Justin M. Forbes wrote:
>
>> GCC version is 3.1 .config is attached, fairly large as I base it off of
>> the original Red Hat one to make sure everything compiles, even though I
>> am not using most of it. Strangely no compile problems on my base 7.2 box
>> (gcc 2.96). .config is attached.
>
>The short answer ist perhaps: 3.1 is not a supported compiler...
>
>But I'm surprised that I wasn't able to reproduce it using the 20020703
>(past 3.1) snapshot of the gcc-3.1 branch that is in Debian unstable.
>
I am building kernels with Mandrakes gcc-3.1.1 snapshots since time ago,
and have no problems with it (now gcc-3.1.1-0.7mdk, branch of 2002/07/01)
Probably kernel is more sensible to binutils version...
Here: binutils-2.12.90.0.14-2mdk
--
J.A. Magallon \ Software is like sex: It's better when it's free
mailto:jamagallon@able.es \ -- Linus Torvalds, FSF T-shirt
Linux werewolf 2.4.19-rc1-jam3, Mandrake Linux 8.3 (Cooker) for i586
gcc (GCC) 3.1.1 (Mandrake Linux 8.3 3.1.1-0.7mdk)
prev parent reply other threads:[~2002-07-17 22:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-17 0:59 2.4.19-rc2 compile fail Justin M. Forbes
2002-07-17 8:24 ` Adrian Bunk
2002-07-17 12:04 ` Justin M. Forbes
2002-07-17 17:11 ` Adrian Bunk
2002-07-17 22:18 ` J.A. Magallon [this message]
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=20020717221837.GA2390@werewolf.able.es \
--to=jamagallon@able.es \
--cc=bunk@fs.tum.de \
--cc=kernelmail@attbi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
/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