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: <200010051819.e95IJiY01236@laxmls02.socal.rr.com> X-Sender: cloder AT pop-server DOT socal DOT rr DOT com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0 Date: Thu, 05 Oct 2000 11:22:23 -0700 To: cygwin AT sourceware DOT cygnus DOT com From: Chad Loder Subject: RE: gcc problem? Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Isn't the preprocessor supposed to take care of this? I remember reading that the first phase of preprocessing is to map from the arbitrary platform character set to the standard source character set (this includes mapping the platform's end-of-line character(s) to LF if necessary). On the other hand, it's a question of "what is the platform's end-of-line character sequence" and since the platform is Cygwin (as opposed to Win32) then the end-of-line sequence is just LF, right? So...never mind (maybe). :) c At 12:22 PM 10/5/2000 -0400, you wrote: >Hi Victor, > >> Question: what am i doing wrong? or what is wrong with gcc? > >nothing wrong, except that you have CR/LF line endings in your source code. > >Karsten > >-- >Want to unsubscribe from this list? >Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com > -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com