All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Reppert <repp0017@tc.umn.edu>
To: "Karel Kulhavý" <clock@twibright.com>
Cc: Daniel Andersen <kernel-list@majorstua.net>,
	linux-kernel@vger.kernel.org
Subject: Re: gcc 2.95.3
Date: Fri, 23 Jan 2004 12:33:56 -0600	[thread overview]
Message-ID: <1074882836.20723.4.camel@minerva> (raw)
In-Reply-To: <20040123163008.B1237@beton.cybernet.src>

[-- Attachment #1: Type: text/plain, Size: 960 bytes --]

On Fri, 2004-01-23 at 10:30, Karel Kulhavý wrote:
> On Fri, Jan 23, 2004 at 05:01:23PM +0100, Daniel Andersen wrote:
> > > I read here "make sure you have gcc 2.95.3 available" - does it mean
> > > my gcc-3.2.3 or gcc-3.2.2 is not suitable for kernel compiling?
> > 
> > Please have a look at http://developer.osdl.org/cherry/compile/
> 
> What if the kernel compiles cleanly but the generated code is invalid?
> Or is gcc-3.2.2 BugFree(TM) (BugFree as in BugFree speech, not as
> in BugFree beer)?

Many people have been using gcc-3.2 or later to build kernels, and I
haven't really heard of any problems with this, at least on i386. I
personally have used 3.2.2 and 3.3.2 (well, with Debian's patches) and
haven't had any weirdness with 2.6 or 2.4. ISTR there being arches that
need 3.x to compile, but I could be mistaken.

2.95.3 is definitely the *oldest* compiler you'd want to use, and pretty
much skip between that and 3.2.

Matt

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2004-01-23 18:34 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-23 14:50 make in 2.6.x Karel Kulhavý
2004-01-23 15:11 ` Bas Mevissen
2004-01-23 15:20 ` Sam Ravnborg
2004-01-23 15:39   ` David Woodhouse
     [not found] ` <20040123100035.73bee41f.jeremy@kerneltrap.org>
2004-01-23 15:13   ` gcc 2.95.3 Karel Kulhavý
2004-01-23 16:03     ` Daniel Andersen
     [not found]     ` <001b01c3e1ca$26101f20$1e00000a@black>
2004-01-23 16:30       ` Karel Kulhavý
2004-01-23 18:33         ` Matthew Reppert [this message]
2004-01-23 23:20           ` Stef van der Made
2004-01-24  0:48             ` Russell King
2004-01-26 14:41               ` David Woodhouse
2004-01-24 12:46             ` Ingo Buescher
2004-01-24 18:32               ` Stef van der Made
2004-01-23 18:55     ` Felipe Alfaro Solana
2004-01-25 11:05     ` Florian Weimer
2004-01-23 15:20   ` make in 2.6.x Karel Kulhavý
2004-01-23 17:42 ` Wakko Warner
2004-01-23 20:32   ` Sam Ravnborg
  -- strict thread matches above, loose matches on Subject: below --
2001-11-13  1:02 GCC 2.95.3 Hawkins Jeffrey-CJH016
2001-02-21 14:48 gcc 2.95.3 Tom Appermont

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=1074882836.20723.4.camel@minerva \
    --to=repp0017@tc.umn.edu \
    --cc=clock@twibright.com \
    --cc=kernel-list@majorstua.net \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.