public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Martin Dalecki <dalecki@evision-ventures.com>
To: Peter Samuelson <peter@cadcamlab.org>
Cc: Linux Kernel Developer <linux_developer@hotmail.com>,
	linux-kernel@vger.kernel.org
Subject: Re: Recommended compiler? - Re: [patch] kernel/module.c (plus gratuitous  rant)
Date: Mon, 30 Oct 2000 14:49:03 +0100	[thread overview]
Message-ID: <39FD7C4F.74D8DCCC@evision-ventures.com> (raw)
In-Reply-To: <4309.972694843@ocs3.ocs-net> <20001029232347.D4EB081F9@halfway.linuxcare.com.au> <20001030050821.B9175@wire.cadcamlab.org> <OE43voFOAmEaJswFCHO000004ac@hotmail.com> <20001030055859.C9175@wire.cadcamlab.org>

Peter Samuelson wrote:
> 
> > So which is the recommended compiler for each kernel version 2.2.x,
> > 2.4.x(pre?) nowadays?
> 
> * 2.91.66 aka egcs 1.1.2.  It has been officially blessed for 2.4 and
>   has been given an informal thumbs-up by Alan for 2.2.  (It does NOT
>   work for 2.0, if you still care about that.)
> 
> * 2.7.2.3 works for 2.2 (and 2.0) but NOT for 2.4.
> 
> * 2.95.2 seems to work with both 2.2 and 2.4 (no known bugs, AFAIK) and
>   many of us use it, but it is a little riskier than egcs.
> 
> * Red Hat "2.96" or CVS 2.97 will probably break any known kernel.

Works fine for me and 2.4.0-test10-pre5... however there are tons of
preprocessor warnings in some drivers.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  reply	other threads:[~2000-10-30 12:55 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <39F5830E.7963A935@uow.edu.au>
     [not found] ` <Pine.LNX.4.10.10010241353590.1743-100000@penguin.transmeta.com>
2000-10-27 17:45   ` [patch] kernel/module.c (plus gratuitous rant) Pavel Machek
2000-10-27 20:40     ` Jeff Garzik
2000-10-27 21:12       ` Alan Cox
2000-10-27 20:46     ` Alan Cox
2000-10-28  1:00     ` Keith Owens
2000-10-28 11:15       ` Dominik Kubla
2000-10-29  0:27         ` Richard Henderson
2000-10-29 15:09           ` Dominik Kubla
2000-10-30 11:05             ` Peter Samuelson
2000-10-30 18:50               ` Richard Henderson
2000-10-29 23:23       ` Rusty Russell
2000-10-30 11:08         ` Peter Samuelson
2000-10-30 11:19           ` Recommended compiler? - " Linux Kernel Developer
2000-10-30 11:58             ` Peter Samuelson
2000-10-30 13:49               ` Martin Dalecki [this message]
2000-10-30 20:50                 ` Horst von Brand
2000-10-30 22:02                   ` Jakub Jelinek
2000-10-31 10:27                   ` Martin Dalecki

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=39FD7C4F.74D8DCCC@evision-ventures.com \
    --to=dalecki@evision-ventures.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux_developer@hotmail.com \
    --cc=peter@cadcamlab.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