Re: [SEToolkit-developer] Building SE Toolkit

[Dagobert M. <da...@ba...>]

Hello Jon,

Am 16.08.2007 um 19:26 schrieb Jon Craig:

> I'm trying to build the SE Toolkit and I am receiving the following  
> error:
>
> gcc -DHAVE_CONFIG_H -I.  -Dsparc -DDEFAULT_SE_BASEDIR="\"/usr/local"\"
> -DDEFAULT_SE_INCLUDE="\"/usr/local/share/se/include\""
> -DDEFAULT_SE_LIB="\"/usr/local/lib\""   -g -O2 -MT funcs.o -MD -MP -MF
> .deps/funcs.Tpo -c -o funcs.o funcs.c
> funcs.c: In function `yyerror':
> funcs.c:98: error: `__builtin_va_alist' undeclared (first use in  
> this function)
> funcs.c:98: error: (Each undeclared identifier is reported only once
> funcs.c:98: error: for each function it appears in.)
> funcs.c:98: warning: second parameter of `va_start' not last named  
> argument
> gmake[2]: *** [funcs.o] Error 1
> gmake[2]: Leaving directory `/lcl/svn/setoolkit/trunk/se'
> gmake[1]: *** [all-recursive] Error 1
> gmake[1]: Leaving directory `/lcl/svn/setoolkit/trunk/se'
> gmake: *** [all] Error 2
>
> My build platform includes:
> Sun Microsystems  sun4u SUNW,Sun-Blade-1000 (2 X UltraSPARC-III)
> GCC v 3.4.2
> I've run autoreconf -if in the "trunk/se" directory I pulled from  
> your SVN.
>
> Hoping someone could point me in the right direction (like does SE
> Toolkit require SUN Studio?).

I can reproduce the problem with gcc 3.4.3. SE should be buildable  
with GCC,
so I'll treat this as a bug. SE is definitely buildable with Sun Studio.


Best regards

   -- Dagobert