Skip to content
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

Update Perlmutter env #1587

Merged
merged 1 commit into from
Jan 18, 2025

Conversation

esseivaju
Copy link
Contributor

libsci was being linked twice, from OpenMP and the libsci module. This caused a warning at runtime which which was making the regression test fail to parse the JSON output... Disabling that module results in another error: a few CUDA test fail to link with the following error:
test/celeritas/CMakeFiles/celeritas_phys_Particle.dir/phys/Particle.test.cu.o: undefined reference to symbol 'dlclose@@GLIBC_2.2.5'. I looked at the symbol Particle.test.cu.o and there is indeed dlclose, it is not clear to me who is bringing that symbol there.

The failure only happens with VecGeom build, the ORANGE build has -ldl in the linker invocation, I don't know why it's different for VecGeom. Just work around it by setting CMAKE_EXE_LINKER_FLAGS...

@esseivaju esseivaju added documentation Documentation, examples, tests, and CI minor Minor internal changes or fixes labels Jan 18, 2025
@esseivaju esseivaju requested a review from sethrj January 18, 2025 01:28
Copy link
Member

@sethrj sethrj left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good to get that debugged; and cray libs are the worst. Thanks @esseivaju !

@pcanal the missing dl might be a RDC link magic issue 😬

@sethrj sethrj enabled auto-merge (squash) January 18, 2025 01:37
@sethrj sethrj disabled auto-merge January 18, 2025 01:38
@sethrj sethrj merged commit 4089f58 into celeritas-project:develop Jan 18, 2025
14 checks passed
@esseivaju
Copy link
Contributor Author

I checked a verbose CI run, and you can see that orange links to libdl here too, whereas VecGeom does not. It doesn't fail to link though, so maybe something in my environment is injecting that dependency in my VecGeom build 🤔

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Documentation, examples, tests, and CI minor Minor internal changes or fixes
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants