On Tue, Mar 29, 2016 at 2:51 PM, Nathaniel Smith <[email protected]> wrote: > Yeah, I'm not at all sure what's going on here and whether it's > intentional or a bug in glibc, and we should figure out what's > actually happening and why for our own understanding,
It appears that glibc's loader is like Windows loader, and if it's looking for libfoo and there's already some library called libfoo loaded then it will short-circuit the regular library lookup rules and use whatever libfoo was previously found, even if that is not the libfoo that would be found now using the currently relevant lookup rules. IMO this is a bug, plus it appears to be documented absolutely nowhere (at least on Windows this is a well-documented misfeature), but we'll see what upstream says... https://sourceware.org/bugzilla/show_bug.cgi?id=19884 https://github.com/njsmith/rpath-weirdness -n -- Nathaniel J. Smith -- https://vorpus.org _______________________________________________ Wheel-builders mailing list [email protected] https://mail.python.org/mailman/listinfo/wheel-builders
