public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Ford <david@blue-labs.org>
To: sinisa@mysql.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.15 and GNU 3.0.2
Date: Mon, 26 Nov 2001 14:56:09 -0500	[thread overview]
Message-ID: <3C029E59.4040106@blue-labs.org> (raw)
In-Reply-To: <15362.34918.524256.760222@sinisa.nasamreza.org>

That really depends on what sort of system you are running it on.

Out of five computers I build kernels for at home here, one of them has 
an AMD K6II processor in it and that is the only one that I need to use 
gcc 2.95.3 with.  The rest I use 3.0.x and they are quite stable.  I 
just did a round of updates to 2.5.1p, but their prior uptimes were 
between 30 and 80 days.

I'm not saying 3.0.2 is perfect, for sure it isn't.  I'm saying that in 
some situations it can certainly be used.

Every compiler has issues, for some projects I have to use 3.0.2, some I 
have to use 2.95.3.  You keep notes on what works best and go with it.

David

Sinisa Milivojevic wrote:

>Hi!
>
>I think that documentation should stress more strongly that GNU 3.0.*
>series of compilers can not be used for building of the production
>kernels.
>
>I have got kernel panic in init ....
>
>This is not a complaint, just an information.
>
>



  parent reply	other threads:[~2001-11-26 19:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-26 18:22 2.4.15 and GNU 3.0.2 Sinisa Milivojevic
2001-11-26 18:36 ` Mr. Shannon Aldinger
2001-11-26 19:56 ` David Ford [this message]
2001-11-27 11:47   ` Sinisa Milivojevic
2001-12-08 17:38     ` Heinz Diehl
     [not found] <20011126193256.U5129@suse.de>
2001-11-26 19:18 ` Sinisa Milivojevic
2001-11-26 19:43   ` Ken Witherow

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=3C029E59.4040106@blue-labs.org \
    --to=david@blue-labs.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sinisa@mysql.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