[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Bug ld/24718] Unresolved weak dependency on a versioned symbol should n
carlos at redhat dot com
[Bug ld/24718] Unresolved weak dependency on a versioned symbol should not prevent a program from running
Mon, 24 Jun 2019 00:51:21 +0000
--- Comment #9 from Carlos O'Donell <carlos at redhat dot com> ---
(In reply to Paul Pluzhnikov from comment #8)
> (In reply to Florian Weimer from comment #6)
> > I would say this is a static link editor limitation. It has to mark symbol
> > versions as weak if they are only referenced by weak symbols.
> Ok, I'll update product to "binutils".
Again, I'll comment for the record that the "weak" status of the symbol should
make no difference at runtime.
Please also note that VER_FLG_WEAK was not for weak symbols, but for "weak
version definitions" :
That is to say:
* If you have a bug fix / performance improvement, which is externally
invisible to the binary, you can expose a weak version definition for the bug
fix e.g. GLIBC_BZ24718.
* Normal binaries record the weak version definition, but if it's not present
at runtime they operate normally, and the lack of this weak version definition
* Binaries that need the bug fix can depend explicitly on the weak version
definition which promotes it to a strong version definition and it becomes
_required_ at runtime.
- weak symbols are not relevant to dynamic linking.
- VER_FLG_WEAK is not for weak symbols but for weak version definitions, and
the traditional role for those in Solaris is to demarcate bug fixes and
performance changes or other library internal changes. Using it for optional
"weak" functions could have unintended behavioural consequences that would need
to be reviewed.
You are receiving this mail because:
You are on the CC list for the bug.