We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I believe zlib was added to https://github.com/LLNL/benchpark/tree/develop/systems/genericx86/externals/base/00-packages.yaml to make Laghos work. We need to remove it from the system definitions.
The text was updated successfully, but these errors were encountered:
I believe zlib was added to https://github.com/LLNL/benchpark/tree/develop/systems/genericx86/externals/base/00-packages.yaml to make Laghos work. * [ ] What was the reason? Is this because we need the handle?
I believe zlib was added to https://github.com/LLNL/benchpark/tree/develop/systems/genericx86/externals/base/00-packages.yaml to make Laghos work.
* [ ] What was the reason? Is this because we need the handle?
This was to avoid spack from defaulting to building zlib-ng, which does not work for non-intel compilers
* [ ] Is the correct solution to put it in externals for each system?
Possibly. But that will assume every system has to have zlib installed
* [ ] If yes, does every system definition have to have it? * [ ] If yes, is there a better place to put it?
The Spack team may be able to clarify this better
Sorry, something went wrong.
After discussion 11/26, we should remove zlib from packages on all systems except for lassen. @rfhaque.
scheibelp
becker33
No branches or pull requests
I believe zlib was added to https://github.com/LLNL/benchpark/tree/develop/systems/genericx86/externals/base/00-packages.yaml to make Laghos work. We need to remove it from the system definitions.
The text was updated successfully, but these errors were encountered: