Make --win32 shell bug?

[Chris Faylor]

On Tue, Oct 17, 2000 at 09:19:32PM -0600, Scott Carter wrote:
>Like Chris, if I run the makefile, exactly as shown, I get the "unterminated
>call" error. However, if I modify the makefile to something that makes
>sense, i.e.
>---------------------------------------------------------------------------
>OBJLST := $(shell echo \
>xxx)
>---------------------------------------------------------------------------
>(note the backslash at the end of the first line), then I get the
>"STATUS_ACCESS_VIOLATION" error that Anshil cited. Was the missing backslash
>perhaps a typo in the email? Without the backslash, the "unterminated call"
>error seems appropriate. But with the backslash, the
>"STATUS_ACCESS_VIOLATION" error seems inappropriate -- perhaps that is the
>'bug' that Anshil was trying to ask about.
>
>I'm running make 3.79-3 on cygwin 1.1.2.

The latest make is 3.79.1-1.

My version doesn't get a STATUS_ACCESS_VIOLATION with this file, even if I
add a backslash.

cgf

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com