delorie.com/archives/browse.cgi | search |
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 15:56:41 +0100 (WEST) |
From: | Andrey Romanenko <andrew AT eq DOT uc DOT pt> |
To: | cygwin AT cygwin DOT com |
Subject: | Re: g77 + gcc + flex + bison woes |
In-Reply-To: | <Pine.GSO.4.44.0304141043340.26381-100000@slinky.cs.nyu.edu> |
Message-ID: | <Pine.LNX.4.44.0304141554100.18871-100000@nectar.eq.uc.pt> |
MIME-Version: | 1.0 |
Igor, > Did you try putting the library after your main module, like this: > > gcc yourmain.o -fl -o myprog > > ? This way, the main() from your code should have been pulled in first. > The order of gcc arguments does matter, and there is usually no need to > pull a module from the library... Yes, I have -lfl at the very end of the lile. I am aware of the issue. In that case this looks like a bug. Or, a feature of the rather complicated salad that I have (g77+gcc+bison+flex). 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/
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |