With the latest version of cygwin, the windows '&' command separators no
longer work at all unless you use "make --win32", which I guess is logical.
I have confirmed that if you use the --win32 make flag using the latest
cygwin, you will see the failure. Running "make --win32 fail" fails, but
running "make --win32 ok1" works fine.
Jer.
Jeremy Broughton
Staff Software Developer
Windows Team Lead, IBM DB2 Development Infrastructure
Home Office: 403-210-1614, Voice Mail: 905-413-3983
e-mail: [EMAIL PROTECTED]
Christopher
Faylor
<cgf-no-personal- To
[EMAIL PROTECTED] [EMAIL PROTECTED]
in.com> cc
11/16/2004 03:30 Subject
PM Re: ampersand at character 2048 in
a command is lost in make
Please respond to
cygwin
On Tue, Nov 16, 2004 at 04:56:51PM -0500, Jeremy Broughton wrote:
>Using cygwin 1.3.10 and 1.5.7, if an '&' ampersand character appears at
>character 2048 of a makefile command, the ampersand is lost from the
>command. If white-space is manipulated to move the & one character
>forward or backward in the makefile command, everything works fine.
>
>I have attached a testcase makefile below that reproduces the problem
>with simple makefile echo commands. Run "make fail" to see the failing
>case when an ampersand is at character 2048. Run "make ok1" and "make
>ok2" to see the same command succeed if the ampersand is shifted one
>character left or right respectively. Run "make ok3" to see the same
>command succeed if character 2048 appears in the middle of the echo
>command.
>
>(See attached file: makefile)
I tried this with the current version of cygwin and make and the output
from fail and ok1 was identical. I tried on both textmode and binmode
mounts (not that that should make a difference).
cgf
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
