Hi, On 25 September 2016 at 10:16, Armin Rigo <arigo@tunes.org> wrote:
How about looking first from the place of the symlink itself, and if not found, we dereference the symlink and look again?
That can't work, because there is no way to know the path of the symlink to libpypy-c.so. We can only learn the dereferenced path, using dladdr(). I've partly reverted my check-in: now we look first based on the pypy executable's real location, like before; and only if that fails, we look based on the libpypy-c.so's real location. Like before, we never look based on where a symlink is. That means it should be fully backward compatible, but in addition it also works if the symlink is on the libpypy-c.so instead of the pypy executable. We should still try to convince a few distributions to use this new approach, in order to fix embedding there. A bientôt, Armin.