[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Bug ld/12562] Ld.dk fails with "could not read symbols: Bad value" mess

From: davek at gcc dot gnu.org
Subject: [Bug ld/12562] Ld.dk fails with "could not read symbols: Bad value" message
Date: Sat, 12 Mar 2011 17:49:32 +0000


--- Comment #11 from Dave Korn <davek at gcc dot gnu.org> 2011-03-12 17:49:21 
UTC ---
(In reply to comment #10)
> Both ld.gold and ld.hjl print warnings "cannot find entry symbol 'foo'". Still
> better then obscure "libfoobar.a: could not read symbols: Bad value" error.

Right.  I figure I can make ld.bfd do at least that much.  What it needs to be
able to do is open a library, pull in an archive member, have it claimed by the
plugin, then when the plugin has added ltrans objects and a symbol still isn't
satisfied it needs to be allowed to pull the same member in again, this time
getting only the native object.  Just need to find the right place to clear the
archive_pass flag on archive members that the plugin claims.

There are two separate bugs here; the first is that ld.bfd was reopening the
file chain at the wrong point, and this exposed the second: that we don't
support pulling in the native version of an archive member if its symbols are
still required after the plugin claimed it first time round.  But I can't see
much use in opening a second bug just for the sake of the paperwork, let's just
call it a bug with two parts :)

Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]