GPU GEOS : Mismatched template definition usage in coreComponents/physicsSolvers #3496
Comments
drmichaeltcvx
added
type: bug
|
When we force set |
|
I used the branch ' Unfortunately, the base class FiniteElementBase mismatch error now moved to another pair of derived classes: |
|
Here are excerpts from the failing build process with Are the problems caused by some missed ' |
|
@drmichaeltcvx It is difficult for me to think that this would have any dependence on hardware (Intel vs AMD). I would think this has to be something in the software stack. The dockerfiles that generate our TPL environment for CI are here: You should look on dockerhub for a base image with closest match to your Linux distribution/version. I don't know if you have provided the linux distribution you are on. Once you have a suitable base image with a hopefully equivalent software stack, adding the image should involve copying one of the dockerfiles, replacing the base image, and modifying the packages to mimic your software stack. here are some examples of base images: |
|
Thanks Randy,
How do you generate the CI image for GEOS? Do you have dockerfiles for this?
Michael
From: Randolph Settgast ***@***.***>
Sent: Wednesday, January 22, 2025 12:15 PM
To: GEOS-DEV/GEOS ***@***.***>
Cc: Thomadakis, Michael ***@***.***>; Mention ***@***.***>
Subject: [**EXTERNAL**] Re: [GEOS-DEV/GEOS] GPU GEOS : Mismatched template definition usage in coreComponents/physicsSolvers (Issue #3496)
Be aware this external email contains an attachment and/or link.
Ensure the email and contents are expected. If there are concerns, please submit suspicious messages to the Cyber Intelligence Center using the Report Phishing button.
@drmichaeltcvx<https://github.com/drmichaeltcvx> It is difficult for me to think that this would have any dependence on hardware (Intel vs AMD). I would think this has to be something in the software stack. The dockerfiles that generate our TPL environment for CI are here:
https://github.com/GEOS-DEV/thirdPartyLibs/tree/master/docker
You should look on dockerhub for a base image with closest match to your Linux distribution/version. I don't know if you have provided the linux distribution you are on. Once you have a suitable base image with a hopefully equivalent software stack, adding the image should involve copying one of the dockerfiles, replacing the base image, and modifying the packages to mimic your software stack.
here are some examples of base images:
https://hub.docker.com/_/ubuntu
https://hub.docker.com/r/rockylinux/rockylinux
https://hub.docker.com/_/fedora
-
Reply to this email directly, view it on GitHub<#3496 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AS6ZG2Q3WGOY53IRTB75GN32L7N3FAVCNFSM6AAAAABTZIN3K6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMMBXHEZTSOJQGQ>.
You are receiving this because you were mentioned.Message ID: ***@***.******@***.***>>
|
|
I am providing here the configure and build logs for a failed GPU build. Let's go through these first to see if we can identify any useful information that could point to where the problem starts. TPL builds fine for GPUs on our s/w stack. CMake command
Make-build-2025-01-17-134202.log Please comment |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
Building GEOS (latest "
develop" and TPL "master") with CUDA, runs into conflicting definitions for certain templates.To Reproduce
Steps to reproduce the behavior:
Try to provide minimal test cases where possible to help isolate the problem.
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Platform (please complete the following information):
Additional context
Output from
make allThe text was updated successfully, but these errors were encountered: