From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21456 invoked by alias); 20 May 2003 16:16:24 -0000 Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org Received: (qmail 17798 invoked from network); 20 May 2003 16:14:39 -0000 Received: from unknown (HELO monty-python.gnu.org) (199.232.76.173) by sources.redhat.com with SMTP; 20 May 2003 16:14:39 -0000 Received: from mx1.redhat.com ([66.187.233.31]) by monty-python.gnu.org with esmtp (Exim 4.20) id 19I9gX-0000Gy-Fc for gcc@gcc.gnu.org; Tue, 20 May 2003 12:09:53 -0400 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.11.6/8.11.6) with ESMTP id h4KG9lH27028; Tue, 20 May 2003 12:09:47 -0400 Received: from post-office.corp.redhat.com (post-office.corp.redhat.com [172.16.52.227]) by int-mx1.corp.redhat.com (8.11.6/8.11.6) with ESMTP id h4KG9lI17014; Tue, 20 May 2003 12:09:47 -0400 Received: from greed.delorie.com (dj.cipe.redhat.com [10.0.0.222]) by post-office.corp.redhat.com (8.11.6/8.11.6) with ESMTP id h4KG9kZ15106; Tue, 20 May 2003 12:09:46 -0400 Received: (from dj@localhost) by greed.delorie.com (8.11.6/8.11.6) id h4KG9jR20778; Tue, 20 May 2003 12:09:45 -0400 Date: Tue, 20 May 2003 16:19:00 -0000 Message-Id: <200305201609.h4KG9jR20778@greed.delorie.com> From: DJ Delorie To: peter@baradas.org CC: gcc@gcc.gnu.org, crossgcc@sources.redhat.com In-reply-to: <20030520053204.ADDB298982@baradas.org> (message from Peter Barada on Tue, 20 May 2003 01:32:04 -0400 (EDT)) Subject: Re: failure building gcc-3.3 (broken libiberty/vsprintf.c or build?) References: <20030520053204.ADDB298982@baradas.org> X-SW-Source: 2003-05/txt/msg01869.txt.bz2 > gcc-3.3/lbiberty/vsprintf.c, indeed includes (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.