bug-glibc
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: 2.1.95: configure doesn't search $PATH to find make


From: Patrick Smith
Subject: Re: 2.1.95: configure doesn't search $PATH to find make
Date: Mon, 23 Oct 2000 09:10:51 -0400

Andreas Jaeger wrote:
> 
> >>>>> Patrick Smith writes:
> 
>  > With make 3.77 in /usr/bin/make and make 3.79 in another directory,
>  > which appears earlier in my $PATH, if I type
> 
>  >      /PATH-TO_SOURCE/configure ...
> 
>  > then configure finds make 3.77 and refuses to proceed.
> Configure your system correctly - we search for:
> gnumake, gmake and then make in the path (see configure for details).

Oops.  I missed that detail.  Sorry...


>  > If I type (in bash)
> 
>  >      MAKE=`type -path make` /PATH-TO_SOURCE/configure ...
> 
>  > then configure finds make 3.79 and is content.
> 
>  > As make will normally be invoked through the user's $PATH by the user
>  > typing 'make' at a shell prompt, shouldn't configure also locate make in
>  > this fashion?
> It does, I don't understand why it doesn't work for you.

I see it now.  I'm running RedHat 6.0, which puts make in /usr/bin/make
and creates /usr/bin/gmake as a symlink to that.  On top of that, I
picked up make-3.79 and compiled and built it myself, installing it in
another directory.  But the 'make install' for make just installs the
make executable; it doesn't create gmake or gnumake.

Perhaps if configure finds gnumake or gmake with an unacceptable
version, it should continue looking for make under the remaining names?
-- 
address@hidden



reply via email to

[Prev in Thread] Current Thread [Next in Thread]