Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Date:	Mon, 14 Apr 2003 14:05:36 +0100 (WEST)
From:	Andrey Romanenko <andrew AT eq DOT uc DOT pt>
To:	Ronald Landheer-Cieslak <ronald AT landheer DOT com>
cc:	cygwin AT cygwin DOT com
Subject:	Re: g77 + gcc + flex + bison woes
In-Reply-To:	<Pine.LNX.4.44.0304111344030.18674-100000@localhost.localdomain>
Message-ID:	<Pine.LNX.4.44.0304141356160.15736-100000@nectar.eq.uc.pt>
MIME-Version:	1.0

Dear Ronald,

Thank you for your reply. This weekend I gave it another try and
found a solution ^H^H^H^H^H^H^H^H workaround. As I suspected flex
was at fault. The offending code is in libfl.a that contains libmain.o,
that, in turn, has a main(). Unlike what happens under Linux, the
linker replaced my (correct) main with the one from libfl.a no matter
what. And, no, I didn't have YY_MAIN macro defined. My workaroind
consisted of purging libfl.a of libmain.o. This way the program
runs swimmingly. I am not sure why there is such difference between
Linux and Cygwin..

Andrey




--
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/

- Raw text -