Closed erykoff closed 9 months ago
sigh thats not good. we can probably force it to use conda-forge pybind somehow. I had done some work on this in the past.
However, I don't have dailight hours today to redact the packages.
@isuruf any thoughts on the mitigation before marking the pytorch packages as broken?
will merge 213, do you think that it is worth adding a repodata patch?
@erykoff, can you confirm that the issue is fixed in the latest builds?
Yes thank you, our builds are now working correctly after this was released. Thanks for your quick fix!
@isuruf I may have spoken too soon. The macos builds are available (and good), but there don't appear to be new linux-64 builds for mkl and the 102 builds that are available clobber pybind11.
Thank you for bringing this up. I had the builds made locally, so I uploaded the CPU only ones: https://github.com/conda-forge/pytorch-cpu-feedstock/pull/213#issuecomment-1908095969
it seemed that more than just linux64 + mkl was missing.
Solution to issue cannot be found in the documentation.
Issue
Installing pytorch=2.1 and libtorch=2.1 brings in a vendored version of
include/pybind11
which clobbers the installed version ofpybind11-global
on macos (For whatever reason libtorch comes with pytorch on macos but not linux). This is breaking our code. cc @isurufInstalled packages
Environment info