From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 32495 invoked by alias); 16 Apr 2007 04:43:14 -0000 Received: (qmail 32487 invoked by uid 22791); 16 Apr 2007 04:43:13 -0000 X-Spam-Check-By: sourceware.org Received: from omta03sl.mx.bigpond.com (HELO omta03sl.mx.bigpond.com) (144.140.92.155) by sourceware.org (qpsmtpd/0.31) with ESMTP; Mon, 16 Apr 2007 05:43:02 +0100 Received: from oaamta03sl.mx.bigpond.com ([144.136.165.71]) by omta03sl.mx.bigpond.com with ESMTP id <20070416044258.VZPP28147.omta03sl.mx.bigpond.com@oaamta03sl.mx.bigpond.com>; Mon, 16 Apr 2007 04:42:58 +0000 Received: from bubble.grove.modra.org ([144.136.165.71]) by oaamta03sl.mx.bigpond.com with ESMTP id <20070416044258.JJYD15692.oaamta03sl.mx.bigpond.com@bubble.grove.modra.org>; Mon, 16 Apr 2007 04:42:58 +0000 Received: by bubble.grove.modra.org (Postfix, from userid 500) id 82BA0313424; Mon, 16 Apr 2007 14:12:58 +0930 (CST) Date: Mon, 16 Apr 2007 07:44:00 -0000 From: Alan Modra To: Martin Haupt Cc: binutils@sourceware.org Subject: Re: Binutils 2.17: configure in libiberty does not find stdlib.h -> build failure Message-ID: <20070416044258.GS28088@bubble.grove.modra.org> Mail-Followup-To: Martin Haupt , binutils@sourceware.org References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.9i X-IsSubscribed: yes Mailing-List: contact binutils-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: binutils-owner@sourceware.org X-SW-Source: 2007-04/txt/msg00203.txt.bz2 On Sat, Apr 14, 2007 at 09:30:51PM +0200, Martin Haupt wrote: > I am currently trying to build diy-linux with a crosstool compiler on a > lfs 6.2 live system (64bit). > But the first binutils build fails in libibery/cplus-dem.c because > stdlib.h is missing (it's there and the compiler finds it). I looked > through the logs and found out that configure in the libiberty directory > is the only configure which is not finding stdlib.h (and other standard > includes)! That will be because Daniel made libiberty/configure.ac invoke AC_PROG_CPP_WERROR, thus turning cpp warnings into errors. See http://sourceware.org/ml/binutils/2003-09/msg00416.html configure in other dirs doesn't do this. > Now there is a strange spot in the config.log: > > configure:3691: checking for stdlib.h > configure:3704: x86_64-unknown-linux-gnu-gcc -Wl,-dynamic-linker > -Wl,/cross-tools/x86_64-unknown-linux-gnu/sys-root/lib64/ld-linux-x86-64.so.2 > -E conftest.c > x86_64-unknown-linux-gnu-gcc: -dynamic-linker: linker input file unused > because linking not done > x86_64-unknown-linux-gnu-gcc: > /cross-tools/x86_64-unknown-linux-gnu/sys-root/lib64/ld-linux-x86-64.so.2: > linker input file unused because linking not done > configure:3710: $? = 0 It is indeed strange that you have linker options being passed to your cpp. How are you configuring? Do you specify CPP or CPPFLAGS, perhaps via your environment? -- Alan Modra IBM OzLabs - Linux Technology Centre