CR/LF problems,

CR/LF problems,

[Mark Tigges]

Hi,

I just upgraded my cygwin to the latest version in order to 
satisfy xemacs requirements.

Unfortunately now I am completely unable to make cygwin in 
anyway not perform \r\n translation.

This is critical since any Makefile's created in cygwin will not
work in unix.

The relevant mount is mounted as binary:
Device              Directory           Type         Flags
\\cardano\anm       /anm                user         binmode
d:\bin              /usr/bin            system       binmode
d:\lib              /usr/lib            system       binmode
d:                  /                   system       binmode

and when I installed I checked "Unix" as the default text file
mode.  However, as I said it seems to have no effect (I have tried
both tty and binmode in the CYGWIN variable (also  CYGWIN32 as I
saw sporadic mention of it in the user guide as well)).

I am at a complete loss as to what is causing the problem.  If 
anybody knows how to effectively eradicate any \r\n translation
I would be hugely appreciated to be enlightened.

Thanks,

Mark.

--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple

Re: CR/LF problems,

[Larry Hall (RFK Partners, Inc)]

At 05:05 PM 1/11/2001, Mark Tigges wrote:
>Hi,
>
>I just upgraded my cygwin to the latest version in order to 
>satisfy xemacs requirements.
>
>Unfortunately now I am completely unable to make cygwin in 
>anyway not perform \r\n translation.
>
>This is critical since any Makefile's created in cygwin will not
>work in unix.
>
>The relevant mount is mounted as binary:
>Device              Directory           Type         Flags
>\\cardano\anm       /anm                user         binmode
>d:\bin              /usr/bin            system       binmode
>d:\lib              /usr/lib            system       binmode
>d:                  /                   system       binmode
>
>and when I installed I checked "Unix" as the default text file
>mode.  However, as I said it seems to have no effect (I have tried
>both tty and binmode in the CYGWIN variable (also  CYGWIN32 as I
>saw sporadic mention of it in the user guide as well)).
>
>I am at a complete loss as to what is causing the problem.  If 
>anybody knows how to effectively eradicate any \r\n translation
>I would be hugely appreciated to be enlightened.
>
>Thanks,
>
>Mark.



Its hard to tell what's wrong without knowing what you're doing.  Still,
from what you've provided, your mounts look fine, which means if some app
writes without binary specified, you should see the resulting file as 
binary.  The mounts don't protect you from those apps that write in text 
mode.  Perhaps that's your problem?  Output of cygcheck -s -r -v might 
be helpful to you but I'm left with the impression that the trouble lies
elsewhere...

tty and binmode settings no affect on file modes.  CYGWIN32 is an old 
reference to the now named CYGWIN environment variable.  Setting CYGWIN32
to anything will have no affect.



Larry Hall                              lhall@rfk.com
RFK Partners, Inc.                      http://www.rfk.com
118 Washington Street                   (508) 893-9779 - RFK Office
Holliston, MA 01746                     (508) 893-9889 - FAX



--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple

Re: CR/LF problems,

[Mark Tigges]

"Larry Hall (RFK Partners, Inc)" wrote:
> 
> At 05:05 PM 1/11/2001, Mark Tigges wrote:
> >Hi,
> >
> >I just upgraded my cygwin to the latest version in order to
> >satisfy xemacs requirements.
> >
> >Unfortunately now I am completely unable to make cygwin in
> >anyway not perform \r\n translation.
> >
> >This is critical since any Makefile's created in cygwin will not
> >work in unix.
> >
> >The relevant mount is mounted as binary:
> >Device              Directory           Type         Flags
> >\\cardano\anm       /anm                user         binmode
> >d:\bin              /usr/bin            system       binmode
> >d:\lib              /usr/lib            system       binmode
> >d:                  /                   system       binmode
> >
> >and when I installed I checked "Unix" as the default text file
> >mode.  However, as I said it seems to have no effect (I have tried
> >both tty and binmode in the CYGWIN variable (also  CYGWIN32 as I
> >saw sporadic mention of it in the user guide as well)).
> >
> >I am at a complete loss as to what is causing the problem.  If
> >anybody knows how to effectively eradicate any \r\n translation
> >I would be hugely appreciated to be enlightened.
> >
> >Thanks,
> >
> >Mark.
> 
> Its hard to tell what's wrong without knowing what you're doing.  Still,
> from what you've provided, your mounts look fine, which means if some app
> writes without binary specified, you should see the resulting file as
> binary.  The mounts don't protect you from those apps that write in text
> mode.  Perhaps that's your problem?  Output of cygcheck -s -r -v might
> be helpful to you but I'm left with the impression that the trouble lies
> elsewhere...

