This is the mail archive of the
mailing list for the Cygwin project.
Re: make, bash, or cygwin bug?
- To: Kai Henningsen <kai at cats dot ms>, cygwin at sourceware dot cygnus dot com
- Subject: Re: make, bash, or cygwin bug?
- From: Earnie Boyd <earnie_boyd at yahoo dot com>
- Date: Fri, 8 Oct 1999 05:01:46 -0700 (PDT)
- Reply-To: earnie_boyd at yahoo dot com
--- Kai Henningsen <email@example.com> wrote:
> /bin/sh: \home\gcc-2.95.1\kai\gcc\cc1obj.exe^M: command not
> Well, of course. But who told you to append a cr there?
> This Makefile line:
> CC1OBJ = `$(CC) -print-prog-name=cc1obj`
> Someone obviously didn't understand that a cr counts as white
> space, just like a lf does. I have no idea if that's a fault of make,
> bash, or the cygwin1.dll.
Or your setup!! You've obviously modified your mounts to process text in
binary default mode. When this happens you must change the \r\n line endings
to \n line endings just as if you were on a UNIX platform.
And _NO_ cr does not count as white space, it is a specially handled character
when processing in "Text Mode".
Earnie Boyd <mailto:firstname.lastname@example.org>
Newbies, please visit
(If you respond to the list, then please don't cc me)
Do You Yahoo!?
Bid and sell for free at http://auctions.yahoo.com
Want to unsubscribe from this list?
Send a message to email@example.com