-
-
Notifications
You must be signed in to change notification settings - Fork 31
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
Build with CMake on unix #128
Conversation
…nda-forge-pinning 2022.09.03.21.29.17
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 ( |
This PR is ready, but it's better to direct review efforts at #127 to avoid duplicated efforts. |
Here's the full package plan from
|
Just noting that we're seeing something similar over in Dask's macOS Python 3.9 CI build when attempting to import
Full traceback:
|
There are some differences, but the SO version is the same as before, which makes the error quite bizarre, because the pytorch build logs say:
which directly contradicts the error being reported:
I'm really baffled by this, but I could vaguely imagine that, not having cmake metadata, the build system does something weird and encodes a requirement for "+1", and then ends up failing once that guess is no more necessary. CC @isuruf, if you any idea what might be happening here. |
Switching from autotools to cmake is not ABI compatible most of the time, unless the upstream maintainers care about it (which is not the case most of the time). I wrote a checklist of things to do in https://conda-forge.org/docs/maintainer/knowledge_base.html#moving-from-an-autotools-build-to-a-cmake-build I think you should mark the latest builds as broken ASAP. |
See conda-forge/admin-requests#480 (currently only for osx, because further up it was explicitly mentioned that "This only happens on x86, not ARM." - happy to expand it though, if you think that's prudent) |
I think it's better to mark all versions as broken, do the checklist and then re-enable cmake builds. |
Expanded conda-forge/admin-requests#480. |
Thanks for the context! I'll see if I can use that to fix it, or otherwise we could just change over at 3.22. In the meantime, I'm reverting this in #129, so that the branches remain publishable. |
I am not sure what is the reason and I can't investigate at the moment, but just FYI it seems that this PR also changed something on the Windows side leading do regressions, unless I am wrong. See robotology/robotology-superbuild#1251 . |
Windows used to be built with cmake already, the only change there was to make the static builds depend on the shared ones (as on unix), and correspondingly rename the import libraries from
Are you using |
The error is related to project that do not use/link protobuf at all, that is just a (configuration) error of the line:
|
The problem is that |
🤦 |
Well, it could be solved by adding |
Ah sorry, I get your question now, |
I guess it is just an historical legacy of Historically, this counterintuitive behavior has been handled by explicitly adding a As an example of tricky incompatibilities that are different between |
As #127:
Testing things like grpc through the examples provided upstream needs
find_package(protobuf)
to run, which fails on unix withbecause the builds here are done with autotools.
Build with cmake to be able to run better testing in grpc-cpp feedstock. Also: