[Bug dynamic-link/19884] Discrepancy between documented and actual search path for shared libraries

["fweimer at redhat dot com" <sourceware-bugzilla at sourceware dot org>]

https://sourceware.org/bugzilla/show_bug.cgi?id=19884

--- Comment #6 from Florian Weimer <fweimer at redhat dot com> ---
Nathaniel, it occurred to me that your use case is not helped at all if we
fixed this in glibc *now*.  We'd need a time machine to fix this in the EL5
time frame, so that you get binary compatibility with libcs from that era.

From a Red Hat perspective, changing search path resolution in Red Hat
Enterprise Linux 5 and CentOS 5 is not a good idea because it is precisely the
kind of change users do *not* expect, even if it is technically a bug fix.  It
would have to be gated by a dlopen flag.  (This also applies to Red Hat
Enterprise Linux 6 and CentOS 6.)

Therefore, I suggest we move the discussion to libc-help and find a way you can
build DSOs for Python modules so that they do not exhibit this problem, largely
with tools available on an EL5 distribution.

-- 
You are receiving this mail because:
You are on the CC list for the bug.