[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Bug-gnubg] GNU Question
From: |
Jim Segrave |
Subject: |
Re: [Bug-gnubg] GNU Question |
Date: |
Mon, 1 Sep 2003 01:11:55 +0200 |
User-agent: |
Mutt/1.4.1i |
On Mon 01 Sep 2003 (00:58 +0200), Jim Segrave wrote:
> On Mon 01 Sep 2003 (00:01 +0200), Nardy Pillards wrote:
> > From: Joern Thyssen <address@hidden>
> > > On Sun, Aug 31, 2003 at 10:01:05PM +0200, Jim Segrave wrote
> > > >
> > > > As for putting the position and match ID's in the copy buffer, it
> > > > sounds like a good idea to me.
> > >
> > > Already done.
> > >
> > > J?rn
> > >
>
> I've put a #if USE_GUI around these calls in gnubg.c and removed the
> dead variable in play.c - try that out.
>
> The alloca errors seem odd - we could have a conditional in routines
> using alloca:
>
> #ifdef WIN32
> #define alloca __builtin_alloca
> #endif
>
> to suppress the other warnings, but I haven't done that.
Actually, while I was doing that, a make was running - I have
temporarily made these #ifdef ndef, as they appear to be functions for
a later version of Python
--
Jim Segrave address@hidden