-
Notifications
You must be signed in to change notification settings - Fork 64
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
py-rattler install
with a relative prefix path results in invalid dynamic library dependency paths
#1037
Comments
Is this only with the most recent py-rattler releases? We changed to use "abi3" format and that might have triggered this. |
I was able to test as far back as 0.6.0 and it had the same behavior. |
Upon further inspection, it looks like ncurses is the only package in my entire package cache that has a placeholder dynamic dependency:
Every other dylib already has |
Looks like I was a little wrong, the placeholder is supposed to be replaced with the full path. I was able to fix my build by calling |
install
with a relative prefix path results in invalid dynamic library dependency paths
Makes sense! Would you be able to submit a Pr? |
Checklist
What happened?
After switching from mamba to py-rattler in my project, I started getting occasional strange behavior where files couldn't be found. Consider an environment
conda
with ncurses installed:Shouldn't libtinfo.6.dylib be one of
@loader_path/libtinfo.6.dylib
or perhaps@loader_path/../lib/libtinfo.6.dylib
?Edit:
I see that LC_RPATH is set to
@loader_path/
, so I believe it should be@rpath/libtinfo.6.dylib
or@rpath/../lib/libtinfo.6.dylib
Additional Context
No response
The text was updated successfully, but these errors were encountered: