Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT sourceware DOT cygnus DOT com>
List-Archive:	<http://sourceware.cygnus.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT sourceware DOT cygnus DOT com>
List-Help:	<mailto:cygwin-help AT sourceware DOT cygnus DOT com>, <http://sourceware.cygnus.com/ml/#faqs>
Sender:	cygwin-owner AT sourceware DOT cygnus DOT com
Delivered-To:	mailing list cygwin AT sourceware DOT cygnus DOT com
Message-ID:	<389F392A.A99DA3BA@openmarket.com>
Date:	Mon, 07 Feb 2000 16:29:14 -0500
From:	"Guy T. Moore Jr." <gmoore AT openmarket DOT com>
Organization:	Engineering
X-Mailer:	Mozilla 4.61 [en] (WinNT; I)
X-Accept-Language:	en
MIME-Version:	1.0
To:	cygwin AT sourceware DOT cygnus DOT com
Subject:	Re: clearmake and cywin b20 and \r\n on NT
References:	<20000207203046 DOT 22646 DOT qmail AT web107 DOT yahoomail DOT com> <20000207155839 DOT A11986 AT cygnus DOT com>

> Actually, it looks like a "\r\n" line ending problem to me.  It's probably trying
> to run "\r" as a program.

Actually, after saving the output and doing an octal dump of it,it
is trying to run "pwd\r" as a program. The correct error message is:

pwd\r : not found

I definitely do not have any \r in my makefile.
Seems like clearmake is adding that in whether or not my lines in \r or \r\n

I am going back to CLearCase support with this info.

Chris Faylor wrote:
> 
> On Mon, Feb 07, 2000 at 12:30:46PM -0800, Earnie Boyd wrote:
> >--- "Guy T. Moore Jr." <gmoore AT openmarket DOT com> wrote:
> >>
> >> What was the exact answer to using Clearmake and Cygwin b20
> >> on the WinNT platform?
> >>
> >> I just tried:
> >> CYGWIN=nobinmode
> >> but that did not help running clearmake.
> >>
> >> I still get,
> >> : not found
> >>
> >
> >This is definately a message coming from the ash port.  I see it most commonly
> >when some command can't be executed via sh when trying to use it from a
> >non-Cygwin program.  Is Clearmake OpenSource?  Can you rebuild it using Cygwin?
> >Rebuilding with Cygwin would be the best solution.  If you can't do that, try:
> >
> >cp sh.exe ash.exe
> >cp bash.exe sh.exe
> >
> >This will give you a different message that may help determine the real problem
> >which I suspect to be pathing issues related to Cygwin vs non-Cygwin paths.
> 
> Actually, it looks like a "\r\n" line ending problem to me.  It's probably trying
> to run "\r" as a program.
> 
> cgf

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

- Raw text -