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

[Erik Christiansen <erik@dd.nec.com.au>]

On Tue, May 20, 2003 at 01:32:04AM -0400, Peter Barada wrote:
> 
> gcc-3.3/lbiberty/vsprintf.c, indeed includes <varargs.h> (which gcc
> supplise), so if gcc-3.3 has killed support for varargs,h, why is
> libiberty/vsprintf.c trying to include it.  In fact, why is gcc-3.3
> trying to build libiberty with the *target* compiler anyway?
> 
> Any suggestions?

   Is there something sytematically wrong with libiberty? Building the
   latest snapshot (gcc-core-20030512) for avr also breaks on libiberty.
   make install has makefile rule problems:

   gcc -c   -g -O2 -DIN_GCC -DCROSS_COMPILE  -W -Wall -Wwrite-strings
   -Wstrict-prototypes -Wmissing-prototypes -Wtraditional -pedantic
   -Wno-long-long   -DHAVE_CONFIG_H -DGENERATOR_FILE    -I. -I.
   -I../../gcc -I../../gcc/. -I../../gcc/config -I../../gcc/../include
   ../../gcc/gengenrtl.c -o gengenrtl.o
   make[1]: *** No rule to make target `../libiberty/libiberty.a',
   needed by `gengenrtl'.  Stop.
   make[1]: Leaving directory `/usr/local/src/gcc-20030512/obj-avr/gcc'

   In this case, the configure step warned:

>>>
   checking host system type... i686-pc-linux-gnu
   checking target system type... avr-unknown-none
   checking build system type... i686-pc-linux-gnu
   *** This configuration is not supported in the following subdirectories:
     target-libiberty
    (Any other directories should still work fine.)
<<<

   That being the case, why did it bomb, failing to install an
   executable? And is it not unusual for further compilation to be done
   under the install target??

   I hope I'm not mixing in something different on this thread, but at
   first glance it looks like the makefiles are not up to snuff.

Regards,
Erik