Re: "undef. ref. to __va_copy"??

[James Henstridge <james daa com au>]

Because there isn't a standard way to *copy* a va_list structure.  On some
machines it is a pointer, and on others it is an array.  I guess egcs
offers more helper routines to do these sort of things than the older
versions of gcc.

I suppose the rationale is that if the functionality is there, you may as
well use it.

James Henstridge.

--
Email: james@daa.com.au
WWW:   http://www.daa.com.au/~james/


On Wed, 24 Mar 1999, Drazen Kacar wrote:

> Dean Elhard wrote:
> 
> > The __va_copy reference comes from the egcs vararg.h header.  You are
> > getting it because the glib RPM you installed was compiled with egcs
> > and so, when the /usr/lib/glib/include/glibconfig.h was created, it
> > included the line
> > 	#define G_VA_COPY	__va_copy
> > because __va_copy was the correct configuration parameter on that
> > machine.
> 
> You mean that glib is compiler dependant? Just like C++ libraries?
> Why doesn't it just #include <varargs.h> if it exists on a given
> platform?
> 
> -- 
>  .-.   .-.    Life is a sexually transmitted disease.
> (_  \ /  _)
>      |        dave@srce.hr
>      |        dave@fly.cc.fer.hr
> 
> 
> -- 
>         FAQ: Frequently-Asked Questions at http://www.gnome.org/gnomefaq
>          To unsubscribe: mail gnome-list-request@gnome.org with 
>                        "unsubscribe" as the Subject.
>