Need to migrate container to Debian 12 #6168
Comments
|
AFAICR with the image based on Debian 12 it is not possble to create packages for ppc853x-5.2 anymore (ppc853x is the single OLD_PPC_ARCH that we still support). Maybe one day the docker image must be updated and is not compatible with DSM 6 toolchains anymore. I know the github build action does not build packages for DSM 5.2, but I do not want to be the only one that has a backup of the debian 11 based docker image. |
|
Mabe we'd need to tag & release our container images, have a v5, v6 and v7.2 images or something. Updating to Debian 12 is easy, managing multiple images is something I wouldn't know where to start from, further with to spawning corresponding matrix using github-action. Maybe others have knowledge on this? |
I just pushed the spksrc image that was created 4 months ago as All that was needed was to create a (classic) personal access token to log in to ghcr and then it was possible to push a tagged Docker image... |
|
From there could we, for instance, add a dsm52 to the matrix enforcing the usage of this tagged image? And remaining to be using latest untagged? Once set we'd be good to update latest, non affecting dsn52 |
|
Migration to debian 12 completed #6183, closing. |
In order to build some package using the Synology DSM-7.2 toolchain we need to update our container image.
See my issue I've been facing intel/opencl-clang#546 (comment)
I believe the issue is due to my container image being Debian 11 with glibc-2.31 when building the NATIVE components wheras the Synology provided gcc-12.2 toolchain uses glibc-2.36, matching Debian 12 default libc version.
Related to #6166
The text was updated successfully, but these errors were encountered: