From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20800 invoked by alias); 7 May 2008 07:57:06 -0000 Received: (qmail 20792 invoked by uid 22791); 7 May 2008 07:57:05 -0000 X-Spam-Check-By: sourceware.org Received: from mx.transitive.com (HELO pennyblack.transitives.com) (217.207.128.220) by sourceware.org (qpsmtpd/0.31) with ESMTP; Wed, 07 May 2008 07:56:34 +0000 Received: from [192.168.2.168] (helo=[192.168.2.168]) by pennyblack.transitives.com with esmtp (Exim 4.50) id 1JteVs-0002iP-Kp; Wed, 07 May 2008 07:56:34 +0000 Message-ID: <482160AD.40504@transitive.com> Date: Wed, 07 May 2008 08:16:00 -0000 From: James Molloy User-Agent: Icedove 1.5.0.14pre (X11/20071018) MIME-Version: 1.0 To: Ralf Wildenhues CC: gcc-help@gcc.gnu.org Subject: Re: GCC 4.3.0 configure failure: libgcc References: <48206A25.5060304@transitive.com> <20080506204032.GB16385@ins.uni-bonn.de> In-Reply-To: <20080506204032.GB16385@ins.uni-bonn.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact gcc-help-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-help-owner@gcc.gnu.org X-SW-Source: 2008-05/txt/msg00079.txt.bz2 Ralf Wildenhues wrote: > Hello James, > > * James Molloy wrote on Tue, May 06, 2008 at 04:24:37PM CEST: > >> I'm attempting to build GCC 4.3.0 - and I thought I had succeeded until >> I realised that the 'all-gcc' make target (now?) doesn't build libgcc.a. >> > > >> configure:4082: g++ -c -g -O2 conftest.cc >&5 >> conftest.cc: In function 'int main()': >> conftest.cc:13: error: 'exit' was not declared in this scope >> > > >> As you can see, the test program autoconf is generating does not include >> , so g++ is perfectly correct in erroring. >> > > >> Compiling GCC 4.3.0 from source using G++ 4.1.2, autoconf 2.61, and >> automake 1.10. >> > > Use Autoconf 2.59 to generate configure (and Automake 1.9.6). Better > yet, do not regenerate configure scripts at all, just use those shipped > with 4.3.0. > > Newer Autoconf versions don't take care to declare exit any more. > The GCC macros need to be adjusted for this before using newer Autoconf. > I'll post a patch. > > Hope that helps. > > Cheers, > Ralf > Hi Ralf, Thanks for the reply. I haven't regenerated the configure script at all, I'm using the vanilla one as shipped with the stable 4.3.0 release. So really I'm not sure if the bug is with autoconf or gcc's config.in - I've found a workaround with help from members of freenode.net#osdev who have had the same problem - it seems more widespread than I first thought. The workaround is to compile the targets "all-gcc all-target-libgcc" then install "install-gcc install-target-libgcc" - which for some reason completes successfully. I really have no idea why - the same configure script in the libgcc subdirectory must be called, surely. I reply with this in the hope that it will be useful in bug tracking. Cheers, James