This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: failure building gcc-3.3 (broken libiberty/vsprintf.c or build?)
- From: DJ Delorie <dj at redhat dot com>
- To: peter at baradas dot org
- Cc: gcc at gcc dot gnu dot org, crossgcc at sources dot redhat dot com
- Date: Tue, 20 May 2003 12:09:45 -0400
- Subject: Re: failure building gcc-3.3 (broken libiberty/vsprintf.c or build?)
- References: <20030520053204.ADDB298982@baradas.org>
> 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.