From: Adrian Bunk <bunk@fs.tum.de>
To: Ville Herva <vherva@niksula.cs.hut.fi>,
Marcelo Tosatti <marcelo@conectiva.com.br>,
linux-kernel@vger.kernel.org, gibbs@scsiguy.com, alan@redhat.com
Subject: Re: 2.4.22pre8 hangs too (Re: 2.4.21-jam1, aic7xxx-6.2.36: solid hangs)
Date: Sat, 9 Aug 2003 22:19:51 +0200 [thread overview]
Message-ID: <20030809201951.GP16091@fs.tum.de> (raw)
In-Reply-To: <20030808125502.GB150921@niksula.cs.hut.fi>
On Fri, Aug 08, 2003 at 03:55:02PM +0300, Ville Herva wrote:
>...
> Ok, the kernel compiled with gcc version 3.2.1 20021207 (Red Hat Linux 8.0
> 3.2.1-2) has now been up for more than a week. It seems stable, but I'm not
> sure yet.
>
> Which brings me to the question: which gcc version is considered most stable
> for compiling 2.4.x these days?
>...
> This seems to suggest 2.96-85 would be more stable than gcc-3.2.1-2. Is this
> the case?
>...
2.95.3 and the (unofficial) 2.96 are the best compilers for 2.4 .
In most cases 3.2.1 will give you a working kernel, but if you need
maximum stablity don't use gcc 3.x for compiling kernel 2.4 .
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:[~2003-08-09 20:19 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-29 7:39 2.4.21-jam1, aic7xxx-6.2.36: solid hangs, crashes on boot Ville Herva
2003-07-30 7:13 ` 2.4.22pre8 hangs too (Re: 2.4.21-jam1, aic7xxx-6.2.36: solid hangs) Ville Herva
2003-07-30 14:50 ` Marcelo Tosatti
2003-07-30 18:10 ` Ville Herva
2003-08-08 12:55 ` Ville Herva
2003-08-09 20:19 ` Adrian Bunk [this message]
2003-08-09 22:15 ` Ville Herva
2003-08-27 6:43 ` 2.4.22pre8 hangs too (Re: 2.4.21-jam1 " Ville Herva
2003-08-27 7:03 ` Stephan von Krawczynski
2003-08-27 7:12 ` Ville Herva
2003-08-27 7:21 ` Stephan von Krawczynski
2003-08-27 7:37 ` Ville Herva
2003-08-27 9:30 ` Stephan von Krawczynski
2003-08-27 10:13 ` Ville Herva
2003-08-27 10:56 ` Stephan von Krawczynski
2003-08-27 11:04 ` Ville Herva
2003-08-27 11:30 ` Stephan von Krawczynski
2003-08-28 9:26 ` Ingo Oeser
2003-08-28 19:09 ` Ville Herva
2003-08-28 1:13 ` TeJun Huh
2003-08-28 5:40 ` Ville Herva
2003-08-28 5:57 ` Tejun Huh
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=20030809201951.GP16091@fs.tum.de \
--to=bunk@fs.tum.de \
--cc=alan@redhat.com \
--cc=gibbs@scsiguy.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
--cc=vherva@niksula.cs.hut.fi \
/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
Powered by JetHome