So, what about kwhich on RH6.2?

So, what about kwhich on RH6.2?

[Pete Zaitcev]

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

--- linux-2.2.19-pre3/scripts/kwhich	Sun Dec 10 16:49:45 2000
+++ linux-2.2.19-pre3-p3/scripts/kwhich	Sat Dec 23 21:10:33 2000
@@ -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 majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

Re: So, what about kwhich on RH6.2?

[David S. Miller]

   Date: 	Wed, 03 Jan 2001 22:08:33 -0800
   From: Pete Zaitcev <zaitcev@metabyte.com>

   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
davem@redhat.com
-
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/

Re: So, what about kwhich on RH6.2?

[Pete Zaitcev]

>    Date:        Wed, 03 Jan 2001 22:08:33 -0800
>    From: Pete Zaitcev <zaitcev@metabyte.com>
> 
>    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 majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

Re: So, what about kwhich on RH6.2?

[Andi Kleen]

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?


-Andi

-
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/

Re: So, what about kwhich on RH6.2?

[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....

-
-
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/

Re: So, what about kwhich on RH6.2?

[Andrew Morton]

Andi Kleen 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 ?

I don't buy that.  The compulsory modutils upgrade a couple of months
back caused, what?  Ten emails?

> 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 majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

Re: So, what about kwhich on RH6.2?

[Alan Cox]

> 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. 

-
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/

Re: So, what about kwhich on RH6.2?

[Alan Cox]

> > 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 majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

Re: So, what about kwhich on RH6.2?

[J . A . Magallon]

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/

Re: So, what about kwhich on RH6.2?

[Albert D. Cahalan]

>>> 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 majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

Re: So, what about kwhich on RH6.2?

[Mike A. Harris]

On Thu, 4 Jan 2001, Albert D. Cahalan wrote:

>>>> 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

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 majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/