So, what about kwhich on RH6.2?
Are we going to use Miquel's patch? I cannot build fresh 2.2.x on plain RH6.2 without it. The 2.2.19-pre6 comes out without it. Or is "install new bash" the official answer? Alan?
-- Pete
scripts/kwhich +1 -1
@@ -7,7 +7,7 @@ exit 1 fi -IFS=: +IFS=":$IFS" for cmd in $* do for path in $PATH
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
Please read the FAQ at http://www.tux.org/lkml/
Date: Wed, 03 Jan 2001 22:08:33 -0800
From: Pete Zaitcev <[email protected]>
Are we going to use Miquel's patch? I cannot build fresh 2.2.x on plain RH6.2 without it. The 2.2.19-pre6 comes out without it. Or is "install new bash" the official answer? Alan?
I do not understand, I just got a working 2.2.19-pre6 build on one of my 6.2 Sparc64 systems, what kind of failure do you see?
Later,
David S. Miller
[email protected]
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
Please read the FAQ at http://www.tux.org/lkml/
Quoted 9 lines
Date: Wed, 03 Jan 2001 22:08:33 -0800
From: Pete Zaitcev <[email protected]>Are we going to use Miquel's patch? I cannot build fresh 2.2.x on plain RH6.2 without it. The 2.2.19-pre6 comes out without it. Or is "install new bash" the official answer? Alan?
I do not understand, I just got a working 2.2.19-pre6 build on one of my 6.2 Sparc64 systems, what kind of failure do you see?
Oops. I cannot reproduce it anymore. Since I am quite sure in my recollection of this problem, I conclude that there was a kernel (perhaps 2.2.19-pre3), that called kwhich with several arguments. No problem now on the pre6.
-- Pete
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
Please read the FAQ at http://www.tux.org/lkml/
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....
-
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
Please read the FAQ at http://www.tux.org/lkml/
Quoted 4 lines · Andrew Morton
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?
-Andi
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
Please read the FAQ at http://www.tux.org/lkml/
Quoted 8 lines · Andi Kleen
Quoted 4 lines · Andrew Morton
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 ?
I don't buy that. The compulsory modutils upgrade a couple of months back caused, what? Ten emails?
Quoted 1 line
Would you volunteer to handle the support load on l-k that would cause?
With pleasure.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
Please read the FAQ at http://www.tux.org/lkml/
Quoted 8 lines · Andrew Morton
Quoted 4 lines
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.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
Please read the FAQ at http://www.tux.org/lkml/
Quoted 4 lines
Quoted 1 line
And break compilation on all non RedHat 7, non connectiva systems ?
I don't buy that. The compulsory modutils upgrade a couple of months back caused, what? Ten emails?
Most people are still using the old old modutils
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
Please read the FAQ at http://www.tux.org/lkml/
Quoted 11 lines · On 2001.01.04 Alan Cox wrote:
Quoted 8 lines · Andrew Morton
Quoted 4 lines
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)
Signature · 9 lines
J.A. Magallon $> cd pub mailto:[email protected] $> 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 [email protected] Please read the FAQ at http://www.tux.org/lkml/
Quoted 7 lines
Quoted 5 lines
Quoted 2 lines
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.
Creating symlinks during the build would solve the problem.
/usr/src/linux/kern-cc -> /usr/bin/kgcc/usr/src/linux/user-cc -> /usr/bin/gcc
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
Please read the FAQ at http://www.tux.org/lkml/
Quoted 6 lines · Albert D. Cahalan
Quoted 6 lines
Quoted 5 lines
Quoted 2 lines
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?
Quoted 6 lines
Quoted 1 line
Hardcoding kgcc is definitely not an option.
Creating symlinks during the build would solve the problem.
/usr/src/linux/kern-cc->/usr/bin/kgcc/usr/src/linux/user-cc->/usr/bin/gcc
But who builds kernels in /usr/src anymore, or as root for that
matter... ;o)
----------------------------------------------------------------------
Mike A. Harris - Linux advocate - Free Software advocate
This message is copyright 2000, all rights reserved.
Views expressed are my own, not necessarily shared by my employer.
----------------------------------------------------------------------
If at first you don't succeed, call it version 1.0
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
Please read the FAQ at http://www.tux.org/lkml/