Your message dated Mon, 27 Nov 2023 16:15:03 +0800 with message-id <189aa38a-02f6-4119-b25c-29fcf2aea...@sail.ng> and subject line Re: Removed package(s) from unstable has caused the Debian Bug report #931002, regarding rust-coresimd: FTBFS (unrecognized platform-specific intrinsic function: `x86_rdrand16_step`unrecognized platform-specific intrinsic function: `x86_rdrand16_step`) to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 931002: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931002 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: src:rust-coresimd Version: 0.1.2-1 Severity: serious Tags: ftbfs Dear maintainer: I tried to build this package in buster but it failed: -------------------------------------------------------------------------------- [...] debian/rules build-arch dh build-arch --buildsystem cargo dh_update_autotools_config -a -O--buildsystem=cargo dh_autoreconf -a -O--buildsystem=cargo dh_auto_configure -a -O--buildsystem=cargo debian cargo wrapper: options, profiles, parallel: ['parallel=2'] [] ['-j2'] debian cargo wrapper: rust_type, gnu_type: x86_64-unknown-linux-gnu, x86_64-linux-gnu debian cargo wrapper: linking /usr/share/cargo/registry/* into /<<PKGBUILDDIR>>/debian/cargo_registry/ dh_auto_build -a -O--buildsystem=cargo debian/rules override_dh_auto_test make[1]: Entering directory '/<<PKGBUILDDIR>>' export RUSTC_BOOTSTRAP=1; \ dh_auto_test debian cargo wrapper: options, profiles, parallel: ['parallel=2'] [] ['-j2'] debian cargo wrapper: rust_type, gnu_type: x86_64-unknown-linux-gnu, x86_64-linux-gnu debian cargo wrapper: running subprocess (['env', 'RUST_BACKTRACE=1', '/usr/bin/cargo', '-Zavoid-dev-deps', 'build', '--verbose', '--verbose', '-j2', '--target', 'x86_64-unknown-linux-gnu'],) {} Compiling coresimd v0.1.2 (/<<PKGBUILDDIR>>) Running `rustc --crate-name build_script_build build.rs --color never --crate-type bin --emit=dep-info,link -C debuginfo=2 -C metadata=4c9f73b74e941fa4 -C extra-filename=-4c9f73b74e941fa4 --out-dir /<<PKGBUILDDIR>>/target/debug/build/coresimd-4c9f73b74e941fa4 -C incremental=/<<PKGBUILDDIR>>/target/debug/incremental -L dependency=/<<PKGBUILDDIR>>/target/debug/deps` Running `/<<PKGBUILDDIR>>/target/debug/build/coresimd-4c9f73b74e941fa4/build-script-build` [coresimd 0.1.2] cargo:rustc-env=TARGET=x86_64-unknown-linux-gnu Running `rustc --crate-name coresimd src/lib.rs --color never --crate-type lib --emit=dep-info,link -C debuginfo=2 -C metadata=709a32ec1dae0a97 -C extra-filename=-709a32ec1dae0a97 --out-dir /<<PKGBUILDDIR>>/target/x86_64-unknown-linux-gnu/debug/deps --target x86_64-unknown-linux-gnu -C incremental=/<<PKGBUILDDIR>>/target/x86_64-unknown-linux-gnu/debug/incremental -L dependency=/<<PKGBUILDDIR>>/target/x86_64-unknown-linux-gnu/debug/deps -L dependency=/<<PKGBUILDDIR>>/target/debug/deps -C debuginfo=2 --cap-lints warn -C linker=x86_64-linux-gnu-gcc -C link-arg=-Wl,-z,relro --remap-path-prefix /<<PKGBUILDDIR>>=/usr/share/cargo/registry/coresimd-0.1.2` error: unrecognized platform-specific intrinsic function: `x86_rdrand16_step` --> src/coresimd/x86/rdrand.rs:6:5 | 6 | fn x86_rdrand16_step() -> (u16, i32); | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ error: unrecognized platform-specific intrinsic function: `x86_rdrand32_step` --> src/coresimd/x86/rdrand.rs:7:5 | 7 | fn x86_rdrand32_step() -> (u32, i32); | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ error: unrecognized platform-specific intrinsic function: `x86_rdseed16_step` --> src/coresimd/x86/rdrand.rs:8:5 | 8 | fn x86_rdseed16_step() -> (u16, i32); | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ error: unrecognized platform-specific intrinsic function: `x86_rdseed32_step` --> src/coresimd/x86/rdrand.rs:9:5 | 9 | fn x86_rdseed32_step() -> (u32, i32); | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ error: unrecognized platform-specific intrinsic function: `x86_rdrand64_step` --> src/coresimd/x86_64/rdrand.rs:6:5 | 6 | fn x86_rdrand64_step() -> (u64, i32); | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ error: unrecognized platform-specific intrinsic function: `x86_rdseed64_step` --> src/coresimd/x86_64/rdrand.rs:7:5 | 7 | fn x86_rdseed64_step() -> (u64, i32); | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ error: aborting due to 6 previous errors error: Could not compile `coresimd`. Caused by: process didn't exit successfully: `rustc --crate-name coresimd src/lib.rs --color never --crate-type lib --emit=dep-info,link -C debuginfo=2 -C metadata=709a32ec1dae0a97 -C extra-filename=-709a32ec1dae0a97 --out-dir /<<PKGBUILDDIR>>/target/x86_64-unknown-linux-gnu/debug/deps --target x86_64-unknown-linux-gnu -C incremental=/<<PKGBUILDDIR>>/target/x86_64-unknown-linux-gnu/debug/incremental -L dependency=/<<PKGBUILDDIR>>/target/x86_64-unknown-linux-gnu/debug/deps -L dependency=/<<PKGBUILDDIR>>/target/debug/deps -C debuginfo=2 --cap-lints warn -C linker=x86_64-linux-gnu-gcc -C link-arg=-Wl,-z,relro --remap-path-prefix /<<PKGBUILDDIR>>=/usr/share/cargo/registry/coresimd-0.1.2` (exit code: 1) dh_auto_test: /usr/share/cargo/bin/cargo build returned exit code 101 make[1]: *** [debian/rules:8: override_dh_auto_test] Error 101 make[1]: Leaving directory '/<<PKGBUILDDIR>>' make: *** [debian/rules:4: build-arch] Error 2 dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit status 2 -------------------------------------------------------------------------------- The build was made in my autobuilder with "dpkg-buildpackage -B" and it also fails here: https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/rust-coresimd.html where you can get a full build log if you need it. If this is really a bug in one of the build-depends, please use reassign and affects, so that this is still visible in the BTS web page for this package. Thanks.
--- End Message ---
--- Begin Message ---On Thu, 8 Dec 2022 01:59:44 +0800 Blair Noctis <n...@sail.ng> wrote: > On Sun, 8 Sep 2019 13:58:06 +0200 (CEST) Santiago Vila <sanv...@unex.es> > wrote:> > This was automatically closed by ftpmaster because the package was > > removed from unstable, but this still does not fix the FTBFS problem > > in stable. > > It's now only in oldstable, nothing depends on it, and it requires a nightly > rustc which we currently don't have. Is it safe to close this? Closing it as no one seems to care about this anymore, and at this point of time (2023-11-27) it only exists in oldoldstable aka 10/buster. -- Sdrager, Blair NoctisOpenPGP_signature.asc
Description: OpenPGP digital signature
--- End Message ---