At 05:38 PM 8/17/2006, Christopher Faylor wrote:
>On Fri, Aug 18, 2006 at 12:21:41AM +0300, Eli Zaretskii wrote:
>>> Date: Thu, 17 Aug 2006 17:02:30 -0400
>>> From: Bill Hoffman
>>>
>>> At 04:48 PM 8/17/2006, Christopher Faylor wrote:
>>>
>>> >I don't understand why MinGW's make should be using a
On Fri, Aug 18, 2006 at 12:34:16AM +0300, Eli Zaretskii wrote:
>> Date: Thu, 17 Aug 2006 17:30:50 -0400
>> From: Christopher Faylor <[EMAIL PROTECTED]>
>> Cc:
>>
>> >One thing: my original idea was to have a configure option that
>> >enabled the DOS path capabilities. I note some here are advoca
On Fri, Aug 18, 2006 at 12:21:41AM +0300, Eli Zaretskii wrote:
>> Date: Thu, 17 Aug 2006 17:02:30 -0400
>> From: Bill Hoffman
>>
>> At 04:48 PM 8/17/2006, Christopher Faylor wrote:
>>
>> >I don't understand why MinGW's make should be using anything like /bin/sh.
>> >Shouldn't it be using cmd.exe
On Thu, Aug 17, 2006 at 05:11:19PM -0400, William A. Hoffman wrote:
>I obviously care that the patch gets done. What I do not care about is
>the style of the code in make. The issue here is should sh_chars_sh be
>directly referenced or not. I think it should not, Chris things it
>should. It rea
At 05:10 PM 8/17/2006, Eli Zaretskii wrote:
>I use a shell that is a native Windows program, not a Cygwin
>program. (There could be some quoting conflict between the Cygwin
>and non-Cygwin binaries.)
To reproduce the problem you have to run from a cygwin shell or a msys shell.
-Bill
__
> Date: Thu, 17 Aug 2006 17:30:50 -0400
> From: Christopher Faylor <[EMAIL PROTECTED]>
> Cc:
>
> >One thing: my original idea was to have a configure option that
> >enabled the DOS path capabilities. I note some here are advocating a
> >configure test which simply sets the HAVE_DOS_PATHS option
On Thu, Aug 17, 2006 at 11:41:01PM +0300, Eli Zaretskii wrote:
>> Date: Thu, 17 Aug 2006 13:21:31 -0400
>> From: Christopher Faylor <[EMAIL PROTECTED]>
>> Cc:
>>
>> It does make me wonder what kind of quoting problems we'd see with
>> HAVE_DOS_PATHS, though. On cygwin, I wouldn't want every back
On Thu, Aug 17, 2006 at 04:56:03PM -0400, Paul D. Smith wrote:
>Please don't dispair if I'm not as communicative as I usually am. For
>those not aware, in the "real world" I've decided to leave my previous
>position (of 13+ years!) and take on a new challenge. As a result,
>there is some turbulen
> Date: Thu, 17 Aug 2006 17:11:19 -0400
> From: "William A. Hoffman" <[EMAIL PROTECTED]>
>
> I obviously care that the patch gets done. What I do not care about is the
> style of the code in make. The issue here is should sh_chars_sh
> be directly referenced or not. I think it should not, Ch
> Date: Thu, 17 Aug 2006 16:43:49 -0400
> From: Christopher Faylor <[EMAIL PROTECTED]>
>
> This is even easier than I was thinking, really. If this value
> was defined in the appropriate pre-header file then an
>
> #ifndef PATH_SEPARATOR
> # define PATH_SEPARATOR ":"
> #endif
>
> in make.h woul
> From: "Paul D. Smith" <[EMAIL PROTECTED]>
> Cc: Eli Zaretskii <[EMAIL PROTECTED]>, Bill Hoffman <[EMAIL PROTECTED]>
> Date: Thu, 17 Aug 2006 16:56:03 -0400
>
> Please don't dispair if I'm not as communicative as I usually am. For
> those not aware, in the "real world" I've decided to leave my p
> Date: Thu, 17 Aug 2006 17:02:30 -0400
> From: Bill Hoffman <[EMAIL PROTECTED]>
>
> At 04:48 PM 8/17/2006, Christopher Faylor wrote:
>
> >I don't understand why MinGW's make should be using anything like /bin/sh.
> >Shouldn't it be using cmd.exe or command.com?
> >
> It seems that if it finds sh
At 04:56 PM 8/17/2006, Paul D. Smith wrote:
>Hi all;
>
>Please don't dispair if I'm not as communicative as I usually am. For
>those not aware, in the "real world" I've decided to leave my previous
>position (of 13+ years!) and take on a new challenge. As a result,
>there is some turbulence in my
At 04:30 PM 8/17/2006, Eli Zaretskii wrote:
>> Date: Thu, 17 Aug 2006 15:50:11 -0400
>> From: Bill Hoffman <[EMAIL PROTECTED]>
>>
>> >I'm not a make maintainer and don't really care about this one way or
>> >the other.
>> [...]
>> I am not a make maintainer either, and care even less than you.
>
>
> Date: Thu, 17 Aug 2006 16:31:21 -0400
> From: "William A. Hoffman" <[EMAIL PROTECTED]>
>
> From the cygwin shell the error is:
> c:/cygwin/bin/gcc.exe "a.c" "b.c"
> gcc: a.c b.c: No such file or directory
> gcc: no input files
> c:\hoffman\My Builds\CMakeDev\Tests\COnly\b\make.exe: *** [allgcc
> Date: Thu, 17 Aug 2006 16:22:20 -0400
> From: Bill Hoffman <[EMAIL PROTECTED]>
>
> #broken
> all:
> c:/Program\ Files/Microsoft\ Visual\ Studio\ .NET\ 2003/Vc7/bin/cl.exe
> "a.c" "b.c"
>
> #CreateProcess(C:\cygwin\bin\sh.exe,C:/cygwin/bin/sh.exe -c "c:/Program\
> Files/Microsoft\ Visua
At 04:48 PM 8/17/2006, Christopher Faylor wrote:
>I don't understand why MinGW's make should be using anything like /bin/sh.
>Shouldn't it be using cmd.exe or command.com?
>
>cgf
It seems that if it finds sh.exe in the path it uses it.
Remember the chars_sh and chars_dos thing that is switched a
Hi all;
Please don't dispair if I'm not as communicative as I usually am. For
those not aware, in the "real world" I've decided to leave my previous
position (of 13+ years!) and take on a new challenge. As a result,
there is some turbulence in my life at the moment and one consequence
of this is
On Thu, Aug 17, 2006 at 04:22:20PM -0400, Bill Hoffman wrote:
>As requested by Eli, I am posting the problems I am having with mingw-make
>from a cygwin command line.
>
>
>I narrowed down the major problem with mingw make and my makefiles.
>Looks like a process launching issue. If the files are do
On Thu, Aug 17, 2006 at 11:30:53PM +0300, Eli Zaretskii wrote:
>> Date: Thu, 17 Aug 2006 15:50:11 -0400
>> From: Bill Hoffman <[EMAIL PROTECTED]>
>>
>> >I'm not a make maintainer and don't really care about this one way or
>> >the other.
>> [...]
>> I am not a make maintainer either, and care even
On Thu, Aug 17, 2006 at 11:09:31PM +0300, Eli Zaretskii wrote:
>> Date: Thu, 17 Aug 2006 13:50:49 -0400
>> From: Christopher Faylor <[EMAIL PROTECTED]>
>>
>> >The Cygwin build could (and probably should) use configure.in, but the
>> >MinGW and MSVC ports don't use the configure script to build
>>
> Date: Thu, 17 Aug 2006 13:21:31 -0400
> From: Christopher Faylor <[EMAIL PROTECTED]>
> Cc:
>
> It does make me wonder what kind of quoting problems we'd see with
> HAVE_DOS_PATHS, though. On cygwin, I wouldn't want every backslash to
> be interpreted as part of a path name "just in case".
If
At 04:22 PM 8/17/2006, Bill Hoffman wrote:
>As requested by Eli, I am posting the problems I am having with mingw-make
>from a cygwin command line.
>
>
>I narrowed down the major problem with mingw make and my makefiles.
>Looks like a process launching issue. If the files are double quoted
>and pa
> Date: Thu, 17 Aug 2006 15:50:11 -0400
> From: Bill Hoffman <[EMAIL PROTECTED]>
>
> >I'm not a make maintainer and don't really care about this one way or
> >the other.
> [...]
> I am not a make maintainer either, and care even less than you.
Sorry, Bill, you lost me here: I thought you _did_ ca
As requested by Eli, I am posting the problems I am having with mingw-make
from a cygwin command line.
I narrowed down the major problem with mingw make and my makefiles.
Looks like a process launching issue. If the files are double quoted
and passed to a full path command it passes both files a
> Date: Thu, 17 Aug 2006 15:49:46 -0400
> From: Earnie Boyd <[EMAIL PROTECTED]>
>
> Quoting Eli Zaretskii <[EMAIL PROTECTED]>:
>
> >
> > The Cygwin build could (and probably should) use configure.in, but the
> > MinGW and MSVC ports don't use the configure script to build
> > themselves, and so t
> Date: Thu, 17 Aug 2006 13:50:49 -0400
> From: Christopher Faylor <[EMAIL PROTECTED]>
>
> >The Cygwin build could (and probably should) use configure.in, but the
> >MinGW and MSVC ports don't use the configure script to build
> >themselves, and so the native builds cannot set PATH_SEPARATOR_CHAR
At 01:21 PM 8/17/2006, Christopher Faylor wrote:
>On Thu, Aug 17, 2006 at 12:38:29PM -0400, Bill Hoffman wrote:
>>At 11:42 AM 8/17/2006, Christopher Faylor wrote:
>>>On Thu, Aug 17, 2006 at 10:23:35AM -0400, Bill Hoffman wrote
>
>I'm not a make maintainer and don't really care about this one way or
Quoting Eli Zaretskii <[EMAIL PROTECTED]>:
The Cygwin build could (and probably should) use configure.in, but the
MinGW and MSVC ports don't use the configure script to build
themselves, and so the native builds cannot set PATH_SEPARATOR_CHAR
there.
For MinGW, it can use configure if the MSY
On Thu, Aug 17, 2006 at 01:42:53PM -0400, Eli Zaretskii wrote:
>> Date: Thu, 17 Aug 2006 12:38:29 -0400
>> From: Bill Hoffman <[EMAIL PROTECTED]>
>>
>> >> /* Handle other OSs. */
>> >>! #if defined(HAVE_DOS_PATHS) && !defined(__CYGWIN__)
>> >> # define PATH_SEPARATOR_CHAR ';'
>> >> #elif defin
On Thu, Aug 17, 2006 at 12:38:29PM -0400, Bill Hoffman wrote:
>At 11:42 AM 8/17/2006, Christopher Faylor wrote:
>>On Thu, Aug 17, 2006 at 10:23:35AM -0400, Bill Hoffman wrote:
>>
>>
>>>if (p[1] != '\\' && p[1] != '\''
>>>&& !isspace ((unsigned char)p[1])
On Thu, Aug 17, 2006 at 10:23:35AM -0400, Bill Hoffman wrote:
>At 11:40 PM 8/16/2006, Christopher Faylor wrote:
>>I don't understand why isn't this just using the UNIX-ish settings for
>>Cygwin. The settings should, at the very least, be the same as the
>>UNIX-sh case.
>
>Because there was a bug w
On Thu, Aug 17, 2006 at 06:24:03AM +0300, Eli Zaretskii wrote:
>> Date: Wed, 16 Aug 2006 21:21:21 -0400
>> From: Bill Hoffman <[EMAIL PROTECTED]>
>>
>> *** make-3.81/job.c Sun Mar 19 22:03:04 2006
>> --- ../make-3.81/job.c Wed Aug 16 19:42:14 2006
>> *** construct_command_argv_int
> Date: Thu, 17 Aug 2006 12:38:29 -0400
> From: Bill Hoffman <[EMAIL PROTECTED]>
>
> >> /* Handle other OSs. */
> >>! #if defined(HAVE_DOS_PATHS) && !defined(__CYGWIN__)
> >> # define PATH_SEPARATOR_CHAR ';'
> >> #elif defined(VMS)
> >> # define PATH_SEPARATOR_CHAR ','
> >
> >This is probably
At 11:42 AM 8/17/2006, Christopher Faylor wrote:
>On Thu, Aug 17, 2006 at 10:23:35AM -0400, Bill Hoffman wrote:
>
>
>>if (p[1] != '\\' && p[1] != '\''
>>&& !isspace ((unsigned char)p[1])
>>! && strchr (sh_chars, p[1]) == 0)
>>
At 11:40 PM 8/16/2006, Christopher Faylor wrote:
>I don't understand why isn't this just using the UNIX-ish settings for
>Cygwin. The settings should, at the very least, be the same as the
>UNIX-sh case.
Because there was a bug where sh_chars_sh was being directly referenced if
HAVE_DOS_PATHS wa
36 matches
Mail list logo
