Your message dated Thu, 19 Sep 2024 17:04:18 +0000
with message-id <e1srkzm-00dzhq...@fasolo.debian.org>
and subject line Bug#1082166: fixed in libopaque 0.99.7-2
has caused the Debian Bug report #1082166,
regarding libopaque:FTBFS:build failure (‘-fcf-protection=full’ is not
supported)
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.)
--
1082166: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1082166
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libopaque
Version: 0.99.7-1
Severity: serious
Tags: FTBFS, patch
User: debian-ri...@lists.debian.org
Usertags: riscv64
X-Debbugs-Cc: debian-ri...@lists.debian.org
Dear libopaque Maintainer,
The package libopaque build failed on architectures other than x86 and
i386.The crucial buildd log below:
```
make[1]: Entering directory '/<<PKGBUILDDIR>>/src'
cc -g -O2 -Werror=implicit-function-declaration
-ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat
-Werror=format-security -Wall -pedantic -Wl,-z,defs -Wl,-z,relro
-Wl,-z,noexecstack -Wl,-z,now -fsanitize=signed-integer-overflow
-fsanitize-undefined-trap-on-error -fcf-protection=full -Iaux_ -o
common.o -c common.c
cc -g -O2 -Werror=implicit-function-declaration
-ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat
-Werror=format-security -Wall -pedantic -Wl,-z,defs -Wl,-z,relro
-Wl,-z,noexecstack -Wl,-z,now -fsanitize=signed-integer-overflow
-fsanitize-undefined-trap-on-error -fcf-protection=full -Iaux_
-I/usr/include/oprf -o opaque.o -c opaque.c
cc -g -O2 -Werror=implicit-function-declaration
-ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat
-Werror=format-security -Wall -pedantic -Wl,-z,defs -Wl,-z,relro
-Wl,-z,noexecstack -Wl,-z,now -fsanitize=signed-integer-overflow
-fsanitize-undefined-trap-on-error -fcf-protection=full -Iaux_ -o
aux_/kdf_hkdf_sha512.o -c aux_/kdf_hkdf_sha512.c
make -C utils/man
make[2]: Entering directory '/<<PKGBUILDDIR>>/src'
make[2]: warning: jobserver unavailable: using -j1. Add '+' to parent
make rule.
pandoc -s -o opaque.1 opaque.md
cc1: error: ‘-fcf-protection=full’ is not supported for this target
cc1: error: ‘-fcf-protection=full’ is not supported for this target
cc1: error: ‘-fcf-protection=full’ is not supported for this target
make[1]: *** [makefile:145: opaque.o] Error 1
make[1]: *** Waiting for unfinished jobs....
make[1]: *** [makefile:148: common.o] Error 1
make[1]: *** [makefile:148: aux_/kdf_hkdf_sha512.o] Error 1
make[2]: Leaving directory '/<<PKGBUILDDIR>>/src/utils/man'
make[1]: Leaving directory '/<<PKGBUILDDIR>>/src'
dh_auto_build: error: cd src && make -j4 "INSTALL=install
--strip-program=true" returned exit code 2
make: *** [debian/rules:11: binary-arch] Error 25
dpkg-buildpackage: error: debian/rules binary-arch subprocess returned
exit status 2
```
The full buildd log is here:
https://buildd.debian.org/status/fetch.php?pkg=libopaque&arch=riscv64&ver=0.99.7-1&stamp=1726708574&raw=0
My solution to this issue:
This error is caused by the fact that architectures other than x86 do not
support -fcf-protection=full. We can add a condition to check if the host
architecture is x86. If it is not x86, this CFLAG should be disabled.I have
finished above work ,and i have tested that on local, it works well.The
debpatch is in the attachment. Please let me know wheather this solution
can be accepted.
Gui-Yue
Best Regards
fix_libopaque_build_failure.patch
Description: Binary data
--- End Message ---
--- Begin Message ---
Source: libopaque
Source-Version: 0.99.7-2
Done: Joost van Baal-Ilić <joos...@debian.org>
We believe that the bug you reported is fixed in the latest version of
libopaque, 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 1082...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Joost van Baal-Ilić <joos...@debian.org> (supplier of updated libopaque 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 ftpmas...@ftp-master.debian.org)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Thu, 19 Sep 2024 18:09:18 +0200
Source: libopaque
Architecture: source
Version: 0.99.7-2
Distribution: unstable
Urgency: low
Maintainer: Joost van Baal-Ilić <joos...@debian.org>
Changed-By: Joost van Baal-Ilić <joos...@debian.org>
Closes: 1082166
Changes:
libopaque (0.99.7-2) unstable; urgency=low
.
* d/patches/0002-fix-fcf-protection=full_error.patch: added patch
contributed by Gui-Yue <yuemeng.gui@g.c>: Avoid using -fcf-protection=full
on architectures that do not support it. Closes: #1082166
Checksums-Sha1:
920f9f2a19425ba3f1f73d818c2259cef5412f99 2087 libopaque_0.99.7-2.dsc
3fbccea9fea921c94c8695e3ce6d187bc88687ec 6952 libopaque_0.99.7-2.debian.tar.xz
42b8982af702d205098aa004d97180e34012f5a0 5879
libopaque_0.99.7-2_source.buildinfo
Checksums-Sha256:
f7447aea28d7128d71c8012550646793319a326098f9f7c6188d006cf59bfc23 2087
libopaque_0.99.7-2.dsc
230ba25e1c97cd9b4322602cfb16474a353e59b4430afafe784bd22cb272e605 6952
libopaque_0.99.7-2.debian.tar.xz
efe562a7e4515157699c3efc42f9780243067de355c3e637cfe45b76d4a47893 5879
libopaque_0.99.7-2_source.buildinfo
Files:
9a6125f2d02e27b9cf1ad6821aced519 2087 utils optional libopaque_0.99.7-2.dsc
3c8c66afae0b25e83b835009678cf771 6952 utils optional
libopaque_0.99.7-2.debian.tar.xz
6b4134f6cf25295827b587ee61817ba0 5879 utils optional
libopaque_0.99.7-2_source.buildinfo
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEkqrZAbIbS8eaR6AwVPGmYxdIZxMFAmbsTfwACgkQVPGmYxdI
ZxNXAw//ZsuSjs8H7qxYh71ioRSZnuCYbPmuHSaheQh7DDBR04skgCRvPz8hNqD7
5N6xr41PqyK64nwwt6d1v7L4DfgOa2uVm/q4WWbmuPNWaePkzS2GyFh3JbxcUMdW
tvZcEZOa1tfbVhn+6gdVO48g5lRjs/nZpKBdZx7ZUIEYiJKhXqpA4rai4kMOmSP3
8/Xle9crtTBoXygLD8hmB1CH6YIV1RKv0Ehns5AWMIRQU8+tP4eHeohzSvgPu9Y9
UCQTHTx7y262yM0MlNejms8w7e6cqzXeNrl1ta3JxJ/qUMbYhBDzuRPC3XCV9gc5
PPLQ0NagMIkuDLnQkCloOLMr1rgAT6tPft2FdHGjXBHZXy+OA0t+D0Tgd7R41ivU
DqGyFmDAA6gFDKbwnT2JxNFOwdg+Vl2Xz38N3NLLDCzOo9rPcyMVffGiMdyFfNtt
TOD2jVsG5qGi3dLBn52povuk0X7nCmjHHxPbv05UXiIM5gnx1yLZcVdouLABeFmC
U/ZQtHL5A2BCWZYa8JzPl6qZXdbggreEUqmFPDivdQcHtyjGCxveN+Sxp1zdd6A1
0ePDoCugD4Me0zXfhmDnmeG2CgbX+9WU4Ii90JzSwdYyPa/KUG/bribQ12TCwOQZ
3ySvO1BG/xedUP9AAK7NHWYPeBJ56nZbhZQeBykRCrxN0w9IQjc=
=m06K
-----END PGP SIGNATURE-----
pgpKhpn4g3oTa.pgp
Description: PGP signature
--- End Message ---
