This is a bug with strip -g which makes the stripped object wrong. HJ
has checked in a patch, however it just makes the linker abort, rather
than segfault, so at least we know what is wrong.
It seems #342777 is in the same basket, so who knows how many
libraries have been built with this incorrect strip version. Is there
any way to find out? I have requested in the above bug that somebody
backport the fix, but at this stage anything stripped with the current
binutils will make the objects unlinkable.
----- End forwarded message -----
block 343163 with 342777
thanks
----- Forwarded message from <email address hidden> ----- sourceware. org/bugzilla/ show_bug. cgi?id= 2008
On Fri, Dec 09, 2005 at 02:49:07PM +1100, Ian Wienand wrote:
> http://
This is a bug with strip -g which makes the stripped object wrong. HJ
has checked in a patch, however it just makes the linker abort, rather
than segfault, so at least we know what is wrong.
It seems #342777 is in the same basket, so who knows how many
libraries have been built with this incorrect strip version. Is there
any way to find out? I have requested in the above bug that somebody
backport the fix, but at this stage anything stripped with the current
binutils will make the objects unlinkable.
----- End forwarded message -----
Jeremy
-- www.jerryweb. org/ : JerryWeb.org sailcut. sourceforge. net/ : Sailcut CAD opensource. polytechnique. org/ : Polytechnique.org Free Software
http://
http://
http://