| Patch | Description | Author | Forwarded | Bugs | Origin | Last update |
|---|---|---|---|---|---|---|
| 0003-clean-amd64-flags.patch | cleanup architecture specific build flags This should prevent some failure to build from source on non-amd64 targets. | tienne Mollier <emollier@debian.org> | yes | 2022-04-12 | ||
| 0006-CMakeLists.txt-do-not-enforce-fPIE.patch | CMakeLists.txt: do not enforce -fPIE. When built with LTO enabled, the linking of liboam.so chokes on the following error, which is somewhat similar to the Debian bug #1030876 affecting PA-RISC, although the symptoms subtly differs in that it suggests to build using -fPIC: /usr/bin/ld: /tmp/cc0wF8Kx.ltrans0.ltrans.o: relocation R_X86_64_PC32 against symbol `_ZTVSt9exception@@GLIBCXX_3.4' can not be used when making a shared object; recompile with -fPIC The -fPIC argument is passed appropriately down to the build command, however it looks to be erased by the late introduction of -fPIE flag by upstream build system. Erasing this flag allows the build to go through, both with LTO and on PA-RISC. |
=?utf-8?q?=C3=89tienne_Mollier?= <emollier@debian.org> | yes | debian upstream | 2023-08-27 | |
| 0007-rocm_smi64-soversion.patch | forcefully set rocm_smi64 soversion to 1. Upstream soversion is at 5 for a while, but Debian's soversion has been set to 1 in the beginning of the rocm-smi-lib package. This is probably erroneous, and the library should probably be better off being synchronized with upstream so there is some kind of ABI compatibility between the two distributions. . FIXME: please use upstream soversion next time an ABI breakage justifies an SOVERSION bump, instead of just incrementing the present version by one. |
tienne Mollier <emollier@debian.org> | not-needed | 2023-09-17 | ||
| 0008-typo.patch | fix typos caught by lintian. | tienne Mollier <emollier@debian.org> | yes | upstream | 2023-09-17 |