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 Delivered-To: mailing list cygwin AT cygwin DOT com Message-ID: <005e01c1ab46$a9859950$6600a8c0@cherry> From: "David Gluss" To: "Andrew Markebo" Cc: "Stephan Mueller" , References: <001901c1aaab$c87ed790$6600a8c0 AT cherry> Subject: Re: Bug in new Bison parser generator Date: Fri, 1 Feb 2002 09:28:51 -0800 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 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" To: "David Gluss" Cc: "Stephan Mueller" ; 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? > > /Andy > > -- > The eye of the beholder rests on the beauty! > -- 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/