Re: [Bug-gnubg] Compile: lib/buffer.[ch] used at all?

[Joseph Heled]

I would think so too, i.e. that Sun include files are used with gcc of 
vice versa.

I might be wrong, but 'iso/stdarg_iso.h' does not look gcc to me.

-Joseph

Jim Segrave wrote:
> On Thu 07 Aug 2003 (20:33 +0200), Holger wrote:
>
> > Hi all,
> >
> > I think lib/buffer.[ch] aren't used at all, so I guess they could be 
> > removed from lib/Makefile.am?
> >
> > After messing around with the paths I've encountered once more problems on 
> > Solaris.
> >
> > Making all in lib
> > make[2]: Entering directory `/tmp/hb-030807/gnubg/gnubg/lib'
> > source='buffer.c' object='buffer.o' libtool=no \
> > depfile='.deps/buffer.Po' tmpdepfile='.deps/buffer.TPo' \
> > depmode=gcc3 /bin/bash ../depcomp \
> > gcc -DHAVE_CONFIG_H -I. -I. -I..     -g -O2 -c `test -f 'buffer.c' || echo 
> > './'`buffer.c
> > buffer.c: In function `BufferWritef':
> > buffer.c:245: error: `__builtin_va_alist' undeclared (first use in this 
> > function)
> > buffer.c:245: error: (Each undeclared identifier is reported only once
> > buffer.c:245: error: for each function it appears in.)
> > make[2]: *** [buffer.o] Error 1
> >
> > This is because in iso/stdarg_iso.h (included by stdarg.h):
> > 78:#define     va_start(list, name)    (void) (list = (__va_list) 
> > &__builtin_va_alist)
> >
> > But I can't find the definition of __builtin_va_alist (did a "grep -rn 
> > __builtin_va_alist /usr/include/*").
>
>
> I'd have been more worried if you had found them :-). They are
> built-in to the compiler's code generator (most builtins will generate
> in-line code or sometimes will actally trigger the compiler to do some
> optimisations).
>
> This looks like either your compiler is using another compiler's
> include paths or there's some other compiler installation problem.