summaryrefslogtreecommitdiff
path: root/README.md
diff options
context:
space:
mode:
authorFrank Willmore <frankwillmore@gmail.com>2021-05-13 23:31:20 -0500
committerGitHub <noreply@github.com>2021-05-13 21:31:20 -0700
commitb70bf073b5f647dd5a7f1917ed55dfd39d1a2a0c (patch)
tree62280d39b42de6b0df2d3cccec974d810b035a91 /README.md
parentb91f24fa8aa105bd1218e40e2da6677040271c6e (diff)
downloadspack-b70bf073b5f647dd5a7f1917ed55dfd39d1a2a0c.tar.gz
spack-b70bf073b5f647dd5a7f1917ed55dfd39d1a2a0c.tar.bz2
spack-b70bf073b5f647dd5a7f1917ed55dfd39d1a2a0c.tar.xz
spack-b70bf073b5f647dd5a7f1917ed55dfd39d1a2a0c.zip
cc: change mode to ccld for loopopt edit (#23482)
For configure (e.g. for hdf5) to pass, this option needs to be pulled out when invoked in ccld mode. I thought it had fixed the issue but I still saw it after that. After some digging, my guess is that I was able to get hdf5 to build with ifort instead of ifx. Lot of overlapping changes occurring at the time, as it were. There are still outstanding issues building hdf5 with ifx, and Intel is looking into what appears to be a compiler bug, but this manifests during build and is likely a separate issue. I have verified that the making the edit in 'ccld' mode removes the -loopopt=0 and enables hdf5 to pass configure. It should be fine to make the edit in 'ld' mode as well, but I have not tested that and didn't include an -or- condition for it.
Diffstat (limited to 'README.md')
0 files changed, 0 insertions, 0 deletions