You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Basically, the latest PAPI version available in Spack is fairly old (6.0.0.1). The latest 7.0.0 or 7.0.1 releases are not in Spack for some reason. And git master doesn't build with Intel's oneAPI compiler using Spack because the patch that Spack attempts to apply in that case is already applied in the current git sources. @G-Ragghianti@gcongiu could you add the latest PAPI releases to Spack and constrain the patching so that it's not attempted with master?
General information
I have run spack debug report and reported the version of Spack/Python/Platform
I have run spack maintainers <name-of-the-package> and @mentioned any maintainers
I have uploaded the build log and environment files
I have searched the issues of this repo and believe this is not a duplicate
The text was updated successfully, but these errors were encountered:
We have an open PR for papi@7.0.0.1 #38443 which is waiting for someone to create a patch that implements the cray compiler fix that is mentioned in the PR. I will look into doing this soon.
Steps to reproduce the issue
Error message
Error message
Information on your system
Additional information
Basically, the latest PAPI version available in Spack is fairly old (6.0.0.1). The latest 7.0.0 or 7.0.1 releases are not in Spack for some reason. And git
master
doesn't build with Intel's oneAPI compiler using Spack because the patch that Spack attempts to apply in that case is already applied in the current git sources. @G-Ragghianti @gcongiu could you add the latest PAPI releases to Spack and constrain the patching so that it's not attempted withmaster
?General information
spack debug report
and reported the version of Spack/Python/Platformspack maintainers <name-of-the-package>
and @mentioned any maintainersThe text was updated successfully, but these errors were encountered: