From:	kdh5j AT weyl DOT math DOT virginia DOT edu (Kirk Hilliard)
Subject:	Re: Bison for NT
18 May 1997 19:48:51 -0700 :
Sender:	mail AT cygnus DOT com
Approved:	cygnus DOT gnu-win32 AT cygnus DOT com
Distribution:	cygnus
Message-ID:	<199705182233.SAA65118.cygnus.gnu-win32@weyl.math.Virginia.EDU>
X-Mailer:	Mail User's Shell (7.2.5 10/14/92)
Original-To:	gnu-win32 AT cygnus DOT com
Original-Sender:	owner-gnu-win32 AT cygnus DOT com

Earlier today I wrote:
> Has anyone here ported bison to the NT?  If so, I would appreciate
> the details.  When successful, I will post instructions and also put
> them up on a web site.
>
> While I would be happy to use the cygwin-32 package to build bison,
> I need to be able to compile the parsers it generates using MSVC.

I reinstalled gnu-win32 b18 and this time bison configured and
compiled right out of the box.  I ran `configure' from bash (and
ignored `configure.bat' this time) and the ran `make'.  

The parser code that the resulting bison produced compiles without a
hitch under gcc, but I had a little trouble compiling it under MSVC
until I realized that I needed to #define MSDOS myself.  The initial C
code of my yacc file now contains:

  #ifdef _MSC_VER
  #define MSDOS 1 /* NT bison needs this */
  #endif

The resulting parser treats my grammer in the manner that I desired.

Thanks to all who replied,

Kirk Hilliard

P.S. I would still love to hear from anyone who has an opinion on
     whether my grammer is simply taking advantage of a loophole in
     bison and the 5 UNIX yaccs.
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request AT cygnus DOT com" with one line of text: "help".

- Raw text -