The trouble lies everywhere, I use 'cat > filename' or xemacs, or
(cygwin compiled posix) python scripts that programmatically create
files (like Makefile) that all have \r\n, this behaviour does not
match the behaviour of the previous installation of cygwin that I 
had (I believe 1.0), that's why I am so frustrated.

Is there no way to force cygwin to the behaviour that I grew used to.

Our automatically generated Makefile's are only useable under cygnus
with this behaviour - something that is not acceptable.

Cheers,
Mark.

> 
> tty and binmode settings no affect on file modes.  CYGWIN32 is an old
> reference to the now named CYGWIN environment variable.  Setting CYGWIN32
> to anything will have no affect.
> 
> Larry Hall                              lhall@rfk.com
> RFK Partners, Inc.                      http://www.rfk.com
> 118 Washington Street                   (508) 893-9779 - RFK Office
> Holliston, MA 01746                     (508) 893-9889 - FAX

--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple

Re: CR/LF problems,

[Larry Hall (RFK Partners, Inc)]

At 06:18 PM 1/11/2001, Mark Tigges wrote:
> > Its hard to tell what's wrong without knowing what you're doing.  Still,
> > from what you've provided, your mounts look fine, which means if some app
> > writes without binary specified, you should see the resulting file as
> > binary.  The mounts don't protect you from those apps that write in text
> > mode.  Perhaps that's your problem?  Output of cygcheck -s -r -v might
> > be helpful to you but I'm left with the impression that the trouble lies
> > elsewhere...
>
>The trouble lies everywhere, I use 'cat > filename' or xemacs, or
>(cygwin compiled posix) python scripts that programmatically create
>files (like Makefile) that all have \r\n, this behaviour does not
>match the behaviour of the previous installation of cygwin that I 
>had (I believe 1.0), that's why I am so frustrated.
>
>Is there no way to force cygwin to the behaviour that I grew used to.
>
>Our automatically generated Makefile's are only useable under cygnus
>with this behaviour - something that is not acceptable.


"cat > filename" where the file system "filename" is in is mounted binary 
works fine for me.  You're going to have to do some debugging to determine
why you see this problem.  Someone might be able to help some with the 
output of cygcheck -s -r -v and an exact description of the problem (or you
might be able to spot it yourself!;-))  The devil is in the details, always.




Larry Hall                              lhall@rfk.com
RFK Partners, Inc.                      http://www.rfk.com
118 Washington Street                   (508) 893-9779 - RFK Office
Holliston, MA 01746                     (508) 893-9889 - FAX



--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple

Re: CR/LF problems,

[Earnie Boyd]

Mark Tigges wrote:
>  
> and when I installed I checked "Unix" as the default text file
> mode.  However, as I said it seems to have no effect (I have tried
> both tty and binmode in the CYGWIN variable (also  CYGWIN32 as I
> saw sporadic mention of it in the user guide as well)).
> 
> I am at a complete loss as to what is causing the problem.  If
> anybody knows how to effectively eradicate any \r\n translation
> I would be hugely appreciated to be enlightened.
> 

I'm at a complete loss too.  What shell are you using?  Send the output
of `cygcheck -s -r -v' to the list.

Cheers,
Earnie.

__________________________________________________
Do You Yahoo!?
Talk to your friends online with Yahoo! Messenger.
http://im.yahoo.com

--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple

Re: CR/LF problems,

[mark]

On 11 Jan, Earnie Boyd wrote:
> Mark Tigges wrote:
>>  
>> and when I installed I checked "Unix" as the default text file
>> mode.  However, as I said it seems to have no effect (I have tried
>> both tty and binmode in the CYGWIN variable (also  CYGWIN32 as I
>> saw sporadic mention of it in the user guide as well)).
>> 
>> I am at a complete loss as to what is causing the problem.  If
>> anybody knows how to effectively eradicate any \r\n translation
>> I would be hugely appreciated to be enlightened.
>> 
> 
> I'm at a complete loss too.  What shell are you using?  Send the output
> of `cygcheck -s -r -v' to the list.
> 

