public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "RaúlNúñez de Arenas Coronado" <dervishd@jazzfree.com>
To: linux-kernel@vger.kernel.org, roy@karlsbakk.net
Subject: Re: Which gcc version?
Date: Fri, 23 Nov 2001 18:12:53 +0100	[thread overview]
Message-ID: <E167Jsj-00002C-00@DervishD> (raw)

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 856 bytes --]

    Hi Roy :)))

>Which one should I use to compile the kernel?

    Dunno about RH, but I compile the kernel using gcc-3.0.1 and
works fine. Well, take into account that this is NOT the recommended
choice, since gcc 3.x series is not considered stable for the kernel.

    Anyway, I'm tired to having a compiler for binaries, another
compiler for the kernel, another one for libraries, etc... and I
compile all using gcc 3.0.1.

    Sooner or later the kernel will need to be ported to gcc 3.x
series, so, the sooner it gets tested with this compiler, the better.

    Anyway, if you have gcc 2.95.x installed onto your distro, use
that for the kernel for maximum stability.

    My compiled kernel works with gcc 3.x but it's a kernel with no
so many drivers. I don't know what kind of weird things can happen
with a heluvalota drivers kernel.

    Raúl

             reply	other threads:[~2001-11-23 17:46 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-23 17:12 RaúlNúñez de Arenas Coronado [this message]
2001-11-23 18:02 ` Which gcc version? M. Edward (Ed) Borasky
2001-11-23 18:14   ` Thorsten Glaser
  -- strict thread matches above, loose matches on Subject: below --
2001-11-23 12:53 Roy Sigurd Karlsbakk
2001-11-23 12:57 ` Arjan van de Ven
2001-11-23 13:51 ` war
2001-11-23 19:43   ` J Sloan
2001-11-23 13:59 ` Anton Altaparmakov
2001-11-23 14:11   ` war
2001-11-23 15:14     ` Arjan van de Ven
2001-11-23 15:30       ` Gábor Lénárt
2001-11-23 15:34         ` Arjan van de Ven
2001-11-23 19:50         ` J Sloan
2001-11-23 20:34           ` John Jasen
2001-11-23 21:55             ` J Sloan
2001-11-24  3:08               ` John Jasen
2001-11-24 12:24             ` Paul G. Allen
2001-11-26 18:31             ` Alan Cox
2001-11-27  8:42               ` Ahmed Masud
2001-11-23 16:10       ` Anton Altaparmakov
2001-11-23 14:43   ` Anton Altaparmakov
2001-11-23 16:23     ` Jeff Garzik
2001-11-23 18:30   ` Daniel Phillips
2001-11-23 18:56   ` Anton Altaparmakov
2001-11-23 19:28     ` Daniel Phillips
2001-11-23 20:14       ` Andrew Morton
2001-11-23 20:24       ` Anton Altaparmakov
2001-11-23 20:35         ` Andrew Morton
2001-11-23 21:09           ` David Weinehall
2001-11-24 16:01     ` Luigi Genoni
2001-11-24 16:09       ` Daniel Phillips
2001-11-24 17:32         ` Luigi Genoni
2001-04-05 10:56 which " Manoj Sontakke
2001-04-05  5:48 ` Alexander Viro
2001-04-05 14:09   ` Manoj Sontakke
2001-04-05 11:37     ` Bart Trojanowski
2001-04-05 12:02       ` Matti Aarnio
2001-04-05 12:26       ` David Woodhouse
2001-04-05 12:31         ` Matti Aarnio
2001-04-05 13:09         ` Richard B. Johnson
2001-04-05 11:45     ` Matti Aarnio
2001-04-05 11:50     ` christophe barbe

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=E167Jsj-00002C-00@DervishD \
    --to=dervishd@jazzfree.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=roy@karlsbakk.net \
    /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