From: John Weber <weber@nyc.rr.com>
To: linux-kernel@vger.kernel.org
Subject: Re: kernel compiler
Date: Thu, 25 Oct 2001 11:20:32 -0400 [thread overview]
Message-ID: <3BD82DC0.7697B1AF@nyc.rr.com> (raw)
David Weinehall wrote:
>
> On Thu, Oct 25, 2001 at 10:31:08AM -0400, Frontgate Lab wrote:
> > Just out of a need to know things :)
> >
> > What compiler do Alan Cox and Linus use to create the 2.4 series
> > kernels?
> >
> > I am currently using RedHat's compiler gcc-2.96-85 and have been told
> > not to do so because it "breaks things" .
>
> This is likely due to the fact that some people are still living with
> the misconception that all gcc-2.96 releases are buggy. They are not;
> only early versions are.
>
> gcc-2.95.[34] and gcc-2.96-(newer versions) are viable choices if you
> want a working kernel. Some other versions might work, but then again,
>
> At the moment, gcc3 doesn't work too well with the kernel, and you won't
> get any large benefit.
>
I use gcc3 to compile anything and everything I need. With the
exception of "multi-line literal complaints", my kernel compiles fine.
Is there anything that I should know?
next reply other threads:[~2001-10-25 15:20 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-25 15:20 John Weber [this message]
2001-10-25 15:26 ` kernel compiler 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
-- strict thread matches above, loose matches on Subject: below --
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
2001-10-25 15:46 ` Jakub Jelinek
2001-10-25 15:45 ` Steve Lord
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=3BD82DC0.7697B1AF@nyc.rr.com \
--to=weber@nyc.rr.com \
--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