Thanks for the help.  I am using the standard shell that
one gets when executing the cygwin.bat, which seems to be bash.

I attached the cygcheck output.


Thanks again,
Mark.

Re: CR/LF problems,

[Larry Hall (RFK Partners, Inc)]

At 06:25 PM 1/11/2001, mark@numericalmethods.com wrote:
>On 11 Jan, Earnie Boyd wrote:
> > Mark Tigges wrote:
> >>  
> >> and when I installed I checked "Unix" as the default text file
> >> mode.  However, as I said it seems to have no effect (I have tried
> >> both tty and binmode in the CYGWIN variable (also  CYGWIN32 as I
> >> saw sporadic mention of it in the user guide as well)).
> >> 
> >> I am at a complete loss as to what is causing the problem.  If
> >> anybody knows how to effectively eradicate any \r\n translation
> >> I would be hugely appreciated to be enlightened.
> >> 
> > 
> > I'm at a complete loss too.  What shell are you using?  Send the output
> > of `cygcheck -s -r -v' to the list.
> > 
>
>Thanks for the help.  I am using the standard shell that
>one gets when executing the cygwin.bat, which seems to be bash.
>
>I attached the cygcheck output.
>
>
>Thanks again,
>Mark.



The only problem I can see is you have a copy of cygwin1.dll in 
c:\winnt\system32.  Get it out of there.  What command shows you the 
problem?  Can you give a reproducible case?



Larry Hall                              lhall@rfk.com
RFK Partners, Inc.                      http://www.rfk.com
118 Washington Street                   (508) 893-9779 - RFK Office
Holliston, MA 01746                     (508) 893-9889 - FAX



--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple

Re: CR/LF problems,

[mark]

On 11 Jan, Larry Hall (RFK Partners, Inc) wrote:
> At 06:25 PM 1/11/2001, mark@numericalmethods.com wrote:
>>On 11 Jan, Earnie Boyd wrote:
>> > Mark Tigges wrote:
>> >>  
>> >> and when I installed I checked "Unix" as the default text file
>> >> mode.  However, as I said it seems to have no effect (I have tried
>> >> both tty and binmode in the CYGWIN variable (also  CYGWIN32 as I
>> >> saw sporadic mention of it in the user guide as well)).
>> >> 
>> >> I am at a complete loss as to what is causing the problem.  If
>> >> anybody knows how to effectively eradicate any \r\n translation
>> >> I would be hugely appreciated to be enlightened.
>> >> 
>> > 
>> > I'm at a complete loss too.  What shell are you using?  Send the output
>> > of `cygcheck -s -r -v' to the list.
>> > 
>>
>>Thanks for the help.  I am using the standard shell that
>>one gets when executing the cygwin.bat, which seems to be bash.
>>
>>I attached the cygcheck output.
>>
>>
>>Thanks again,
>>Mark.
> 
> 
> 
> The only problem I can see is you have a copy of cygwin1.dll in 
> c:\winnt\system32.  Get it out of there.  What command shows you the 
> problem?  Can you give a reproducible case?
> 
> 
> 

There was some reason why I put it there before, but I can't remember
what it was.  Anyhow I erased it and it did not solve the problem.  I
made sure that I copied the new one in today when I upgraded cygwin.

All which I have tried have yielded negative results.

I programatically create files through a cygwin compiled python.
I 'cat > filename' a file (with new lines)
I create files with an editor (tried both xemacs and emacs)

All cases always create files with '\r\n'

Sorry to uninterested subscribers for creating undue amounts of traffic.

Cheers,
Mark.


--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple

Re: CR/LF problems,

[Earnie Boyd]

mark@numericalmethods.com wrote:
> 
> 
> Thanks for the help.  I am using the standard shell that
> one gets when executing the cygwin.bat, which seems to be bash.
> 
> I attached the cygcheck output.
> 

> HOME = `//cardano/mark'

Your use of //cardano is what is being processed in textmode.  The
easiest solution is going to be to mount //cardano in binary mode
something like this
  mkdir /cardano
  mount -b //cardano /cardano
Then, modify the occurrences in the environment from //cardano to
/cardano.

HTH,
Earnie.

__________________________________________________
Do You Yahoo!?
Talk to your friends online with Yahoo! Messenger.
http://im.yahoo.com

--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple