From: "Michael Frank" <mhf@linuxmail.org>
To: "Felipe Alfaro Solana" <felipe_alfaro@linuxmail.org>,
"Nick Bartos" <spam99@2thebatcave.com>
Cc: "Linux Kernel Mailinglist" <linux-kernel@vger.kernel.org>
Subject: Re: recommended "stable" compiler?
Date: Fri, 20 Feb 2004 21:58:30 +0800 [thread overview]
Message-ID: <opr3n83soj4evsfm@smtp.pacific.net.th> (raw)
In-Reply-To: <1077283178.798.2.camel@teapot.felipe-alfaro.com>
On Fri, 20 Feb 2004 14:19:39 +0100, Felipe Alfaro Solana <felipe_alfaro@linuxmail.org> wrote:
> On Fri, 2004-02-20 at 12:59, Nick Bartos wrote:
>> What is the recommended stable compiler for compiling the latest 2.4.x
>> kernel?
>
> I'm no kernel guru, but I have been compiling 2.5/2.6 kernels for a long
> time with gcc 3.3 with no problems at all. I had problems with gcc 3.2
> in the past, miscompiling the ymfpci driver.
>
I am linux newbie, but have done 100's of kernel compiles the past 2 years.
AFAIK, 2.95.3 is still the official compiler and still supported.
2.95.3 without framepointers compiling kernels for 686 has never failed me
with 2.4 and 2.6 and I still use it exclusively for kernels.
3.2.2 made me lots of trouble with kernels - crashing within minutes.
Using RH 3.2.5 and Gentoo 3.2.3 for other compiles (whole system except kernel
in case of gentoo). No problems seen.
Have not tried 3.3 but by what I have read it is OK.
In any case keep your trusted old workhorse 2.95 around when trying something new...
Regards
Michael
prev parent reply other threads:[~2004-02-20 14:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-20 11:59 Nick Bartos
2004-02-20 13:19 ` Felipe Alfaro Solana
2004-02-20 13:58 ` Michael Frank [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=opr3n83soj4evsfm@smtp.pacific.net.th \
--to=mhf@linuxmail.org \
--cc=felipe_alfaro@linuxmail.org \
--cc=linux-kernel@vger.kernel.org \
--cc=spam99@2thebatcave.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®