Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Any package that might call blas from openmp must conflict with the pthreads build of openmp. From the openblas faq:
But adding the required constraint:
to exclude the incompatible pthreads build results in a default solve with
libblas=*=blis
andliblapack=*=netlib
due to the features minimization to exclude openmp having higher priority than the preference for openblas.In general, the opemp builds of openblas should be strictly more compatible, so I'm not sure why it's deprioritized so severely (in #99). The test case there doesn't give any errors with
libopenblas=0.3.27=openmp_h25fa9fd_1
andllvm-openmp=18.1.8=hf5423f3_1
.Maybe there's another way to weigh down netlib even more so
liblapack=*=openblas + openblas=*=*openmp*
is a preferred solution toliblapack=*=netlib
? Would adding more features on liblapack netlib do that?I also added the missing
run_exports
toopenblas
, which is the package required in host dependencies for linking openblas.