Matt,
This problem might be related to building the Egcs 'C' compiler with the
following commands:
%./configure --target=arm-linux --prefix=/usr/local/arm
%cd gcc
%make LANGUAGES=c
%make LANGUAGES=c install
Some how 'arm-linux-ranlib' is not getting called properly. I'm in the
process of determining if the problem also shows up when running:
%./configure --target=arm-linux --prefix=/usr/local/arm
%make -i LANGUAGES=c
%make -i LANGUAGES=c install
from the ~/egcs-1.1.1 directory.
The workaround is to run "arm-linux-ranlib" by hand by hand.
Regards,
Jason
----------
From: [EMAIL PROTECTED]
[SMTP:[EMAIL PROTECTED]]
Sent: Wednesday, March 24, 1999 9:38 AM
To: Nicholas Clark
Cc: [EMAIL PROTECTED]
Subject: Re: Internal compiler error compiling GLIBC2.1
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]
unsubscribe: body of `unsubscribe linux-arm' to [EMAIL PROTECTED]
