[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: BU 2.13 build problem
From: |
Alan Modra |
Subject: |
Re: BU 2.13 build problem |
Date: |
Mon, 9 Sep 2002 11:20:02 +0930 |
User-agent: |
Mutt/1.2.5i |
On Sun, Sep 08, 2002 at 02:59:38PM +0200, Johnny Teveßen wrote:
> $ ../configure --prefix=/usr --target=i686-linux-elf
> --enable-targets=i686-linux-elf,i686-linux,i386-linux-elf,i386-linux,i386-elf,i386-aout,i686-aout,arm-elf,arm-oabi,arm-coff,arm-aout,arm-pe,sh-elf
You didn't specify --build or --host, and I strongly suspect that
config.guess chose values other than i686-linux-elf. That probably
means that the build machinery is setting things up for a cross
compilation. In a cross-compilation environment, configure generally
can't run code snippets to determine target requirements, so defaults
are chosen that may not be ideal. In particular, you lose the "don't
run ranlib" optimisation.
> Then I removed my old binutils (since they were RPMed, the new ones
> would overwrite them and I didn't want RPM's DB to get confused)
> and did:
>
> $ make install
>
> Which I though would ONLY copy files. But it also compiled at least
> one further file using gcc, and then stopped with an error because
> it wasn't able to find "ranlib".
I recommend _not_ installing over the top of your system binutils.
Use a prefix of /usr/local, then set your path to search
/usr/local/bin before /usr/bin.
The extra compilation may have been to generate info files. If you
are using a release tarball this should not happen, but users of
cvs or snapshots will see this sort of thing.
--
Alan Modra
IBM OzLabs - Linux Technology Centre