Skip to content
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

spack install vtk #11987

Closed
lcebaman opened this issue Jul 11, 2019 · 6 comments
Closed

spack install vtk #11987

lcebaman opened this issue Jul 11, 2019 · 6 comments

Comments

@lcebaman
Copy link

lcebaman commented Jul 11, 2019

Steps to reproduce the issue

spack install vtk ^hdf5+hl+mpi
Input spec
--------------------------------
vtk
    ^hdf5+hl+mpi

Concretized
--------------------------------
==> Error: Multiple providers found for 'gl': ['mesa@18.1.2%gcc@8.2.0~hwrender~llvm+swrender arch=linux-centos7-x86_64  ^binutils ^bison@2.4.1: ^damageproto@1.1: ^diffutils@3.7%gcc@8.2.0 arch=linux-centos7-x86_64  ^expat@2.2.5%gcc@8.2.0+libbsd arch=linux-centos7-x86_64  ^fixesproto@5.0: ^flex@2.5.35: ^gdbm ^gettext@0.19: ^glproto@1.4.14: ^help2man ^icu4c ^inputproto ^kbproto ^libbsd ^libpthread-stubs ^libsigsegv ^libx11@1.6: ^libxau@0.99.2: ^libxcb@1.9.3: ^libxdamage ^libxdmcp ^libxext ^libxfixes ^libxshmfence@1.1: ^libxv ^libxvmc ^m4@1.4.18%gcc@8.2.0+sigsegv arch=linux-centos7-x86_64  ^ncurses ^openssl ^perl@5.14.0: ^pkgconf@1.6.0%gcc@8.2.0 arch=linux-centos7-x86_64  ^presentproto@1.0: ^py-argparse ^py-mako@0.3.4: ^py-markupsafe@0.9.2: ^py-setuptools ^python@2.7:2.8,3.4: ^readline ^util-macros ^videoproto ^xcb-proto ^xextproto@7.1.99: ^xproto@7.0.17: ^xtrans ^zlib@1.2.11%gcc@8.2.0+optimize+pic+shared arch=linux-centos7-x86_64', 'opengl']

Platform and user environment

$ uname -a 
Linux indy2-login0 3.10.0-327.36.3.el7.x86_64 #1 SMP Mon Oct 24 16:09:20 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
$ lsb_release -d
Description:	CentOS Linux release 7.3.1611 (Core)
@lcebaman
Copy link
Author

Any idea how to fix this?

@adamjstewart
Copy link
Member

adamjstewart commented Jul 13, 2019

Possible duplicate of #7901 #7339 #7986 #8059 #8133 #9408. Hopefully one of those issues mentions a workaround that helps!

@lcebaman
Copy link
Author

Possible, but the solutions provided do not satisfy our system. We cannot even locate packages.yaml. Is there a cleaner solution?

@adamjstewart
Copy link
Member

We cannot even locate packages.yaml.

You can figure out where your packages.yaml contributions come from via:

$ spack config blame packages

Also see https://spack.readthedocs.io/en/latest/configuration.html for additional locations where packages.yaml files can be placed if you don't already have any.

Is there a cleaner solution?

I don't currently know of one, but @scheibelp or @tgamblin might.

@scheibelp @tgamblin if we figure out a reliable way to workaround this, we should add it to https://spack.readthedocs.io/en/latest/known_issues.html until a more permanent solution can be found. This seems to be a common issue.

@scheibelp scheibelp self-assigned this Jul 15, 2019
@scheibelp
Copy link
Member

What commit of Spack are you on?

the solutions provided do not satisfy our system.

So for example you cannot build mesa? If so, you could do spack spec vtk+osmesa ^hdf5+hl+mpi ^mesa, which should avoid the concretization issue.

@alalazo
Copy link
Member

alalazo commented Nov 2, 2020

I can't reproduce this issue anymore, both with the original and the new concretizer. Closing for now, but feel free to reopen if I missed something.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants