From: "Joshua M. Kwan" <joshk@ludicrus.ath.cx>
To: John Bradford <john@grabjohn.com>
Cc: linux-kernel@vger.kernel.org, abacus_an@yahoo.co.in
Subject: Re: kernel compilation: pls send cc to me
Date: Mon, 30 Dec 2002 02:43:57 -0800 [thread overview]
Message-ID: <20021230104357.GB13892@localhost> (raw)
In-Reply-To: <200212301038.gBUAcZWw000609@darkstar.example.net>
Oh...
Well, I stand corrected. I never noticed any difference compiling with
gcc-2.95 versus compiling with 3.2.
What is the recommended version then?
Regards
Josh
On Mon, Dec 30, 2002 at 10:38:35AM +0000, John Bradford wrote:
> > The kernel is meant to be very portable anyway.
>
> Not really. The kernel is designed to compiled with a specific
> compiler. A GCC version other than the recommended version might
> uncover bugs that should be fixed anyway, but it might also break
> things that are worked around for the recommended GCC version.
>
> John.
next prev parent reply other threads:[~2002-12-30 10:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-30 10:21 kernel compilation: pls send cc to me abacus an
2002-12-30 10:30 ` Joshua M. Kwan
2002-12-30 10:38 ` John Bradford
2002-12-30 10:43 ` Joshua M. Kwan [this message]
2002-12-30 11:00 ` John Bradford
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=20021230104357.GB13892@localhost \
--to=joshk@ludicrus.ath.cx \
--cc=abacus_an@yahoo.co.in \
--cc=john@grabjohn.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