https://sourceware.org/bugzilla/show_bug.cgi?id=27666
Jan Beulich <jbeulich at suse dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jbeulich at suse dot com
--- Comment #8 from Jan Beulich <jbeulich at suse dot com> ---
(In reply to Nick Clifton from comment #2)
> Created attachment 13455 [details]
> Proposed patch
This looks to never hove gone in?
> I am working on a theory that the real bug is that
> _bfd_write_archive_contents() is not creating the symbol index. As you
> noted the call to bfd_check_format() fails, because there are two potential
> matches. But I do not think that this is grounds for the archiver to decide
> that there are no objects in the library.
I ran into that issue today, only then realizing that Rainer, in a cleanup
patch [1], also refers to it. Imo excluding the plain ELF targets there would
better be avoided. What I'm puzzled by it that with --enable-targets=all the
issue doesn't occur. Why is it that ASSOCIATED_VECS is set only for
--enable-targets=all? The different behavior of bfd_check_format_matches() with
and without it set, when multiple targets match, looks like a pretty obvious
problem to me.
[1] https://sourceware.org/pipermail/binutils/2025-December/146056.html
--
You are receiving this mail because:
You are on the CC list for the bug.
