pure-lfs - using binutils-2.13.90 series

Richard A Downing richard.downing at bcs.org.uk
Thu Feb 20 00:08:36 PST 2003


Ryan.Oliver at pha.com.au wrote:
> Richard A Downing wrote:
> 
>> I'm about to start a new LFS build, my old one has some twisted
>> binutil/gcc mistakes in it, and I want a clean start.
>>
>> I'd like to use binutils-2.13.90.0.18 and gcc-3.2.2 in this.  My current
>> system uses gcc-3.2.2/glibc-2.3.1/binutils-2.13.2.1.
 
> I don't see any issues with it, you may not need the binutils patch
> though, so check that first.

Well, unfortunately I've met an immediate and insuperable (for me) obstacle:
binutils-2.13.90.0.18 uses a different configure/make process to the old
series.  The top level configure script only build the top level Makefile,
and each subsystem run's its own configure as part of make.  This results
in an immediate failure with the pure-lfs LDFLAGS as sown below.  I'm not a
good enough autoconf wizard to debug this, so unless it's obvious to
someone elase out there, I'm going back to GNU for binutils.  Pity.

I did some tests, it's the -all-static that it doesn't like!


richard:~/Pure-lfs/binutil-build:0:$: CFLAGS="-O2 -pipe" /
../binutils-2.13.90.0.18/configure --prefix=/stage1 --disable-nls
creating cache ./config.cache
checking host system type... i686-pc-linux-gnu
checking target system type... i686-pc-linux-gnu
checking build system type... i686-pc-linux-gnu
checking for i686-pc-linux-gnu-ar... no
checking for ar... ar
checking for i686-pc-linux-gnu-as... no
checking for as... as
checking for i686-pc-linux-gnu-dlltool... no
checking for dlltool... dlltool
checking for i686-pc-linux-gnu-ld... no
checking for ld... ld
checking for i686-pc-linux-gnu-nm... no
checking for nm... nm
checking for i686-pc-linux-gnu-ranlib... no
checking for ranlib... ranlib
checking for i686-pc-linux-gnu-windres... no
checking for windres... windres
checking for i686-pc-linux-gnu-objcopy... no
checking for objcopy... objcopy
checking for i686-pc-linux-gnu-objdump... no
checking for objdump... objdump
checking for i686-pc-linux-gnu-ar... no
checking for ar... ar
checking for i686-pc-linux-gnu-as... no
checking for as... as
checking for i686-pc-linux-gnu-dlltool... no
checking for dlltool... dlltool
checking for i686-pc-linux-gnu-ld... no
checking for ld... ld
checking for i686-pc-linux-gnu-nm... no
checking for nm... nm
checking for i686-pc-linux-gnu-ranlib... no
checking for ranlib... ranlib
checking for i686-pc-linux-gnu-windres... no
checking for windres... windres
updating cache ./config.cache
creating ./config.status
creating Makefile
richard:~/Pure-lfs/binutil-build:0:$: make LDFLAGS="-all-static -s"
Configuring in intl
loading cache .././config.cache
checking for a BSD compatible install... /bin/install -c
checking how to run the C preprocessor... gcc -E
checking whether make sets ${MAKE}... yes
checking for gcc... gcc
checking whether the C compiler (gcc -O2 -pipe -all-static -s) works... no
configure: error: installation or configuration problem: C compiler cannot
create executables.
make: *** [configure-intl] Error 1

The config.log in intl is:

This file contains any messages produced by compilers while
running configure, to aid debugging if configure makes a mistake.

configure:562: checking for a BSD compatible install
configure:616: checking how to run the C preprocessor
configure:637: gcc -E  conftest.c >/dev/null 2>conftest.out
configure:677: checking whether make sets ${MAKE}
configure:706: checking for gcc
configure:783: checking whether the C compiler (gcc -O2 -pipe -all-static
-s) works
configure:797: gcc -o conftest -O2 -pipe  -all-static -s conftest.c  1>&5
cc1: unrecognized option `-all-static'
configure: failed program was:
#line 793 "configure"
#include "confdefs.h"
main(){return(0);}

So clearly, the -all-static LDFLAG is being applied to gcc by mistake.

-- 
cheers,
Richard.

Richard A Downing FBCS
-- 
Unsubscribe: send email to listar at linuxfromscratch.org
and put 'unsubscribe lfs-dev' in the subject header of the message



More information about the lfs-dev mailing list