Comment out [email protected] because of build errors with basic gcc stack#48478
Conversation
Add recent versions of py-cylc-flow, py-cylc-rose, py-cylc-uiserver, and their dependency py-protobuf (spack PR spack#48052); pull spack PRs spack#48251 ([email protected] - intel classic conflict) and spack#48478 (comment out [email protected])
|
I am able to successfully build So I am wondering if a conflict (https://spack.readthedocs.io/en/latest/packaging_guide.html#conflicts-and-requirements) would be a better approach. What do you think? |
I was wondering, too. I could build it on my laptop (Oracle Linux 9 with gcc@13), but it failed on an HPC RHEL 8.7 with gcc@11, and on a Ubuntu 24.04 AWS instance with gcc@11. I am wondering if the gcc version is the problem, but I didn't have time to look into it. I was just kicking the can down the road I guess! |
It's not the compiler (would have been surprising anyway), since I can build 1.3.0 with [email protected] on my Oracle Linux 9 system. Since you can build on rhel8, but the build fails on the HPC with RHEL8.7, it's not a RH-based v8 vs RH-based v9 either. Hmm. Otherwise, the stacks have the same requirements across my machines, only the externals differ. |
|
@tldahlgren I can't figure out within a reasonable time what causes the build error and what allows it to build. Do you want me to leave the version in and add a blanket conflict (i.e. without |
Fair point under the circumstances. I've experimented with a couple of options specifying the complete architecture as the first argument and If you want to simply comment out the version, perhaps also comment out lines 32, 36, and 40 with comment(s) about uncommenting once resolve the issues? |
…uiltin/packages/py-arrow/package.py
…/remove_pyarrow_130_due_to_build_errors
Yes, good point. Done in 675b0c7 |
|
Thanks! |
…ck (spack#48478) * Comment out [email protected] because of build errors with basic gcc stack * Also comment out 1.3.0-specific depends_on lines
…ck (spack#48478) * Comment out [email protected] because of build errors with basic gcc stack * Also comment out 1.3.0-specific depends_on lines
…ck (spack#48478) * Comment out [email protected] because of build errors with basic gcc stack * Also comment out 1.3.0-specific depends_on lines
…ck (spack#48478) * Comment out [email protected] because of build errors with basic gcc stack * Also comment out 1.3.0-specific depends_on lines
…ck (spack#48478) * Comment out [email protected] because of build errors with basic gcc stack * Also comment out 1.3.0-specific depends_on lines
2 participants
Resolves #48477
I added the package
py-arroworiginally, but didn't add myself as maintainer. Nobody else contributed to it so far. Since nothing in spack develop as of today depends on[email protected](i.e.1.2.3suffices, and it builds ok), I am commenting out the version with a reference to the issue so that the memory isn't lost.I am also adding myself as maintainer.