Dave,

On Mon, Oct 28, 2002 at 08:58:12PM -0000, Dave Page wrote:
> > -----Original Message-----
> > From: Jason Tishler [mailto:jason@;tishler.net] 
> > Sent: 28 October 2002 20:42
> > Subject: Re: [HACKERS] Request for supported platforms
> > 
> > On Mon, Oct 28, 2002 at 11:20:16AM -0500, Jason Tishler wrote:
> > > My WAG is that you will be able to upgrade your Cygwin
> > > installation before I fix the Cygwin build issues. :,)
> > 
> > I guess my WAG was wrong... :,)
> 
> I've been meaning to ask this for a while - what exactly is a WAG? :-)

Larry was kind enough to answer this one for me.  :,)

> > 1. Cygwin bison needs to be upgraded from 1.35 to 1.75 (i.e., 
> > 1.50+) to process src/interfaces/ecpg/preproc/preproc.y 
> > successfully.  I will post to the Cygwin mailing list asking 
> > the maintainer for this upgrade.
> 
> OK. This shouldn't stop a release though I assume, only a build from
> CVS.

Yes.  Nevertheless, I have posted my request:

    http://cygwin.com/ml/cygwin/2002-10/msg01740.html

> > 2. The following fseeko/ftello ifdef in src/include/pg_config.h.in:
> > 
> >     #ifndef HAVE_FSEEKO
> >     #define fseeko(a, b, c) fseek((a), (b), (c))
> >     #define ftello(a) ftell((a))
> >     #endif
> > 
> > conflicts with the following Cygwin /usr/include/stdio.h entries:
> > 
> >     int _EXFUN(fseeko, (FILE *, off_t, int));
> >     off_t   _EXFUN(ftello, ( FILE *));
> > 
> > Unfortunately, I'm not sure what is the best way to solve 
> > this one yet. Any suggestions would be appreciated.

I found a solution to the above which will hopefully find its way into
the next Cygwin release:

    http://cygwin.com/ml/cygwin-patches/2002-q4/msg00042.html
    
> Yes, I'm seeing errors with this on my updated Cygwin very early in
> the build. I did think it was my hacked about installation, but I
> guess not!

A quick and *dirty* fix for this problem is to temporarily delete the
above two entries from your stdio.h file.

Jason

---------------------------(end of broadcast)---------------------------
TIP 4: Don't 'kill -9' the postmaster

Reply via email to