Are you compiling from CVS or from a released tarball? The bison
requirement was recently raised to bison 1.5 or above (1.75 was recently
released also.) This is an issue only when compiling from CVS, since
the bison stuff is preprocessed for released tarballs. So you might
want to try the just release beta3.
On Mon, 2002-10-28 at 08:32, Jason Tishler wrote:
> Dave,
>
> Thanks for the heads up...
>
> On Mon, Oct 28, 2002 at 10:31:00AM -0000, Dave Page wrote:
> > > -----Original Message-----
> > > From: Bruce Momjian [mailto:pgman@candle.pha.pa.us]
> > > Sent: 26 October 2002 03:17
> > > Subject: [HACKERS] Request for supported platforms
> > >
> > > Folks. start sending in those plaform reports, OS name and
> > > version number please.
> >
> > CYGWIN_NT-5.1 PC9 1.3.10(0.51/3/2) 2002-02-25 11:14 i686 unknown
> ^^^^^^
>
> Please try with Cygwin 1.3.14-1 while I attempt to deal with at least
> the following Cygwin build issues with PostgreSQL CVS as of today at
> about 7:00 AM EST:
>
> 1. pg_config.h.in HAVE_FSEEKO ifdef:
>
> make[4]: Entering directory `/home/jt/src/pgsql/src/backend/access/common'
> gcc -O2 -Wall -Wmissing-prototypes -Wmissing-declarations -I../../../../src/include -DBUILDING_DLL -c -o
heaptuple.oheaptuple.c
> In file included from ../../../../src/include/c.h:56,
> from ../../../../src/include/postgres.h:48,
> from heaptuple.c:21:
> /usr/include/stdio.h:207: parse error before `('
>
> 2. Cygwin bison limit exceeded:
>
> make[4]: Entering directory `/home/jt/src/pgsql/src/interfaces/ecpg/preproc'
> [snip]
> bison -y -d preproc.y
> preproc.y:5560: fatal error: maximum table size (32767) exceeded
>
> > Make check failed with the normal spurious errors.
>
> I would stick with make installcheck due to the Cygwin (i.e., Windows)
> backlog issue.
>
> > Make installcheck also failed on horology, copy2 and domain - see
> > attached output.
> >
> > The clocks changed here on Saturday night, so I guess that shouldn't
> > have caused the first error (or should the docs be updated?).
> >
> > The second 2 errors are both with copys - related to the problem with
> > the listen() backlog queue in the parallel test perhaps?
>
> I haven't looked into the above yet due to the build problems. Any help
> regarding these issues is gratefully appreciated.
>
> Thanks,
> Jason
>
> ---------------------------(end of broadcast)---------------------------
> TIP 5: Have you checked our extensive FAQ?
>
> http://www.postgresql.org/users-lounge/docs/faq.html