From: Steve Lord <lord@sgi.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: mdiwan@wagweb.com (Frontgate Lab), linux-kernel@vger.kernel.org
Subject: Re: kernel compiler
Date: Thu, 25 Oct 2001 10:27:18 -0500 [thread overview]
Message-ID: <200110251527.f9PFRIx15728@jen.americas.sgi.com> (raw)
In-Reply-To: Message from Alan Cox <alan@lxorguk.ukuu.org.uk> of "Thu, 25 Oct 2001 16:28:22 BST." <E15wmQg-0005Bl-00@the-village.bc.nu>
Alan Cox wrote:
> > What compiler do Alan Cox and Linus use to create the 2.4 series
> > kernels?
>
> Im using Red Hat 2.96-85
>
> > I am currently using RedHat's compiler gcc-2.96-85 and have been told
> > not to do so because it "breaks things" .
>
> Generally ignore that story: 2.96-54 has problems, but not the later ones
>
> > The question would be .. how hard is it going to be for me to upgrade to
> > gcc 3 + and will i get any benefit from it? WillI loose any
> > advantages that i currently do have?
>
> Gcc 3.0 doesn't always build correct kernels. Its very much a .0 release -
> new infrastructure, the core to do far better thinga than gcc 2.* but not
> yet the actual results as the bugs all get kicked out
>
> > Or can i still get what i need from compiling 2.4.12 or 2.4.13 with the
> > compiler I have now?
>
> Yeah
> -
Just for information, none of the Redhat compilers (the 2.96 leg) build
all of XFS correctly, see this bug for info:
http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=54571
Steve
next prev parent reply other threads:[~2001-10-25 15:31 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-25 14:31 Frontgate Lab
2001-10-25 15:08 ` David Weinehall
2001-10-25 15:28 ` Alan Cox
2001-10-25 15:27 ` Steve Lord [this message]
2001-10-25 15:46 ` Jakub Jelinek
2001-10-25 15:45 ` Steve Lord
2001-10-25 15:20 John Weber
2001-10-25 15:26 ` Axel
2001-10-25 15:45 ` Alan Cox
2001-10-25 16:45 ` Lost Logic
2001-10-25 17:16 ` Alan Cox
2001-10-25 22:00 ` J . A . Magallon
2001-10-25 22:13 ` J . A . Magallon
2001-10-26 9:18 ` Allan Sandfeld
2001-10-26 9:35 ` 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=200110251527.f9PFRIx15728@jen.americas.sgi.com \
--to=lord@sgi.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=mdiwan@wagweb.com \
/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
all inboxes | Powered by JetHome®