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

[Holger]

At 21:38 07.08.2003 +0200, Jim Segrave wrote:
> On Thu 07 Aug 2003 (20:33 +0200), Holger wrote:
> > 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.

Ah, that makes sense. I had obviously given cc's header files to gcc.

So if gcc is installed in /usr/local/bin then I should only use the 
includes in /usr/local/include? Does it usually make sense to set 
C_INCLUDE_PATH, or should pkg-config handle all non-standard paths?

Thanks and regards,

        Holger