You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When looking for a framework (e.g. Python.framework/Versions/Current/Python) the seerach functions in machlib.dyld not only look in the framework locations (as expected), but also along the library search path using the basename of the library in the framework.
That is, the search for Python.framework will also check /usr/local/lib/Python.
This seems dodgy and needs to be verified using the real linker (and ripped out if the behaviour is different than that linker).
BTW. I'm testing for the current behaviour in the unittests I'm currently writing, that doesn't mean the current behaviour is correct. Writing tests for existing code is so much fun...
The text was updated successfully, but these errors were encountered:
Original report by Ronald Oussoren (Bitbucket: ronaldoussoren, GitHub: ronaldoussoren).
When looking for a framework (e.g. Python.framework/Versions/Current/Python) the seerach functions in machlib.dyld not only look in the framework locations (as expected), but also along the library search path using the basename of the library in the framework.
That is, the search for Python.framework will also check /usr/local/lib/Python.
This seems dodgy and needs to be verified using the real linker (and ripped out if the behaviour is different than that linker).
BTW. I'm testing for the current behaviour in the unittests I'm currently writing, that doesn't mean the current behaviour is correct. Writing tests for existing code is so much fun...
The text was updated successfully, but these errors were encountered: