spack: Clingo concretization picks wrong iconv provider
Hello Spack team,
I am facing an odd concretization behavior with the new concretizer. When I try to install netcdf-c ~mpi Spack is picking libc as the iconv provider. But the default variant for libc is ~iconv so it does not provide the iconv libraries. As a result, the build for netcdf-c~mpi and a host of other packages fail.
In my packages.yaml, I have ONLY libiconv as the iconv provider:
# packages.yaml ....
golang: [gcc]
iconv: [libiconv]
...
But if I ask: spack providers iconv, I get:
iconv:
libc libiconv
Oddly, the new concretizer picks libiconv as the provider when installing netcdf-c+mpi, but picks libc~iconv as the provider when installing netcdf-c~mpi.
Expected Behavior:
Clingo picks libiconv as the iconv provider in both cases.
About this issue
- Original URL
- State: closed
- Created 5 years ago
- Comments: 24 (24 by maintainers)
openssl@centos8does seem to concretize. Thanks for the workaround! I’ll check if it actually installs. There is no checksum foropenssl@centos8in the package.py, sospack installmay just error out.Maybe in future we can have a config flag like
ignore_deprecated_versionswhich would suppress this behavior by the concretizer?I think I’ll just edit
openssl/package.pyto remove the deprecated tag for that version in my packages for now.Big thanks to @alalazo for being so prompt and responsive! 😃
I just took care of the issue in the description so far. Will try to have a look at https://github.com/spack/spack/issues/24205#issuecomment-859158603 today.
@alalazo i tested again on the latest develop branch … this seems to solve the openssl issue.
The glx provider issues still persists. I still get
mesa18when concretizinglibepoxy.For what is worth, I’m looking into a subtle bug here. This diff seems to resolve this issue:
but unit tests are still failing on an edge case. Will continue working on it tomorrow.
@amaji I’ll try to have a look at these two issues going to Monday.
Hi @alalazo,
I need your advice with another issue. I am trying to install
qt+gtk+opengl ^python@3.9.5, but somehow this is choosingmesa18as the glx provider (instead ofmesa). Sincemesa18is old, it does not build withpython@3.9.5.I am wondering why is the ASP solver choosing mesa18 ahead of mesa. This does not change even if I remove
mesa18as a glx provider in mypackages.yaml.^mesa.