From: "Matthew D. Pitts" <mpitts@suite224.net>
To: "Robert B. Easter" <reaster@comptechnews.com>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: recommended gcc compiler version
Date: Fri, 22 Dec 2000 01:19:07 -0500 [thread overview]
Message-ID: <001901c06bdf$1d6c74e0$3b42b0d1@pittscomp.com> (raw)
In-Reply-To: <0012212320430F.02217@comptechnews>
Robert,
gcc 2.7.2.3 is the safest, but egcs 1.1.2 will work. any kernels built with
gcc 2.95.x work but can be buggy.
Matthew Pitts
mpitts@suite224.net
----- Original Message -----
From: Robert B. Easter <reaster@comptechnews.com>
To: <linux-kernel@vger.kernel.org>
Sent: Thursday, December 21, 2000 11:20 PM
Subject: recommended gcc compiler version
> This is a newbie question, but what are the recommended gcc compiler
versions
> for compiling,
>
> Linux 2.2.18?
>
> Linux 2.4.0?
>
>
> I'd rather use the recommended version than not and have difficult bugs.
>
> Thanks. If there is a FAQ, kindy direct me to it, or, if this info isn't
in
> there specificly, perhaps a FAQ maintainer can add this stuff.
>
> --
> -------- Robert B. Easter reaster@comptechnews.com ---------
> - CompTechNews Message Board http://www.comptechnews.com/ -
> - CompTechServ Tech Services http://www.comptechserv.com/ -
> ---------- http://www.comptechnews.com/~reaster/ ------------
> -
> 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/
-
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/
next prev parent reply other threads:[~2000-12-22 6:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-22 4:20 recommended gcc compiler version Robert B. Easter
2000-12-22 6:19 ` Matthew D. Pitts [this message]
2000-12-22 7:08 ` Tim Wright
2000-12-22 19:17 ` Linus Torvalds
2000-12-23 15:55 ` Matthew Vanecek
2000-12-22 7:00 ` Barry K. Nathan
2000-12-22 18:09 ` Andreas Dilger
2000-12-22 8:51 ` Alan Cox
2000-12-22 10:54 ` Rogier Wolff
2000-12-22 11:53 ` Anuradha Ratnaweera
2000-12-24 9:14 ` Kai Henningsen
2000-12-26 8:06 ` Anuradha Ratnaweera
2000-12-22 19:25 ` Linus Torvalds
2000-12-22 20:11 ` Andi Kleen
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='001901c06bdf$1d6c74e0$3b42b0d1@pittscomp.com' \
--to=mpitts@suite224.net \
--cc=linux-kernel@vger.kernel.org \
--cc=reaster@comptechnews.com \
/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