From: kaih@khms.westfalen.de (Kai Henningsen)
To: linux-kernel@vger.kernel.org
Subject: Re: recommended gcc compiler version
Date: 24 Dec 2000 11:14:00 +0200 [thread overview]
Message-ID: <7sSHKzAmw-B@khms.westfalen.de> (raw)
In-Reply-To: <Pine.LNX.4.21.0012221746160.320-100000@bee.lk>
In-Reply-To: <E149NvR-0004Kz-00@the-village.bc.nu> <Pine.LNX.4.21.0012221746160.320-100000@bee.lk>
anuradha@gnu.org (Anuradha Ratnaweera) wrote on 22.12.00 in <Pine.LNX.4.21.0012221746160.320-100000@bee.lk>:
> On Fri, 22 Dec 2000, Alan Cox wrote:
>
> > For i386
> >
> > 2.2.18
> > gcc 2.7.2 or egcs-1.1.2
>
> Just a remainder for debian users. There is a debian package gcc272 which
> is said to be the "GNU C compiler's C part", for "backword compatibility
> purposes". I recompiled my kernel after an
>
> apt-get install gcc272
>
> and after setting
>
> HOSTGCC = gcc272
>
> in kernel source tree Makerile.
I recently compiled 2.2.18 and noticed that make-kpkg (from kernel-package
- don't compile kernels on Debian without it!) did that automatically.
Incidentally, I really like the Flavours patch.
MfG Kai
-
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-24 14:10 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
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 [this message]
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=7sSHKzAmw-B@khms.westfalen.de \
--to=kaih@khms.westfalen.de \
--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