-
Notifications
You must be signed in to change notification settings - Fork 704
New issue
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
{compiler,tools}[GCCcore/12.3.0] Clang v16.0.6, Z3 v4.12.2 #18509
{compiler,tools}[GCCcore/12.3.0] Clang v16.0.6, Z3 v4.12.2 #18509
Conversation
Test report by @boegel |
@boegelbot please test @ generoso |
@SebastianAchilles: Request for testing this PR well received on login1 PR test command '
Test results coming soon (I hope)... - notification for comment with ID 1671332810 processed Message to humans: this is just bookkeeping information for me, |
@boegelbot please test @ jsc-zen2 |
@casparvl: Request for testing this PR well received on jsczen2l1.int.jsc-zen2.easybuild-test.cluster PR test command '
Test results coming soon (I hope)... - notification for comment with ID 1671606181 processed Message to humans: this is just bookkeeping information for me, |
Test report by @casparvl |
Test report by @boegelbot |
Test report by @SebastianAchilles |
Test report by @boegelbot |
I think my failure comes from a From the EasyBuild log (note, this was a different Clang version I was trying to build, but it ran into the same error and I didn't have the logs/build dir for the Clang in this PR anymore):
From https://stackoverflow.com/questions/73679415/build-llvm-16-master-fail-on-libunwind it seems it might be related to the failing configure tests for e.g.
Well, that wasn't a failure at all, it just was a warning! Still, the configure seems to conclude this is a failure (?). I'll try rerunning the build for this PR without Question: this flag is set for GCC. Since here, Clang is being build with Clang, should that receive the GCC optarch? I think we've had some discussion on this before. The tricky part is: it's not trivial that all GCC flags are understood by Clang. At the same time: Clang is not a toolchain, so can we even set an optarch for this...? |
Test report by @casparvl |
Well, at least without the
Now succeeds just fine. The new error is now in the sanity check:
|
Interesting, for me the
The only thing that tends to be different for us than for others is that we build with |
Ah, same issue as #18551 |
Test report by @casparvl |
Going in, thanks @boegel! |
(created using
eb --new-pr
)Needs: easybuilders/easybuild-easyblocks#2929