make-w32
[Top][All Lists]
Advanced

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

Re: [Angelo.Graziosi: Problems with patched gnu make ? (was:Need Volunte


From: William A. Hoffman
Subject: Re: [Angelo.Graziosi: Problems with patched gnu make ? (was:Need Volunteers to test patch for gnu make)]
Date: Wed, 04 Oct 2006 15:33:46 -0400

At 03:21 PM 10/4/2006, Eli Zaretskii wrote:
>> Date: Tue, 03 Oct 2006 23:11:04 +0200
>> From: Eli Zaretskii <address@hidden>
>> Cc: address@hidden
>> 
>> It looks like my guess about vpath was correct: the failing Make
>> doesn't see it.  That's quite strange, since I cannot see anything in
>> the code that could explain the problem.  Obviously, I'm missing
>> something...
>
>William, could you please verify that PATH_SEPARATOR_CHAR is set
>correctly in the patched Make that you built?  It should be `:' in the
>Cygwin build, and the way this is supposed to happen is because
>config.h (produced from config.h.in by the configure script) should
>define PATH_SEPARATOR_CHAR to `:'.  I presume that you still have the
>source tree you patched and compiled, so you should be able to look at
>config.h there.
>
>If config.h does NOT set PATH_SEPARATOR_CHAR to `:', then make.h will
>set it to `;' because HAVE_DOS_PATHS is defined.  If that's what
>happens, then I can definitely understand why vpath is not working,
>since vpath.c uses PATH_SEPARATOR_CHAR to break the vpath list into
>individual directories, and checks each one of them for existence in
>the file system.
>TIA

I do not see a PATH_SEPARATOR_CHAR in the config.h. or in the config.h.in.
Maybe I did not run automake correctly?   How is that supposed to be set?
Sorry for the trouble.... 

-Bill










reply via email to

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