Re: How to configure bison so that config.h does not have HAVE_STDINT_H defined

-- Original message -- From: [EMAIL PROTECTED] > > > Well, this is correct if this header file is available. > > > > > > > That's the thing, it's not available. Or at least, it's not where the > > other > > standard headers

Re: How to configure bison so that config.h does not have HAVE_STDINT_H defined

-- Original message -- From: [EMAIL PROTECTED] > > I have a platform on which I am trying to build bison 2.1 for which I > would like HAVE_STDINT_H not defined. Running the configure script > generates a config.h which has the following lines

How to configure bison so that config.h does not have HAVE_STDINT_H defined

Hi, I have a platform on which I am trying to build bison 2.1 for which I would like HAVE_STDINT_H not defined. Running the configure script generates a config.h which has the following lines: /* Define to 1 if you have the header file. */ #define HAVE_STDINT_H 1 Is there any way to not have

Re: Interesting problem with bison on Windows

-- Original message -- From: Hans Aberg <[EMAIL PROTECTED]> > On 19 Oct 2007, at 17:41, [EMAIL PROTECTED] wrote: > > >>> I am running into an interesting problem on Windows with Bison > >>> 2.1. My grammar defines the word IN as a token. When I build on > >>> Wi

Re: Interesting problem with bison on Windows

-- Original message -- From: Hans Aberg <[EMAIL PROTECTED]> > > On 19 Oct 2007, at 00:42, [EMAIL PROTECTED] wrote: > > > I am running into an interesting problem on Windows with Bison > > 2.1. My grammar defines the word IN as a token. When I build on > > W

Interesting problem with bison on Windows

I am running into an interesting problem on Windows with Bison 2.1. My grammar defines the word IN as a token. When I build on Windows, there is a file which includes the generated gram.h after including Microsoft's header WinDef.h. I'm using Visual Studio .NET 2003. Unfortunately, that head

Re: Building bison 2.1 on Windows

Thanks, Alfonso, I did find 2.1 on sourceforge.net. I'll keep the cygwin page in mind, as well Thanks! -Mary Ann -- Original message -- From: Alfonso Urdaneta <[EMAIL PROTECTED]> > [EMAIL PROTECTED] wrote: > > I'm still searching, but as of now, the only bison e

Re: Building bison 2.1 on Windows

I'm still searching, but as of now, the only bison executables for Windows that I have found is version 1.24 - way too old for my purposes. Any ideas about where I can find bison 2.1? Still hunting (and thanks!), Mary Ann -- Original message -- From: Alfonso Ur

Re: Building bison 2.1 on Windows

Thanks, Laurence, I'll take a look and see if this route is the one for me. In terms of building from the source, I'm just trying to be consistent (grab the tar/zip file, untar/unzip, and build on each platform). Binaries is a reasonable option, as well. Concerning Windows: my personal taste

Building bison 2.1 on Windows

Hi, I'm attempting to build bison 2.1 on Windows with both mks and cygwin. I've gotten a little ways with mks and am just starting with cygwin. Several questions: First question - Since there is no Makefile.nt or Visual Studio files in the tarball, I'll assume that I should be proceeding run