X-Recipient: archive-cygwin@delorie.com X-Spam-Check-By: sourceware.org Date: Mon, 3 Aug 2009 20:00:16 -0400 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: Flex issues in Cygwin 1.7 Message-ID: <20090804000016.GA20140@ednor.casa.cgf.cx> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <71e998b70908031629i7ad5642fk5202a285ab6a75f1@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <71e998b70908031629i7ad5642fk5202a285ab6a75f1@mail.gmail.com> User-Agent: Mutt/1.5.20 (2009-06-14) Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com On Tue, Aug 04, 2009 at 09:29:23AM +1000, bog gob wrote: >I found an issue with flex while building doxygen-1.5.9 in cygwin 1.7. >One obvious issue is that there is a newline inserted after every >normal line in the .cpp output file, this will break code that needs >multiple lines (like a multi line macro). The version of flex is >2.5.35 the same version I have used successfully in building doxygen >using the cygwin 1.5* DLLs. My cygwin installation uses DOS/text file >types. I don't know what a "normal line" is in this context but flex takes \r\n input and produces \n output. That's not going to change. cgf -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple