Your message dated Sun, 13 Sep 2026 15:37:23 +0000
with message-id <[email protected]>
and subject line Bug#1147168: fixed in libyuv 0.0.1971.20260904-2
has caused the Debian Bug report #1147168,
regarding libyuv: FTBFS on riscv64 with vector extension
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 [email protected]
immediately.)


-- 
1147168: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1147168
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: libyuv
Version: 0.0.1904.20250204-1
Severity: serious
Tags: ftbfs, patch
User: [email protected], Aurelien Jarno <[email protected]>
Usertags: riscv64
X-Debbugs-Cc: [email protected]

Dear Maintainer,

As aurel32 pointed out[0], two of the riscv64 buildds (rv-manda-02 and 
rv-manda-04) recently got their hardware upgraded to a CPU with vector 
extension ("V"). 

Now it had ftbfs on rv-manda-02:

```
error: unrecognized command-line option '-fno-vectorize'
error: unrecognized command-line option '-fno-slp-vectorize'
```
see: 
https://buildd.debian.org/status/fetch.php?pkg=libyuv&arch=riscv64&ver=0.0.1971.20260904-1&stamp=1788683665&raw=0

The upstream RISC-V configuration enables RVV by default and uses a 
Clang-based toolchain[1]. Rather than experimenting with a new build 
environment for this package, I simply disabled RVV support for the 
Debian riscv64 build.

Please let me know if any issues.


[0]: https://bugs.debian.org/1145420
[1]: 
https://salsa.debian.org/debian/libyuv/-/blob/master/riscv_script/riscv-clang.cmake?ref_type=heads

-- 
Regards,
--
  Bo YU

diff -Nru libyuv-0.0.1971.20260904/debian/changelog 
libyuv-0.0.1971.20260904/debian/changelog
--- libyuv-0.0.1971.20260904/debian/changelog   2026-09-05 02:06:21.000000000 
+0000
+++ libyuv-0.0.1971.20260904/debian/changelog   2026-09-08 15:56:36.000000000 
+0000
@@ -1,3 +1,10 @@
+libyuv (0.0.1971.20260904-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Disable RVV on riscv64. (Closes: #-1)
+
+ -- Bo YU <[email protected]>  Tue, 08 Sep 2026 15:56:36 +0000
+
 libyuv (0.0.1971.20260904-1) unstable; urgency=medium
 
   * New upstream snapshot.
diff -Nru libyuv-0.0.1971.20260904/debian/rules 
libyuv-0.0.1971.20260904/debian/rules
--- libyuv-0.0.1971.20260904/debian/rules       2026-09-05 02:06:21.000000000 
+0000
+++ libyuv-0.0.1971.20260904/debian/rules       2026-09-08 15:34:11.000000000 
+0000
@@ -27,9 +27,15 @@
   LIBYUV_TEST_FLAG = OFF
 endif
 
+# Disable the RVV on Debian RISC-V buildd
+ifeq ($(DEB_HOST_ARCH), riscv64)
+  LIBYUV_RVV_FLAG = OFF
+endif
+
 override_dh_auto_configure:
        dh_auto_configure -- \
            -DUNIT_TEST=$(LIBYUV_TEST_FLAG) \
+           -DUSE_RVV=$(LIBYUV_RVV_FLAG) \
            -DGTEST_SRC_DIR=/usr/src/googletest/googletest \
            $(NULL)
 

Attachment: signature.asc
Description: PGP signature


--- End Message ---
--- Begin Message ---
Source: libyuv
Source-Version: 0.0.1971.20260904-2
Done: Boyuan Yang <[email protected]>

We believe that the bug you reported is fixed in the latest version of
libyuv, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Boyuan Yang <[email protected]> (supplier of updated libyuv package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Sun, 13 Sep 2026 10:53:42 -0400
Source: libyuv
Architecture: source
Version: 0.0.1971.20260904-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers <[email protected]>
Changed-By: Boyuan Yang <[email protected]>
Closes: 1147168
Changes:
 libyuv (0.0.1971.20260904-2) unstable; urgency=medium
 .
   * debian/rules: Pass -DUSE_RVV=OFF on riscv64.
     Thanks to Bo YU for the analysis and patch. (Closes: #1147168)
Checksums-Sha1:
 7de070fc2e945155b178e94009c44bb043cdca5c 2594 libyuv_0.0.1971.20260904-2.dsc
 0eda4af0162fcaae4290483ef30cf5a6aa386ba8 8340 
libyuv_0.0.1971.20260904-2.debian.tar.xz
 213ccd5b92a3cecd06515eec62b0cce499b337cc 1387756 
libyuv_0.0.1971.20260904-2.git.tar.xz
 57cf2e3bb0cf21a22e9e6cef892f1600657edfdf 17712 
libyuv_0.0.1971.20260904-2_source.buildinfo
Checksums-Sha256:
 985b244ec336b5d8a86d69628a397a057fe059f6863ffb6f6cd24b8f5410beb1 2594 
libyuv_0.0.1971.20260904-2.dsc
 7bc03437450a111bf28cbc30dc79548c9d42b3a673c3edaef044d0796e6bce3d 8340 
libyuv_0.0.1971.20260904-2.debian.tar.xz
 9befcc0b0e7fe09859a8efba43c7f4a0395c755fa6fd426dfef2aeabe19aa888 1387756 
libyuv_0.0.1971.20260904-2.git.tar.xz
 0a8acb0650570351233c77fc3ccf23b334d7943407b3ccd16f353c67d3e48bcd 17712 
libyuv_0.0.1971.20260904-2_source.buildinfo
Files:
 aaad390f15af79cc3779e0245783627c 2594 libs optional 
libyuv_0.0.1971.20260904-2.dsc
 4956a8763f36cb53ca64483bfb57d68a 8340 libs optional 
libyuv_0.0.1971.20260904-2.debian.tar.xz
 934159ae8f614ab40440bcb2993f8e12 1387756 libs optional 
libyuv_0.0.1971.20260904-2.git.tar.xz
 f82dce5ad0da0f0e912c850cd6b13eb9 17712 libs optional 
libyuv_0.0.1971.20260904-2_source.buildinfo
Git-Tag-Info: tag=d15e394ed329961fb8af2a49e076a9e025ab536d 
fp=7e7729476d87d6f11d91accbc293e7b461825ace
Git-Tag-Tagger: Boyuan Yang <[email protected]>

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEN02M5NuW6cvUwJcqYG0ITkaDwHkFAmqmudgACgkQYG0ITkaD
wHkhWBAAw69P5uGKmVDQCAFqnRmnytx/+bALByA3riU3s6/xxS04xAV4Py7dYId4
I3Oe2c3M0AuHl0m9A4XLq8l2TG9AARouNVwCw+jXuuIHtuST2ZYONVeIzZHI//Sd
3HcplXp5P/R1TDq4RIFQ73JPo+RLpMztZLT+t3tBgL3xEk2IiYBH0lf5+riawevB
cxYIJquQPlo9iC7dK1El0pzCrJ+YZytC8HWaSfBimAMi4Zg7JNpWzjXwcEjscsFp
88RYDPbrQh8SpHJoVrVlIL9OwHb943hyYymEbT2OwwD8g+s1BhNyRhgq6EPjx+En
a4Rfvu1sKZhF3puliNpr0GlHYPC94Yv1KL1F6/HJDvxttVCGjeakr1FBAFf4/XWs
QG+hGBuyHOh7QBcCq1lXBmecr14g8juDJNnKjPCDIQ3ZCeiVVEVab2a3Nhq9DwMJ
I8X8XrrXtKndbdqKHotz4oFffZeWXgYDxTBfVinFVuW1OVijwQzyV5NupfkYIyuQ
q1AmZIgNCyFCzd5ayBgu4WrG7yx0s2K66AVyveTbOMb+ozYIoiIRhaEjplvDrvmr
9a/JKkRi8ZgYxFEm2wqRRGo0vhHtVMUe2n+Xn4wRnVUMVPdUxVh1a8Vp2ozGglr6
iHfVn48EQ8l1YHj4YomCAP/ZIV3qWbUePdFxi9Pe2LooRI+Ctsc=
=2jzB
-----END PGP SIGNATURE-----

Attachment: pgpe98AVud8I9.pgp
Description: PGP signature


--- End Message ---

Reply via email to