Closed #1664.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/pull/1664#event-5205877532___
Rpm-maint mailing list
Rpm-maint@lists.rpm
See above, I think this is addressing the wrong end of the problem.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/pull/1664#issuecomment-905384515__
If I understand the ticket correctly, this is solving the wrong problem. With
the exception of `foo_hooks`, all symbols in a plugin should be static in which
case they get resolved at build time and using this GNU-specific extension is
wholly unnecessary.
--
You are receiving this because you
@ffesti, i see what you mean, i will change it, thanks
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/pull/1664#issuecomment-828442036___
I understand the issue of symbols of the plugin vs system symbols as both may
be linked to different versions of a library or symbols may collide otherwise.
I am just not quite sure how or if at all this relates to RTLD_LAZY vs
RTLD_NOW. So while the change may be OK I wonder if the commit messa
dlopen load plugins LIBRARY with RTLD_LAZY flag
it means the symbols are loaded when references are executed
so it causes issue when some references are the same than in system
append RTLD_BINDDEEP allows to first load symbols from the plugin library
You can view, comment on, or merge this pull re
