problems with first pass binutils

Olaf Gruettner olaf.gruettner at web.de
Mon Dec 20 13:59:34 PST 2004


> > checking for C compiler default output file name... a.out
> > checking whether the C compiler works... configure: error: cannot run C
> > compiled programs.
> > If you meant to cross compile, use `--host'.
> > See `config.log' for more details.
> > make: *** [configure-libiberty] Error 1
> > 
> > does this make sense to someone?
> Seems to me that there is an environment var not set correctly.
> Try 
> # env -i PATH=$PATH ../binutils-2.15.91.0.2/configure --prefix=/tools \
> --disable-nls && \
> env -i PATH=$PATH make configure-host && \
> env -i make LDFLAGS="-all-static"
> 
> If this works there might be an environment variable like CPU set;
> check this with "env" and unset the respective variable with
> 
> "unset <name of variable>"

didn´t work:

env -i PATH=$PATH make configure-host
Configuring in libiberty
configure: loading cache ./config.cache
checking whether to enable maintainer-specific portions of Makefiles...
no
checking for makeinfo... makeinfo
checking for perl... perl
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
checking for i686-pc-linux-gnu-ar... ar
checking for i686-pc-linux-gnu-ranlib... ranlib
checking for i686-pc-linux-gnu-gcc... gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... configure: error: cannot run C
compiled programs.
If you meant to cross compile, use `--host'.
See `config.log' for more details.
make: *** [configure-libiberty] Error 1


config.log:
...
...
configure:4156: checking for i686-pc-linux-gnu-ar
configure:4189: checking for ar
configure:4228: checking for i686-pc-linux-gnu-as
configure:4261: checking for as
configure:4300: checking for i686-pc-linux-gnu-dlltool
configure:4333: checking for dlltool
configure:4372: checking for i686-pc-linux-gnu-ld
configure:4405: checking for ld
configure:4444: checking for i686-pc-linux-gnu-nm
configure:4477: checking for nm
configure:4516: checking for i686-pc-linux-gnu-ranlib
configure:4549: checking for ranlib
configure:4588: checking for i686-pc-linux-gnu-windres
configure:4621: checking for windres
configure:4706: checking whether to enable maintainer-specific portions
of Makef
iles
configure:4753: checking if symbolic links between directories work


what does this mean?
does user lfs need write access to /tools or does it work with write
access to /mnt/lfs/tools ?

more ideas?

Olaf




More information about the lfs-support mailing list