From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-return-74670-listarch-gcc=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 23167 invoked by alias); 20 May 2003 06:49:56 -0000
Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Archive: <http://gcc.gnu.org/ml/gcc/>
List-Post: <mailto:gcc@gcc.gnu.org>
List-Help: <http://gcc.gnu.org/ml/>
Sender: gcc-owner@gcc.gnu.org
Received: (qmail 23081 invoked from network); 20 May 2003 06:49:52 -0000
Received: from unknown (HELO ns1.nec.com.au) (147.76.180.1)
  by sources.redhat.com with SMTP; 20 May 2003 06:49:52 -0000
Received: from frodo.nec.com.au (smtp1.nec.com.au [147.76.52.2])
	by ns1.nec.com.au (8.11.6/8.11.6) with ESMTP id h4K6nhq12839;
	Tue, 20 May 2003 16:49:43 +1000
Received: from deer.dd.nec.com.au (localhost.localdomain [127.0.0.1])
	by frodo.nec.com.au (8.11.6/8.11.6) with ESMTP id h4K6lHx06534;
	Tue, 20 May 2003 16:47:17 +1000
Received: from dvalin (dvalin.dd.nec.com.au [147.76.212.105])
	by deer.dd.nec.com.au (8.12.5/8.12.5/Debian-1) with ESMTP id h4K6neIE005558;
	Tue, 20 May 2003 16:49:40 +1000
Received: from dvalin.dd.nec.com.au (localhost [127.0.0.1])
	by dvalin (8.12.3/8.12.3/Debian-5) with ESMTP id h4K6imDg028301;
	Tue, 20 May 2003 16:44:48 +1000
Received: (from erik@localhost)
	by dvalin.dd.nec.com.au (8.12.3/8.12.3/Debian-5) id h4K6ilFS028299;
	Tue, 20 May 2003 16:44:47 +1000
Date: Tue, 20 May 2003 06:53:00 -0000
From: Erik Christiansen <erik@dd.nec.com.au>
To: Peter Barada <peter@baradas.org>
Cc: gcc@gcc.gnu.org, crossgcc@sources.redhat.com
Subject: Re: failure building gcc-3.3 (broken libiberty/vsprintf.c or build?)
Message-ID: <20030520064446.GC794@dd.nec.com.au>
References: <20030520053204.ADDB298982@baradas.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20030520053204.ADDB298982@baradas.org>
User-Agent: Mutt/1.3.28i
X-Topic: bri_ppc
X-SW-Source: 2003-05/txt/msg01841.txt.bz2

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