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 Reply-To: Cygwin List Message-Id: <6.1.0.6.0.20041119143038.04e7a008@pop.prospeed.net> X-Sender: Date: Fri, 19 Nov 2004 14:31:32 -0500 To: Peter Rehley , cygwin AT cygwin DOT com From: Larry Hall Subject: Re: flex and dos source files. How is flex built for cygwin In-Reply-To: <419E499B.4040007@mvista.com> References: <419E499B DOT 4040007 AT mvista DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" At 02:29 PM 11/19/2004, you wrote: >Hi, > >We have a customer that is using flex under a custom version of cygwin that we provided them (with source). The customer is having problems when their "*.l" files are in dos format. Flex is taking the lines from the file and adding them into the lex.yy.c file untouched. (i.e. they still have the \n\r at the end), and this causing problems later on. > >I tried using the version of flex that comes with the latest version of cygwin (1.5.12) and flex changes the \n\r to just \n, which makes everything work fine. Good I thought since the version of flex we provide is not the latest. I'll just recompile. > >But when I tried that with the latest flex (2.5.4a-3) I get the same behavior that the customer is seeing. I get this behavior even if I compile on the latest version of cygwin. > >So, my question is what options are used for building flex? Linking against /usr/lib/binmode.o perhaps? -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 838 Washington Street (508) 893-9889 - FAX Holliston, MA 01746 -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/