From: Adrian Bunk <bunk@fs.tum.de>
To: Paolo Ornati <ornati@fastwebnet.it>
Cc: Artemio <theman@artemio.net>,
Linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: error compiling linux-2.6.6
Date: Sat, 29 May 2004 19:21:36 +0200 [thread overview]
Message-ID: <20040529172136.GS16099@fs.tum.de> (raw)
In-Reply-To: <200405291646.55856.ornati@fastwebnet.it>
On Sat, May 29, 2004 at 04:46:55PM +0200, Paolo Ornati wrote:
> On Saturday 29 May 2004 15:21, you wrote:
> > I am continuing my tries...
> >
> > GCC 2.96, linux-2.6.6.
> > ...
> >
> > Am I doing something wrong? :-(
>
> YES, you are using a very BUGGY gcc version!
It's an unofficial gcc version, but it's not necessary more buggy than
other versions of gcc.
And Documentation/Changes in Linux 2.6.6 also tells that your statement
is wrong:
<-- snip -->
...
The Red Hat gcc 2.96 compiler subtree can also be used to build this tree.
You should ensure you use gcc-2.96-74 or later. gcc-2.96-54 will not build
the kernel correctly.
...
<-- snip -->
> Try 2.95.x (x >= 3) or go to 3.x.x.
>...
His problem is as far as I can see in no way related to the gcc version
he's using.
> Bye
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2004-05-29 17:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-29 11:24 error compiling linux-2.6.6 Artemio
2004-05-29 12:14 ` [2.6 patch] let IEEE1394 select NET Adrian Bunk
2004-05-29 12:23 ` Russell King
2004-05-29 12:57 ` Adrian Bunk
2004-05-29 23:55 ` Andy Lutomirski
2004-05-30 0:08 ` Randy.Dunlap
2004-05-29 13:21 ` error compiling linux-2.6.6 Artemio
2004-05-29 14:46 ` Paolo Ornati
2004-05-29 17:21 ` Adrian Bunk [this message]
2004-05-30 7:55 ` Paolo Ornati
2004-05-29 13:33 ` error compiling linux-2.6.6 and 2.6.7-cr1 Artemio
2004-05-29 14:17 ` Adrian Bunk
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=20040529172136.GS16099@fs.tum.de \
--to=bunk@fs.tum.de \
--cc=linux-kernel@vger.kernel.org \
--cc=ornati@fastwebnet.it \
--cc=theman@artemio.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.