In the last mail [EMAIL PROTECTED] said:
> 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
> 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.
That's the one
> I'll probably have to build the cross toolset again, maybe some time
> next week. What information are you looking for?
If you look back a few lines (hopefully) in the commands make has run you'll
see something like
/usr/local/bin/arm-linux-ar blah/libgcc.a
/usr/local/bin/ranlib blah/libgcc.a
where the ar is your cross toolset ar (same path and prefix as your cross as,
cross gcc etc) while the ranlib is your usual host ranlib
I'm nothing to do with glibc, but if you're able to work out or supply enough
information to let them work out which makefile is doing this, then it's a
bug in the build process that they can correct.
(They in this context includes Phil B?)
Nick
unsubscribe: body of `unsubscribe linux-arm' to [EMAIL PROTECTED]
