This is the mail archive of the
mailing list for the Cygwin project.
Re: Bug in new Bison parser generator
- From: "David Gluss" <dgluss at marple-tech dot com>
- To: "Andrew Markebo" <flognat at flognat dot myip dot org>
- Cc: "Stephan Mueller" <smueller at microsoft dot com>,<cygwin at cygwin dot com>
- Date: Fri, 1 Feb 2002 09:28:51 -0800
- Subject: Re: Bug in new Bison parser generator
- References: <F8268126BF427A409936A83B6B863387050B40B9@red-msg-01.redmond.corp.microsoft.com><001901c1aaab$c87ed790$6600a8c0@cherry> <firstname.lastname@example.org>
The switches for which compiler is compiling the output of Bison
are in the bison.simple or bison.hairy file. There isn't any pre-
configuration to set up which compiler you will be using...what you're
trying to do is to generate portable C or C++ code.
The problem is that the compiler switching in bison.simple used to
work, and now it doesn't. The patch is very small and simple.
Indeed if you compile with gcc, you won't have a problem.
----- Original Message -----
From: "Andrew Markebo" <email@example.com>
To: "David Gluss" <firstname.lastname@example.org>
Cc: "Stephan Mueller" <email@example.com>; <firstname.lastname@example.org>
Sent: Friday, February 01, 2002 12:02 AM
Subject: Re: Bug in new Bison parser generator
> Just a quick question, isn't the base problem somehthing like Bison
> thinks that the target compiler is gcc..
> If you create/configure a bison for msvc++, it doesn't do this include?
> The eye of the beholder rests on the beauty!
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html