cross/libopcodes-2.9.5.0.37.so conflict

[Geert Uytterhoeven <geert@linux-m68k.org>]

Since gcc 2.7.2.3 can no longer build correct m68k-kernels, I'm rebuilding a
new cross-compiler on my PPC box, using the Debian sources for
binutils-2.9.5.0.37 and gcc-2.95.2.

I created a cross-binutils in /usr/local, using the configuration options
--enable-shared --build=powerpc-linux --host=powerpc-linux --target=m68k-linux.

But now my native as complains:

| callisto$ as -v
| as: error in loading shared libraries: /usr/local/lib/libopcodes-2.9.5.0.37.so: undefined symbol: floatformat_ieee_single_big
| callisto$ ldd /usr/bin/as
| 	libopcodes-2.9.5.0.37.so => /usr/local/lib/libopcodes-2.9.5.0.37.so (0x0ffb9000)
| 	libbfd-2.9.5.0.37.so => /usr/local/lib/libbfd-2.9.5.0.37.so (0x0ff45000)
| 	libc.so.6 => /lib/libc.so.6 (0x0fe2f000)
| 	/lib/ld.so.1 => /lib/ld.so.1 (0x30000000)
| callisto$

Anyone with a clue? I built many cross-compilers before, but never got bitten
by this problem.

Should I have installed everything in /usr/local/m68k-linux/ instead? I always
used /usr/local/ before.

Gr{oetje,eeting}s,

						Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
							    -- Linus Torvalds