Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Message-Id: <4.3.1.2.20021001222019.02328a70@pop.rcn.com> X-Sender: lhall AT pop DOT rcn DOT com Date: Tue, 01 Oct 2002 22:21:37 -0400 To: "Kris Warkentin" , "Dan Vasaru" , From: "Larry Hall (RFK Partners, Inc)" Subject: Re: CR/NL problem with cpp.exe In-Reply-To: <01e501c26988$cd4587f0$b6010c0a@catdog> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Maybe Cygwin's version was linked with textmode.o or automode.o and yours isn't. Larry Hall lhall AT rfk DOT com RFK Partners, Inc. http://www.rfk.com 838 Washington Street (508) 893-9779 - RFK Office Holliston, MA 01746 (508) 893-9889 - FAX At 04:26 PM 10/1/2002, Kris Warkentin wrote: >I'm actually quite certain that what you wrote would help. The issue is >that cccp.c (the gcc preprocessor) does not do that and, as near as I can >tell from the FAQ, shouldn't need to. That, however, is where I might be >wrong. I'm wondering if the cpp shipped with Cygwin has been patched so >that it does explicitly open files as text. If that's the case, then that >might explain why I'm seeing different behaviour. > >Aha! I just copied dosfile.c to a text mode partition and it works with our >preprocessor. That implies that there must be some buggery in the Cygwin >version of cpp.exe. I noticed that the version of gcc shipped with cygwin >is 2.95.3-5. Is the '-5' some form of Cygwin specific patch with some >assorted magic in it? Perhaps someone on this list would know. > >cheers, > >Kris > >----- Original Message ----- >From: "Dan Vasaru" >To: "Kris Warkentin" >Sent: Tuesday, October 01, 2002 4:18 PM >Subject: RE: CR/NL problem with cpp.exe > > > > Sorry about that, I set out to write a longer reply (which I posted to the > > group) and typed CTRL+ENTER just as I got started. > > > > If what I wrote to the group doesn't help, (opening your files with >O_TEXT, > > and setting stdin to textmode), then I believe you have a problem. > > 1. What type are your mounts (where your c files reside) > > 2. What is the value of the CYGWIN variable ? > > > > Dan > > -----Original Message----- > > From: Kris Warkentin [mailto:kewarken AT qnx DOT com] > > Sent: Tuesday, October 01, 2002 10:04 PM > > To: Dan Vasaru > > Subject: Re: CR/NL problem with cpp.exe > > > > > > ----- Original Message ----- > > From: "Dan Vasaru" > > To: "Kris Warkentin" > > Sent: Tuesday, October 01, 2002 3:48 PM > > Subject: RE: CR/NL problem with cpp.exe > > > > > > > Kris, > > > > > > Please refer to this section of the FAQ: > > > > > > > Which section? I've read the CR/NL sections of the FAQ and I believe I > > understand the issue at hand. > > > > 1) Two versions of cpp.exe, both compiled under cygwin, both running under > > same environment with the same input from the same filesystem. > > 2) The code for cpp.exe doesn't do anything special but rather just checks > > for '\\' '\n' at the end of a line. > > 3) The cpp.exe shipped with Cygwin works fine - input translation takes > > place just as the FAQ states - the open() call opens them in O_TEXT mode. > > 4) The cpp.exe that we built does not get the benefit of this input > > translation. > > > > As near as I can tell, our cpp.exe should 'just work' and yet it doesn't. > > Any suggestions? > > > > cheers, > > > > Kris > > > > > > >-- >Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple >Bug reporting: http://cygwin.com/bugs.html >Documentation: http://cygwin.com/docs.html >FAQ: http://cygwin.com/faq/ -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/