BU 2.13 build problem

[Johnny Teveßen]

Dear Binutils team,

I'm experiencing problems installing binutils for different targets.
Its scripts don't seem to find "ranlib" on installation stage. Wouldn't
it possible for binutils to use its own, already-built "ranlib" on
"make install" instead?

And: IMHO it's a bit strange that binutils uses "gcc" and "ranlib"
on "make install", when a "make (all)" has already been done. I think
on "make install" there should only copying files take place.

What I did:

$ mkdir build && cd build
$ ../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
$ make

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".

Prefixed, its own "ranlib" had already been installed as
"/usr/bin/i686-linux-elf-ranlib", but the install scripts
were not able to find or use this.

Am I wrong when I think that all compiling/ranlibbing stuff
should already have been done at "make all" stage?

I solved this by restoring an older ranlib into the $PATH
and started "make install" again. Strange, though.

kind regards from Cologne, Germany
Johnny

pgpVxVKGlwjXL.pgp
Description: PGP signature