Nicholas Clark wrote:
> Useless as a bug report, but could someone keep a watch out and report
> where they find the following:
>
> One of either binutils or egcs (and I would guess egcs) when cross compiling
> calls native ranlib on a library rather than cross-ranlib.
> When native is a.out and cross is ELF this tends to trash your library
> (until you run cross-ranlib again). I bodged this by making ranlib a link to
> /bin/true, but this isn't ideal. Now that my native ranlib is ELF, I can't
> tell you where the problem is (unless I go through the hell of bootstrapping
> a cross toolset)
I have seen this while building glibc.
I typed:
%CC=arm-linux-gcc ./configure arm-linux --build=i686-pc-linux-gnu
--prefix=/usr/local/arm/glibc/arm-linux-glibc --enable-add-ons
--with-headers=/~kernel path~/linux-2.2.2/linux/include
%make
and got the error
/usr/local/arm/lib/gcc-lib/arm-linux/egcs-2.91.60/libgcc.a
could not read symbols: Archive has no index; run ranlib to add one.
I'll probably have to build the cross toolset again, maybe some time
next week. What information are you looking for?
Matt La Mantia
unsubscribe: body of `unsubscribe linux-arm' to [EMAIL PROTECTED]
