On Thu, 21 Dec 2023 at 14:57, Paul Gevers <elb...@debian.org> wrote: > The Release Team considers packages that are out-of-sync between testing > and unstable for more than 30 days as having a Release Critical bug in > testing [1]. Your package src:meson has been trying to migrate for 31 > days [2]. Hence, I am filing this bug. The version in unstable fails its > own autopkgtest on arm64 and i386 (and armel, but that's not a regression).
The reason for this is the following (on i86, but the same applies to arm64 too): 2428s = note: /usr/bin/ld: /usr/lib/gcc/i686-linux-gnu/13/../../../i386-linux-gnu/libz.a(inflate.o): in function `.L707': 2428s (.text+0x2c79): undefined reference to `__stack_chk_fail_local' 2428s /usr/bin/ld: /usr/lib/gcc/i686-linux-gnu/13/../../../i386-linux-gnu/libz.a(inflate.o): in function `inflateSync': 2428s (.text+0x3471): undefined reference to `__stack_chk_fail_local' 2428s /usr/bin/ld: /usr/lib/gcc/i686-linux-gnu/13/../../../i386-linux-gnu/libz.a(inftrees.o): in function `inflate_table': 2428s (.text+0xea7): undefined reference to `__stack_chk_fail_local' 2428s /usr/bin/ld: prog: hidden symbol `__stack_chk_fail_local' isn't defined 2428s /usr/bin/ld: final link failed: bad value 2428s collect2: error: ld returned 1 exit status This happens when mixing code compiled natively with code compiled with rustc. To the best of our knowledge, this is a Rust toolchain bug because the exact same compilation commands work on other platforms. The missing symbol has double leading underscores implying it is a compiler internal thing and the test we are using does not attempt to do anything magical, only compile and link C and Rust code together in the same binary.
