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
Delivered-To: mailing list cygwin AT cygwin DOT com
To: "David Gluss" <dgluss AT marple-tech DOT com>
Cc: "Stephan Mueller" <smueller AT microsoft DOT com>, <cygwin AT cygwin DOT com>
Subject: Re: Bug in new Bison parser generator
References: <F8268126BF427A409936A83B6B863387050B40B9 AT red-msg-01 DOT redmond DOT corp DOT microsoft DOT com>
	<001901c1aaab$c87ed790$6600a8c0 AT cherry>
From: Andrew Markebo <flognat AT flognat DOT myip DOT org>
Date: 01 Feb 2002 09:02:53 +0100
In-Reply-To: <001901c1aaab$c87ed790$6600a8c0@cherry>
Message-ID: <m3665h1vf6.fsf@localhost.localdomain>
Lines: 9
User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/20.7
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii

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/