In the last mail Philip Blundell said:
> Report it using the glibcbug script and give details of any places you can
> think of where it happens. Sadly most people are running on GNU systems where
> /bin/sh is Bash, so this sort of problem often remains hidden for a long time.
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)
Nick
unsubscribe: body of `unsubscribe linux-arm' to [EMAIL PROTECTED]
