Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com Message-ID: <3A5E3F3A.C10EE670@cpsc.ucalgary.ca> Date: Thu, 11 Jan 2001 15:18:18 -0800 From: Mark Tigges Reply-To: mtigges AT cpsc DOT ucalgary DOT ca Organization: nobody X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.16 i686) X-Accept-Language: en MIME-Version: 1.0 To: "Larry Hall (RFK Partners, Inc)" CC: cygwin AT cygwin DOT com Subject: Re: CR/LF problems, References: <4 DOT 3 DOT 1 DOT 2 DOT 20010111175843 DOT 022750f8 AT pop DOT ma DOT ultranet DOT com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit "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 AT rfk DOT 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