Description of the problem
I'm debugging why ilastik's builds on Windows fail with pytorch 2.4 and above (ilastik/ilastik#2927), and have been able to trace the problem back to openmp version 5.0.0, which is pulled into our env by pyshtools:
(torchtest) >conda-tree whoneeds openmp
libflang
(torchtest) >conda-tree whoneeds libflang
pyshtools
(torchtest) >conda-tree depends pyshtools
astropy
cartopy
ducc0
fftw
libblas
libflang
liblapack
libpgmath
matplotlib-base
numpy
pooch
python
python_abi
requests
scipy
ucrt
vc
vc14_runtime
xarray
Would it be possible to build a new (conda) package with a newer version of libflang? I've confirmed that pytorch 2.5.1 is functional inside an env with libflang 19.1.3 (current newest on conda-forge), and I've been able to verify that older versions up to libflang 18.1.8 are fine as well. An obvious difference in libflang 18.1.8 is that it stopped depending on clang, maybe that's why pytorch can work with it.
Description of the problem
I'm debugging why ilastik's builds on Windows fail with pytorch 2.4 and above (ilastik/ilastik#2927), and have been able to trace the problem back to
openmpversion 5.0.0, which is pulled into our env bypyshtools:Would it be possible to build a new (conda) package with a newer version of libflang? I've confirmed that
pytorch 2.5.1is functional inside an env withlibflang 19.1.3(current newest on conda-forge), and I've been able to verify that older versions up tolibflang 18.1.8are fine as well. An obvious difference in libflang 18.1.8 is that it stopped depending onclang, maybe that's why pytorch can work with it.