clearmake and cywin b20 and \r\n on NT

clearmake and cywin b20 and \r\n on NT

[Guy T. Moore Jr.]

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

on most commands in my rules.
(The last word of every command gets munged as clearmake passes it to the Cygnus sh.exe.)

Guy Moore 
OpenMarket

I couldn't find all the threads to this discussion at the cygnus.com site
so I'm sending this email to all the related parties.

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

RE: clearmake and cywin b20 and \r\n on NT

[Masterson, David]

Hmmm.  This suggests that it should be possible to write a simple SHELL
wrapper program that strips CR from the end of lines before passing it to
the real shell.  Then you could set the SHELL variable to this wrapper
program.

Does that make sense...?

-----Original Message-----
From: Guy T. Moore Jr. [ mailto:gmoore@openmarket.com ]
Sent: Tuesday, February 08, 2000 9:17 AM
To: Masterson, David
Cc: cygwin@sourceware.cygnus.com
Subject: Re: clearmake and cywin b20 and \r\n on NT


Using the 'make' that is supplied with the Cygwin installation works fine.

clearmake works fine also if I do not set the SHELL variable in the
makefile. 
	i.e.: using the standard DOS shell rather than the sh.exe that is
supplied with Cygnus.
    ALthough commands like 'pwd' are not understood by the DOS shell, etc...

"Masterson, David" wrote:
> 
> Have you tried the same thing using straight GNU make?  I'm not suggesting
> you switch to GNU make rather merely run a test with GNU make to see if it
> has the same problem...
> 
> -----Original Message-----
> From: Guy T. Moore Jr. [ mailto:gmoore@openmarket.com ]
> Sent: Monday, February 07, 2000 1:29 PM
> To: cygwin@sourceware.cygnus.com
> Subject: Re: clearmake and cywin b20 and \r\n on NT
> 
> > 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@openmarket.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@sourceware.cygnus.com

Re: clearmake and cywin b20 and \r\n on NT

[Guy T. Moore Jr.]

Using the 'make' that is supplied with the Cygwin installation works fine.

clearmake works fine also if I do not set the SHELL variable in the makefile. 
	i.e.: using the standard DOS shell rather than the sh.exe that is supplied with Cygnus.
    ALthough commands like 'pwd' are not understood by the DOS shell, etc...

"Masterson, David" wrote:
> 
> Have you tried the same thing using straight GNU make?  I'm not suggesting
> you switch to GNU make rather merely run a test with GNU make to see if it
> has the same problem...
> 
> -----Original Message-----
> From: Guy T. Moore Jr. [ mailto:gmoore@openmarket.com ]
> Sent: Monday, February 07, 2000 1:29 PM
> To: cygwin@sourceware.cygnus.com
> Subject: Re: clearmake and cywin b20 and \r\n on NT
> 
> > 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@openmarket.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@sourceware.cygnus.com

RE: clearmake and cywin b20 and \r\n on NT

[Masterson, David]

Have you tried the same thing using straight GNU make?  I'm not suggesting
you switch to GNU make rather merely run a test with GNU make to see if it
has the same problem...

-----Original Message-----
From: Guy T. Moore Jr. [ mailto:gmoore@openmarket.com ]
Sent: Monday, February 07, 2000 1:29 PM
To: cygwin@sourceware.cygnus.com
Subject: Re: clearmake and cywin b20 and \r\n on NT


> 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@openmarket.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@sourceware.cygnus.com

Re: clearmake and cywin b20 and \r\n on NT

[Guy T. Moore Jr.]

> 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@openmarket.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@sourceware.cygnus.com

RE: clearmake and cywin b20 and \r\n on NT

[Christopher Jones]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 903 bytes --]

Title: RE: clearmake and cywin b20  and \r\n on NT





You may need to check your clearcase view to see if you're using dos interoperability crap or not.  This controls line endings on windows in a view (in some weird way) for most files.  

Brian


> -----Original Message-----
> From: Chris Faylor [ mailto:cgf@cygnus.com ]
> Sent: Monday, February 07, 2000 3:59 PM
> To: Earnie Boyd
> Cc: Guy T. Moore Jr.; cygwin@sourceware.cygnus.com;
> aleherbauer@takefive.co.at
> Subject: Re: clearmake and cywin b20 and \r\n on NT
> 
> 
> On Mon, Feb 07, 2000 at 12:30:46PM -0800, Earnie Boyd wrote:
> >--- "Guy T. Moore Jr." <gmoore@openmarket.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
> >> 
> >

Re: clearmake and cywin b20 and \r\n on NT

[Chris Faylor]

On Mon, Feb 07, 2000 at 12:30:46PM -0800, Earnie Boyd wrote:
>--- "Guy T. Moore Jr." <gmoore@openmarket.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@sourceware.cygnus.com

Re: clearmake and cywin b20 and \r\n on NT

[Earnie Boyd]

--- "Guy T. Moore Jr." <gmoore@openmarket.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.

Regards,
 

=====
Earnie Boyd < mailto:earnie_boyd@yahoo.com >
Cygwin Newbies, please visit
< http://www.freeyellow.com/members5/gw32/index.html >
__________________________________________________
Do You Yahoo!?
Talk to your friends online with Yahoo! Messenger.
http://im.yahoo.com

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