mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Linux Kernel Developer" <linux_developer@hotmail.com>
To: <linux-kernel@vger.kernel.org>
Subject: Recommended compiler? - Re: [patch] kernel/module.c (plus gratuitous rant)
Date: Mon, 30 Oct 2000 06:19:16 -0500	[thread overview]
Message-ID: <OE43voFOAmEaJswFCHO000004ac@hotmail.com> (raw)
In-Reply-To: <4309.972694843@ocs3.ocs-net> <20001029232347.D4EB081F9@halfway.linuxcare.com.au> <20001030050821.B9175@wire.cadcamlab.org>

So which is the recommended compiler for each kernel version 2.2.x,
2.4.x(pre?) nowadays?  I've pretty much kept gcc 2.7.2.3 around just for
compiling the kernel however now I hear you need egcs to compile 2.4?  I
don't mind keeping 2.7.2.3 around in its own installation directory just for
the purpose of doing kernel work however from a previous post I've now got
the impression that egcs has become the recommended compiler?  If I'm going
to keep a secondary compiler around (outside of gcc 2.95.2 which I still
hear is no good for kernel compiles) just for kernel work I'd prefer to use
my disk space on the recommended one.

>
> [Rusty]
> > > CC=gcc-2723 make 2.0 kernel
> > > CC=gcc-2723 make 2.2 kernel
> > > CC=egcs make 2.4 kernel
> >
> > No, environment doesn't override make variables by default.  This
> > works on any shell:
> >
> > make CC=egcs <targets>
>
> If you're going to get pedantic, that won't work either -- since the
> makefiles in kernels 2.0 and 2.2 expect $(CC) to include some compiler
> flags.  This was fixed somewhere in 2.3.3x.
>
> Peter
> -


-
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 11:26 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   ` 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           ` Linux Kernel Developer [this message]
2000-10-30 11:58             ` Recommended compiler? - " Peter Samuelson
2000-10-30 13:49               ` Martin Dalecki
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=OE43voFOAmEaJswFCHO000004ac@hotmail.com \
    --to=linux_developer@hotmail.com \
    --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 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®