{2023.06}[foss/2023a] Clang v16.0.6 #737
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Instance
|
|
Instance
|
|
bot: build repo:eessi.io-2023.06-software arch:x86_64/amd/zen3 |
Updates by the bot instance
|
Updates by the bot instance
|
|
New job on instance
|
|
bot: build repo:eessi.io-2023.06-software arch:x86_64/amd/zen3 |
Updates by the bot instance
|
Updates by the bot instance
|
|
New job on instance
|
|
bot: build repo:eessi.io-2023.06-software arch:x86_64/amd/zen3 |
Updates by the bot instance
|
Updates by the bot instance
|
Updates by the bot instance
|
|
New job on instance
|
|
Ok, same situation as reported here. Some executables have RPATH set, eg. looks just fine. But others dont: They also have the wrong interpreter set, for the same files. This is correct: But this is wrong: |
|
I don't get it, on our own system, it is correct: Of course, we are not using a sysroot, but we are using The installation has 3 stages... I'm guessing it does something like build Clang with GCC, then build Clang with Clang (not sure what the 3rd stage is). Maybe depending on which stage this is built in, does it set RPATH and interpreter correctly? I.e. maybe the rpath stuff gets lost somehow in later stages? |
|
I had the feeling I had seen this issue before. And I think I have. And fixed it. https://github.com/easybuilders/easybuild-easyblocks/pull/2799/files The issue back then (if I remember correctly) was that the stage 2 and 3 compilers weren't being wrapped by the RPATH wrappers. I think the same might be happening now. For some reason, the logic in the EasyBlock is, I guess, not working when using I'll need to check the logs again for those specific debugging statements surrounding the wrapping of the compilers... |
|
Ah, the link line for Don't be fooled by the The question is: why is it not calling the wrapper? If we know that, we can fix this. |
|
Not sure why this 'Re-run cmake no build system arguments' is happening, but this seems to be picking up on the full compiler path: That is probably, subsequently, used. I'm not quite sure why it would be different on our local system... Note that the |
|
Very strange: I cannot reproduce this on our local system when building with |
|
I also see (on the local build and the one on AWS): On the local system, it does not seem to overwrite the |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I've seen that it failed in this PR #637 (comment) but that's been a while, so let me just retry.
Also: on our system we also build with RPATH, and have no issues installing this Clang version... It'll be interesting to see what might be different in EESSI.