On 2024-09-24 09:18:45, Otto Kekäläinen wrote: > Hi! > > We've overhauled the README.md at > https://salsa.debian.org/salsa-ci-team/pipeline to be as complete as > possible, yet clear and to the point. If you are not yet using Salsa > CI for pre-upload quality assurance for your package, you might want > to check out what Salsa CI offers, or just review that your current > usage is optimal. > > We also added a RUNNERS.md for those who want to experiment with > customer runners or donate CI capacity to Debian. > > Feedback and improvement suggestions are also welcome as Merge > Requests are via email.
I just added a barebone config for one of my packages, and while the pipeline worked, I got an error for the arm64 cross-compile that seems to be due to tooling issues: make[1]: Entering directory '/builds/debian/mt-st/debian/output/source_dir' echo '#define VERSION "1.7"' > version.h aarch64-linux-gnu-gcc -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/builds/debian/mt-st/debian/output/source_dir=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -mbranch-protection=standard -Wl,-z,relro -Wl,-z,now -DDEFTAPE='"/dev/tape"' -o mt mt.c aarch64-linux-gnu-gcc -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/builds/debian/mt-st/debian/output/source_dir=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -mbranch-protection=standard -Wl,-z,relro -Wl,-z,now -DDEFTAPE='"/dev/tape"' -o stinit stinit.c ccache: error: execute_noreturn of /usr/bin/aarch64-linux-gnu-gcc failed: Exec format error make[1]: *** [Makefile:44: stinit] Error 1 make[1]: *** Waiting for unfinished jobs.... ccache: error: execute_noreturn of /usr/bin/aarch64-linux-gnu-gcc failed: Exec format error The log is at https://salsa.debian.org/debian/mt-st/-/jobs/6343717. While this is not marked as blocking, just warning, it's still annoying. Is this a known issue? I would like to keep the cross-build, and I see nothing about this being problematic in the docs. thanks! iustin
