-
-
Notifications
You must be signed in to change notification settings - Fork 7
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
Rebuild for libboost 1.82 + flann 1.9.2 + CUDA 11.8 + CUDA 12 #10
Conversation
…nda-forge-pinning 2023.10.08.10.53.16
Hi! This is the friendly automated conda-forge-linting service. I just wanted to let you know that I linted all conda-recipes in your PR ( |
@Tobias-Fischer
Any ideas? |
Gentle ping @Tobias-Fischer |
I think we might be running into pybind/pybind11#4529 |
The pybind11 issue seems to be resolved. We are now running into the same issues as in #9:
I have no idea how to tackle it though, and I am not sure why it appears now. |
Well it is linking to the The question is, what is handing the linker the This probably involves more knowledge of how the build here occurs (probably combined with more verbose builds) |
Also this warning on CI seems important. Maybe worth raising upstream?
Edit: Seems like this should have been fixed ( colmap/colmap#1693 ). Is something here out-of-date? Like |
I think the issue is that this change has not been incorporated in the CmakeConfig of colmap that is being used here: https://github.com/colmap/colmap/blob/43de802cfb3ed2bd155150e7e5e3e8c8dd5aaa3e/cmake/CMakeConfig.cmake.in#L206 |
@conda-forge-admin please rerender |
…nda-forge-pinning 2023.10.21.18.55.51
@conda-forge-admin please rerender |
…nda-forge-pinning 2023.10.21.18.55.51
@conda-forge-admin please rerender |
…nda-forge-pinning 2023.10.21.18.55.51
Thank you both! 🙏 |
Bot could not open a PR due to pybind pin