- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Issue with Backward Compatibility for ROCm 5.2+ – Libraries and Header Files Not Linking Properly
Hi everyone,
I’ve recently upgraded to ROCm 5.2 (following the reorganization outlined in the https://rocm.docs.amd.com/en/latest/conceptual/file-reorg.html, but I’m running into an issue with library and header file linking after the transition. Some of my applications are still referencing the old paths (like /opt/rocm-<ver>/<component>/lib), and I’ve noticed the soft links are causing build issues.
For example, I get errors like this when trying to compile:
fatal error: 'hip/hip_runtime.h' file not found
Even though the wrapper header files are supposed to be redirected, I’m still getting compilation failures. I’ve ensured that my code includes the new paths (/opt/rocm-<ver>/include/hip/hip_runtime.h), but the system seems to be falling back to the old structure.
I've also tried cleaning up the old symbolic links and explicitly setting the include paths in my CMakeLists.txt file:
include_directories(/opt/rocm-<ver>/include)
link_directories(/opt/rocm-<ver>/lib)
But the issue persists.
Has anyone else faced this issue with soft links and backward compatibility in ROCm 5.2+? Should I be handling the linking differently, or is there something I'm missing in terms of library paths or header includes?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
ROCm discussions have moved to https://github.com/ROCm/ROCm/discussions
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Your issue with ROCm 5.2+ likely stems from library path changes and broken symbolic links after the update. Here are a few steps to resolve it:
- Check Environment Variables – Ensure are correctly set. If not, add them manually.
- Verify Symlinks – If the system still looks for old paths, create symbolic links pointing to the new directory structure.
- Update CMake Paths – Explicitly set the correct include and library directories
- Clear Cached Builds – Delete old build files and recompile to prevent conflicts with outdated paths.
For photographers using AMD GPUs in photo editing, keeping software and hardware compatible is crucial for smooth performance. If anyone has faced similar compatibility issues with editing software after a GPU upgrade, feel free to share your experience!
