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, earnie_boyd at yahoo dot com
- Subject: Re: make, bash, or cygwin bug?
- From: "Kai Henningsen" <kai at cats dot ms>
- Date: Fri, 8 Oct 1999 15:23:16 +0200
- Organization: Spuentrup CTI
On 8 Oct 99, at 5:01, Earnie Boyd wrote:
> --- Kai Henningsen <firstname.lastname@example.org> wrote:
> > /bin/sh: \home\gcc-2.95.1\kai\gcc\cc1obj.exe^M: command not
> > found
> > Well, of course. But who told you to append a cr there?
> You did.
> > 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.
Device Directory Type Flags
E: / user textmode
f: /f user textmode
(This was on E:.)
I don't think so.
Regards - Kai Henningsen
Spuentrup CTI Fon: +49 251 322311 0
Windbreede 12 Fax: +49 251 322311 99
D-48157 Münster Mob: +49 161 3223111
Germany GSM: +49 171 7755060
Want to unsubscribe from this list?
Send a message to email@example.com