From: "J . A . Magallon" <jamagallon@able.es>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: So, what about kwhich on RH6.2?
Date: Thu, 4 Jan 2001 23:03:48 +0100 [thread overview]
Message-ID: <20010104230348.E1148@werewolf.able.es> (raw)
In-Reply-To: <20010104091241.B18973@gruyere.muc.suse.de> <E14EBZw-0005oG-00@the-village.bc.nu>
In-Reply-To: <E14EBZw-0005oG-00@the-village.bc.nu>; from alan@lxorguk.ukuu.org.uk on Thu, Jan 04, 2001 at 15:41:17 +0100
On 2001.01.04 Alan Cox wrote:
> > On Thu, Jan 04, 2001 at 07:13:58PM +1100, Andrew Morton wrote:
> > > Silly question:
> > >
> > > can't we just hardwire `kgcc' into the build system and be done
> > > with all this kwhich stuff? It's just a symlink....
> >
> > And break compilation on all non RedHat 7, non connectiva systems ?
> > Would you volunteer to handle the support load on l-k that would cause?
>
> Hardcoding kgcc is definitely not an option.
>
In Mdk 7.2+ there is something called 'alternatives' that seems to be
inherited-copied from Debian. I read aboce that RH and Conectiva have it.
It allows
you to have some gcc-2.95, gcc-2.96, and select a default gcc that
points to the one desired. It has defaults and priorities.
Same thing could be done with 'kgcc': kernel needs something called
kgcc, its up to you to set it up.
In my case (mdk), kgcc is a binary from egcs-1.1.2. If I want to try
building a kernel with gcc-2.96, I should uninstall egcs to let
kernel miss kgcc and find gcc, or tweak kernel Makefiles.
(OT: I still dont understand why egcs is still named egcs instead
of gcc-2.91)
--
J.A. Magallon $> cd pub
mailto:jamagallon@able.es $> more beer
Linux werewolf 2.2.19-pre6 #1 SMP Wed Jan 3 21:28:10 CET 2001 i686
-
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:[~2001-01-04 22:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-04 6:08 So, what about kwhich on RH6.2? Pete Zaitcev
2001-01-04 6:11 ` David S. Miller
2001-01-04 7:07 ` Pete Zaitcev
2001-01-04 8:13 ` Andrew Morton
2001-01-04 8:12 ` Andi Kleen
2001-01-04 8:24 ` Andrew Morton
2001-01-04 14:42 ` Alan Cox
2001-01-04 14:41 ` Alan Cox
2001-01-04 22:03 ` J . A . Magallon [this message]
2001-01-04 22:12 ` Albert D. Cahalan
2001-01-05 10:57 ` Mike A. Harris
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=20010104230348.E1148@werewolf.able.es \
--to=jamagallon@able.es \
--cc=alan@lxorguk.ukuu.org.uk \
--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