Source: rustc, meson Control: found -1 rustc/1.56.0+dfsg1-2 Control: found -1 meson/0.59.2-1 Severity: serious Tags: sid bookworm X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: breaks needs-update
Dear maintainer(s), With a recent upload of rustc the autopkgtest of meson fails in testing when that autopkgtest is run with the binary packages of rustc from unstable. It passes when run with only packages from testing. In tabular form: pass fail rustc from testing 1.56.0+dfsg1-2 meson from testing 0.59.2-1 versioned deps [0] from testing from unstable all others from testing from testing I copied some of the output at the bottom of this report. Currently this regression is blocking the migration of rustc to testing [1]. Due to the nature of this issue, I filed this bug report against both packages. Can you please investigate the situation and reassign the bug to the right package? More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [0] You can see what packages were added from the second line of the log file quoted below. The migration software adds source package from unstable to the list if they are needed to install packages from rustc/1.56.0+dfsg1-2. I.e. due to versioned dependencies or breaks/conflicts. [1] https://qa.debian.org/excuses.php?package=rustc https://ci.debian.net/data/autopkgtest/testing/amd64/m/meson/16267457/log.gz The Meson build system Version: 0.59.2 Source dir: /tmp/autopkgtest-lxc.868hskgl/downtmp/build.URn/src/test cases/rust/5 polyglot static Build dir: /tmp/autopkgtest-lxc.868hskgl/downtmp/build.URn/src/b 538284a9dc Build type: native build Project name: static rust and c polyglot executable Project version: undefined C compiler for the host machine: cc (gcc 10.3.0 "cc (Debian 10.3.0-11) 10.3.0") C linker for the host machine: cc ld.bfd 2.37 Rust compiler for the host machine: rustc -C linker=cc (rustc 1.56.0) Rust linker for the host machine: rustc -C linker=cc ld.bfd 2.37 Host machine cpu family: x86_64 Host machine cpu: x86_64 Library dl found: YES Run-time dependency threads found: YES Build targets in project: 2 Found ninja-1.10.1 at /usr/bin/ninja [1/3] Compiling C object prog.p/prog.c.o [2/3] Compiling Rust source '../test cases/rust/5 polyglot static/stuff.rs' [3/3] Linking target prog FAILED: prog cc -o prog prog.p/prog.c.o -Wl,--as-needed -Wl,--no-undefined -Wl,--start-group libstuff.a -ldl -Wl,--end-group -pthread /usr/bin/ld: libstuff.a(std-80e93fdce0e07191.std.9561c7b1-cgu.5.rcgu.o): in function `std::f64::<impl f64>::lerp': /usr/src/rustc-1.56.0//library/std/src/f64.rs:(.text._ZN3std3f6421_$LT$impl$u20$f64$GT$4lerp17h11b1be7b614aa463E+0x22): undefined reference to `fma' /usr/bin/ld: libstuff.a(std-80e93fdce0e07191.std.9561c7b1-cgu.6.rcgu.o): in function `std::f32::<impl f32>::lerp': /usr/src/rustc-1.56.0//library/std/src/f32.rs:(.text._ZN3std3f3221_$LT$impl$u20$f32$GT$4lerp17he122406d489ebe9dE+0x20): undefined reference to `fmaf' collect2: error: ld returned 1 exit status ninja: build stopped: subcommand failed. ninja explain: deps for 'libstuff.a' are missing ninja explain: libstuff.a is dirty ninja explain: deps for 'prog.p/prog.c.o' are missing ninja explain: prog.p/prog.c.o is dirty ninja explain: libstuff.a is dirty ninja explain: prog is dirty autopkgtest [11:37:48]: test exhaustive
OpenPGP_signature
Description: OpenPGP digital signature