-
Notifications
You must be signed in to change notification settings - Fork 428
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
ENH check all sysroot locations for DSOs #3969
Conversation
cc @jjhelmus |
If this change is accepted, I'd very much like it to make the next release. |
Also, we need this as part of shipping cos7 on conda-forge. |
Bump here everyone. |
another bump here |
bump again on this |
Should we do a rebuild of all cos6 cdts with this fix? And host them on CF? I'm happy with that but will also upload them to defaults. |
Yes this is my plan. |
Shall we merge @mingwandroid ? |
bump here again on merging |
Thanks @beckermr! |
You closed it but didn't merge it @mingwandroid. :) |
Bump here @mingwandroid @jjhelmus this was accidentally closed instead of merged. Can we please reopen and merge it? |
1 similar comment
Bump here @mingwandroid @jjhelmus this was accidentally closed instead of merged. Can we please reopen and merge it? |
Thanks @marcelotrevisani! Can you please merge this one? |
I would be more comfortable if you create a test to cover this scenario. |
@mingwandroid was happy to merge without. I’ve tested the code live. Making a test for this is pretty hard as id need a package to build, link to some dso and then insert two sysroot paths in the env to find the dso in. |
Bump here again. Tests for this edge case are quite difficult. I’d like to merge without them. Can we please merge this? |
bump here again @jjhelmus @mingwandroid |
Ugh now there are conflicts |
Oops, sorry! |
Thanks! |
Hi there, thank you for your contribution! This pull request has been automatically locked because it has not had recent activity after being closed. Please open a new issue or pull request if needed. Thanks! |
This PR changes the DSO checking code to examine all sysroots for potential DSOs when trying to detect missing DSOs in the post-build stage.
We (@isuruf and myself), found that when we have a symlink to the sysroot in the build env and we refer to a DSO by its symlinked location, conda build thinks it's missing because it only checks one spot.
The fact that it only checks one has been in the code since its start in these commits
IDK why it only checks one. @mingwandroid should comment on that.