Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
Sender: cygwin-owner AT sourceware DOT cygnus DOT com
Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com
Message-Id: <199903170620.AAA05167@modi.xraylith.wisc.edu>
X-Authentication-Warning: modi.xraylith.wisc.edu: localhost.xraylith.wisc.edu [127.0.0.1] didn't use HELO protocol
To: tjump AT tertius DOT com
cc: cygwin AT sourceware DOT cygnus DOT com
Subject: Re: [ANN] EGCS-1.1.2 binaries for Cygwin b20.1 available 
In-reply-to: Your message of "Wed, 17 Mar 1999 05:37:21 GMT."
             <36ef3b5d DOT 2548875 AT smtp DOT tertius DOT com> 
Date: Wed, 17 Mar 1999 00:20:15 -0600
From: Mumit Khan <khan AT xraylith DOT wisc DOT EDU>

tjump AT tertius DOT com (Theodore Jump) writes:
> 
> Mumit,
> 
> I want to thank you for your work, but I've a quirk I can't quite figure out
> preventing me from using the new release for Cygwin code builds.
> 
> Basically, it appears that 'as' is being called with an incomplete command li
> ne
> in that it's not being fed a proper file name (it's being fed a ^M as the fil
> e
> name), thus the build of even a trivial file fails, e.g.: g++ test.cc
> 
> I tried this altering the state of my CYGWIN env-var, removing either and bot
> h
> of 'tty' and 'binmode' but this did not change the behavior at all.
> 
> Building either a C or CPP file results in build failure, I have not tested
> other types.  The same build error occurs if I'm trying to generate an .o fil
> e
> or a .exe file.
> 
> The error reported is:
> 
>     Assembler messages:
>      for reading.open
>     : No such file or directory
> 
> ... and occurs with or without the '-save-temps' option.

Yikes! I have no idea what may be causing this! I'm travelling until
Sunday and have no way to checking/fixing, but will do as soon as I
return.

When you added/removed the CYGWIN values (binmode, tty, etc), did you
restart bash? All this should work irrespective of mount types, so even 
if it does, there's still a nasty bug in there somewhere. And it should
also work correctly from CMD shell. 

And I was hoping that this was going to be the best tested release yet. 
Sigh. This is also the first released built natively, so I'll try my
usual canadian-cross build and see if that solves your problem or not.

Regards,
Mumit


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com