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: <00f201c26976$2d4020b0$b6010c0a@catdog> From: "Kris Warkentin" To: Subject: CR/NL problem with cpp.exe Date: Tue, 1 Oct 2002 14:13:00 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Hello, Our Windows hosted development tools are compiled under Cygwin and I'm observing a strange problem with Dos style text files not being pre-processed correctly. Specifically, something like this: printf("This is a long string across\ multiple lines"); or a backslashified #define is being concatenated. Now, if I use the Cygwin cpp.exe, I get the following (expected) behaviour: cpp.exe dosfile.c # works fine - cygwin.dll does input translation cpp.exe < dosfile.c # doesn't work since shell isn't doing input translation However with our cpp, it doesn't work in either case. I've looked at the code for cpp and it doesn't do anything special, just ordinary opens and fopens. From what I understand of the way cygwin.dll works, this should be fine and they should be opened as text files but in our case, it doesn't seem to happen. What am I missing? Is there some sort of define or configure option that I should be using to make this work properly? It can't be $CYGWIN since the cygwin cpp.exe works fine in the same environment as ours so I'm at a complete loss. 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/