What happens if the linked-in RPATH setting is different for an application and a shared library that it loads?
Suppose that an application has a:b, and a shared library X has b:a, and shared library Y is present in both a and b. Presumably the application will get shared library Y from a, but where will X get *its* dependencies from? What if the application has already loaded Y, and X also depends on it? What if X touches Y before the application does? Thanks.
