> Date: Mon, 2 Oct 2006 15:22:04 +0200
> From: "Holleman, Bas" <[EMAIL PROTECTED]>
>
> Yes, that is true. On Windows, the PATH environment variable can have
> more than 256 characters. And I think it is the problem and something
> like this happens if PATH is to long: gmake can not handle so much
> From: Bas Holleman <[EMAIL PROTECTED]>
> Date: Fri, 29 Sep 2006 10:01:16 + (UTC)
>
> Hi Sebastien,
>
> About the problem: gmake begin_process CreateProcess failed.
I cannot find the beginning of this thread in the archives.
> This is my experience: The Windows PATH variable is to long. gm
Hi Sebastien,
About the problem: gmake begin_process CreateProcess failed.
This is my experience: The Windows PATH variable is to long. gmake runs in
something like a DOS environment. It can not handle more than 256 characters.
The solution: delete from the PATH variable what you don't need.
Goo
%% Andreas Buening <[EMAIL PROTECTED]> writes:
ab> Paul D. Smith wrote:
>> The idea I had involves changing escaped special characters like spaces
>> into "impossible" byte values in make's internal string representation.
>> That way all of make's current manipulation would continue to wor
Paul D. Smith wrote:
> The idea I had involves changing escaped special characters like spaces
> into "impossible" byte values in make's internal string representation.
> That way all of make's current manipulation would continue to work
> as-is: when searching for whitespace to break up words for
"Paul D. Smith" wrote on 2004-10-19 19:31 UTC:
> I'm not really sure what would be involved with providing support for
> full UTF-8 character sets in make; I'd have to think about it more.
I believe make works already pretty well with UTF-8 as it is. The only thing
you really need to think about i
%% Markus Kuhn <[EMAIL PROTECTED]> writes:
mk> Are colon and space really the only bytes that cannot be handled
mk> in a filename by make? How would you handle a pathologic filename
mk> that contains bytes such as 0xa0?
Well, filenames that contain newlines can't be represented either.
Mak
"Paul D. Smith" wrote on 2004-10-18 00:26 UTC:
> %% Markus Kuhn <[EMAIL PROTECTED]> writes:
>
> mk> The GNU make 3.80 manual lacks a section on quoting of special
> mk> characters that describes how any arbitrary byte sequence can be
> mk> provided as a prerequisite or a target in a rule.
>
%% Markus Kuhn <[EMAIL PROTECTED]> writes:
mk> The GNU make 3.80 manual lacks a section on quoting of special
mk> characters that describes how any arbitrary byte sequence can be
mk> provided as a prerequisite or a target in a rule.
There is no way to do this, which is why it's not describe
