-
Notifications
You must be signed in to change notification settings - Fork 43
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
Use system's default rocgdb instead of AOMP's #853
base: aomp-dev
Are you sure you want to change the base?
Conversation
rocgdb requires libpython.so which is more likely to be found by the system's default rocgdb. The one in AOMP/bin/rocgdb complains about missing libpython.so file.
I don't think we want to test the sytem's rocgdb (by accident or on purpose). |
I also wonder why we don’t want to test the rocgdb we built and packed ? |
I am seeing a different complaint instead of a missing libpython:
Seems to have started on:
Works before that date:
|
We are actually staging python libs into COD to allow tools that are linked to specific versions of python shared objects to work. If you see a missing python lib error, paste in the exact error message and the system you saw it on. |
I am getting same error irrespective of using 2024-03-07 build or 2023-12-04 build. Note: results are on r11
|
Looking back at the original thread on the 'CI OpenMP compiler daily triage group' teams chat motivated the staging fix, you will need to do the following on a 22.04 system:
Also note that setting the above env vars also fixes the 'amd-dbgapi library version mismatch, got 0.70.1, need 0.71+' error now seen on 20.04 systems. Not a "fix" so much as a workaround for running rocgdb built on an older OS. Not that it helps us in this situation, but the moral of the story is don't link your product with the python shared objects. There is just no backward compatibility guaranteed (at least not building on 20.04 and running on 22.04). |
The 'amd-dbgapi library version mismatch, got 0.70.1, need 0.71+' error is even a problem on the same system where rocgdb was built. Without specifying LD_LIBRARY_PATH, it is picking up the library from the system /opt/rocm:
Gets the staged librocm-dbgapi.so.0 with the workaround:
This issue feels like a cmake bug in rocgdb, as it should try to pick up shared libraries relative to it's installed location first. |
rocgdb requires libpython.so which is more likely to be found by the system's default rocgdb.
The one in AOMP/bin/rocgdb complains about missing libpython.so file.