failure building gcc-3.3 (broken libiberty/vsprintf.c or build?)

[DJ Delorie]

> gcc-3.3/lbiberty/vsprintf.c, indeed includes <varargs.h> (which gcc
> supplies), so if gcc-3.3 has killed support for varargs,h, why is
> libiberty/vsprintf.c trying to include it.

That code in libiberty is ancient.  If it's broken now, that means
that whoever dropped support for varargs.h didn't test it well enough.

> In fact, why is gcc-3.3 trying to build libiberty with the *target*
> compiler anyway?

Libiberty is built up to three times: First, for the machine upon
which the build happens, second, for the machine upon which the
resulting tools will run, and third, for the target for which the
tools produce code.

------
Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sources.redhat.com