build_ascent.sh fails with GCC 13 while building camp #1259
Comments
|
Thanks for the report, I checked and the newest camp release is using Our PR #1245 (and associated branch task/2024_01_blt_update) have updates to use newer camp, umpire,etc. Any chance you can try it out? |
|
Trying the new branch it gets a bit further. Now breaks in mfem: A one line fix to include cstdint in the header resolves it. It then breaks at: |
|
Going through: https://github.com/Alpine-DAV/ascent/blob/develop/src/cmake/thirdparty/SetupUmpire.cmake#L17 it should add but I do not know why I can not find the file. |
|
This issue is lib64 vs lib. Umpire made a change. I think this is also fixed in the update blt branch / PR
…________________________________
From: Freddie Witherden ***@***.***>
Sent: Wednesday, March 20, 2024 4:29:13 PM
To: Alpine-DAV/ascent ***@***.***>
Cc: Harrison, Cyrus D. ***@***.***>; Comment ***@***.***>
Subject: Re: [Alpine-DAV/ascent] build_ascent.sh fails with GCC 13 while building camp (Issue #1259)
Going through:
https://github.com/Alpine-DAV/ascent/blob/develop/src/cmake/thirdparty/SetupUmpire.cmake#L17<https://urldefense.us/v3/__https://github.com/Alpine-DAV/ascent/blob/develop/src/cmake/thirdparty/SetupUmpire.cmake*L17__;Iw!!G2kpM7uM-TzIFchu!yFyOBallCZQmZeFvBtXEV8fNkTqsBH-LGoBMwyno_I5XhN469dYzFLtF45h_qAwpZUQ2NB6Cm_8dQ-XJbXu4QJJ3$>
it clearly adds ${UMPIRE_DIR}/lib/cmake/umpire to the search path. Now if we ls ~/Programming/ascent/scripts/build_ascent/install/umpire-2024.02.0/lib64/cmake/umpire we see:
BLTInstallableMacros.cmake thirdparty umpire-targets.cmake
BLTSetupTargets.cmake umpire-config.cmake umpire-targets-release.cmake
BLTThirdPartyConfigFlags.cmake umpire-config-version.cmake
and so I have no idea why cmake is complaining that it can not find umpire-config.cmake as it is in the directory.
—
Reply to this email directly, view it on GitHub<https://urldefense.us/v3/__https://github.com/Alpine-DAV/ascent/issues/1259*issuecomment-2010899234__;Iw!!G2kpM7uM-TzIFchu!yFyOBallCZQmZeFvBtXEV8fNkTqsBH-LGoBMwyno_I5XhN469dYzFLtF45h_qAwpZUQ2NB6Cm_8dQ-XJbQsr7jOV$>, or unsubscribe<https://urldefense.us/v3/__https://github.com/notifications/unsubscribe-auth/AAJDUHUE4457YVM6ETY4Z73YZILUTAVCNFSM6AAAAABFAK7E6SVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMJQHA4TSMRTGQ__;!!G2kpM7uM-TzIFchu!yFyOBallCZQmZeFvBtXEV8fNkTqsBH-LGoBMwyno_I5XhN469dYzFLtF45h_qAwpZUQ2NB6Cm_8dQ-XJbcXCJEU2$>.
You are receiving this because you commented.Message ID: ***@***.***>
|
|
Yes, that is strange the lib vs lib64 logic is there. Thanks for trying the new branch -- a patch for old umpire should be simple (we need it to include <stdlib.h> in host.h) -- would you like me to test that out and get a branch? |
|
@FreddieWitherden for the umpire issue. build_ascent.sh (if you ask it to fully build ascent) will try to build ascent-develop (not the branched you have checked out), which doens't have the However, you can use the generated |
|
That did it! I was wondering why the CMake error appeared to be at odds with the code itself. Do you think it is worth changing the default to use the checked-out version of Ascent if it is available rather than compiling a fresh checkout from scratch? |
|
@FreddieWitherden thanks for confirming. I do think it we should improve build_ascent build with an option for the the checked out version. (I'll admit this has confused me more than once :-) ) |
|
@FreddieWitherden #1339 updates |
|
resolved in #1339 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
With the current develop branch of Ascent the
build_ascent.shscript fails with GCC 13. The offending package is:which indicates aproblem with
camp. If possible the version ofcampshould be bumped; otherwise perhaps we can simply disable building of tests for camp?The text was updated successfully, but these errors were encountered: