Your message dated Tue, 09 Jul 2024 02:36:25 +0000 with message-id <e1sr0ip-007tqp...@fasolo.debian.org> and subject line Bug#976557: fixed in kafs-client 0.5-5 has caused the Debian Bug report #976557, regarding kafs-client:FTBFS:compile failed(cc: error: unrecognized command-line option ‘-m64’) 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.) -- 976557: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976557 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Source: kafs-client Version: 0.5-4 Severity: important Tags: FTBFS, patch User: debian-ri...@lists.debian.org Usertags: riscv64 X-Debbugs-Cc: debian-ri...@lists.debian.org Dear kafs-client Maintainer, The kafs-client compile failed on riscv64 caused by "unrecognized command-line option ‘-m64’",the crucial log below: ``` make[1]: Entering directory '/<<PKGBUILDDIR>>' make -C src all make[2]: Entering directory '/<<PKGBUILDDIR>>/src' cc -Wdate-time -D_FORTIFY_SOURCE=2 -DVERSION="\"0.5\"" -Iinclude -DETCDIR=\"/etc\" -g -O2 -Wall -Wsign-compare -m64 -m64 -fPIC -o lib_cell_lookup.os -c lib_cell_lookup.c cc -Wdate-time -D_FORTIFY_SOURCE=2 -DVERSION="\"0.5\"" -Iinclude -DETCDIR=\"/etc\" -g -O2 -Wall -Wsign-compare -m64 -m64 -fPIC -o lib_cellserv.os -c lib_cellserv.c cc -Wdate-time -D_FORTIFY_SOURCE=2 -DVERSION="\"0.5\"" -Iinclude -DETCDIR=\"/etc\" -g -O2 -Wall -Wsign-compare -m64 -m64 -fPIC -o lib_dns_lookup.os -c lib_dns_lookup.c cc -Wdate-time -D_FORTIFY_SOURCE=2 -DVERSION="\"0.5\"" -Iinclude -DETCDIR=\"/etc\" -g -O2 -Wall -Wsign-compare -m64 -m64 -fPIC -o lib_object.os -c lib_object.c cc: error: unrecognized command-line option ‘-m64’ cc: error: unrecognized command-line option ‘-m64’ cc: error: unrecognized command-line option ‘-m64’ cc: error: unrecognized command-line option ‘-m64’ cc: error: unrecognized command-line option ‘-m64’ cc: error: unrecognized command-line option ‘-m64’ cc: error: unrecognized command-line option ‘-m64’ cc: error: unrecognized command-line option ‘-m64’ make[2]: *** [Makefile:34: lib_cell_lookup.os] Error 1 make[2]: *** Waiting for unfinished jobs.... make[2]: *** [Makefile:34: lib_cellserv.os] Error 1 make[2]: *** [Makefile:34: lib_dns_lookup.os] Error 1 make[2]: *** [Makefile:34: lib_object.os] Error 1 make[2]: Leaving directory '/<<PKGBUILDDIR>>/src' make[1]: *** [Makefile:43: all] Error 2 make[1]: Leaving directory '/<<PKGBUILDDIR>>' dh_auto_build: error: make -j4 "INSTALL=install --strip-program=true" returned exit code 2 make: *** [debian/rules:9: binary-arch] Error 25 dpkg-buildpackage: error: debian/rules binary-arch subprocess returned exit status 2 ``` The buildd log is here: https://buildd.debian.org/status/fetch.php?pkg=kafs-client&arch=riscv64&ver=0.5-4&stamp=1690546865&raw=0 My solution to this issue: add a patch to modify flag option "-m64". This solution is effective, and it has builded successfully in local.The patch is in the attachment. Please let me know wheather this solution can be accpted. Gui-Yue Best Regardsfix_error_flag_m64.debdiff
Description: Binary data
--- End Message ---
--- Begin Message ---Source: kafs-client Source-Version: 0.5-5 Done: Russ Allbery <r...@debian.org> We believe that the bug you reported is fixed in the latest version of kafs-client, 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 976...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Russ Allbery <r...@debian.org> (supplier of updated kafs-client 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: Mon, 08 Jul 2024 19:09:23 -0700 Source: kafs-client Architecture: source Version: 0.5-5 Distribution: unstable Urgency: medium Maintainer: Bill MacAllister <b...@ca-zephyr.org> Changed-By: Russ Allbery <r...@debian.org> Closes: 976557 1020881 1069757 1075106 Changes: kafs-client (0.5-5) unstable; urgency=medium . * Disable upstream build code that adds -m32 or -m64 based on the dynamically calculated word size. This code is unnecessary on Debian, where the default compiler behavior should be used, and causes problems on some Debian architectures that don't support -m64. Thanks to Yue Gui, Lucas Nussbaum, and wuruilong for the reports. (Closes: #976557, #1069757) * Add reproducible=+fixfilepath to DEB_BUILD_MAINT_OPTIONS to avoid embedding the build path into binaries, which breaks binary reproducibility. Thanks to Vagrant Cascadian for the report. (Closes: #1020881) * Add missing include to the kafs-check-config patch to support using the default cell, fixing build failures with GCC 14. Thanks to Matthias Klose for the report. (Closes: #1075106) * Update standards version to 4.7.0 (no changes required). Checksums-Sha1: b54f121033336a326568e27f89e3083ad7701f59 1805 kafs-client_0.5-5.dsc 45dd4c330c26cfc60f258a0e3171e399f28ac354 25512 kafs-client_0.5-5.debian.tar.xz Checksums-Sha256: 49a9145505d9f3cfe97c7ea31801f92f2474e48075db5bd3f417960de27505c8 1805 kafs-client_0.5-5.dsc 792ed2c85b5737fd2819a5c6c9fb0edc474a945d9ca26c8e5db47daae92da941 25512 kafs-client_0.5-5.debian.tar.xz Files: 814bbacffd40bf25ef31e9c9f9319dfd 1805 net optional kafs-client_0.5-5.dsc 47f2ca17667e5ed8597379efe41260ba 25512 net optional kafs-client_0.5-5.debian.tar.xz -----BEGIN PGP SIGNATURE----- iQEzBAEBCgAdFiEE1zk0tJZ0z1zNmsJ4fYAxXFc23nUFAmaMnLAACgkQfYAxXFc2 3nWmxAgAtoqSML/UA3dPGiNcidL87IzDN4moqD9L2WhDQorDuG+Q24+hrjXQ43en X5Ak7pJ7VUnngqBYTl3dO4h0EMcRyemQOxY2Ssiesz8EiuJljRErnNj7HovWfdld AV8ng7mWt7YH1WNz34UmCROzhWTacfwBrXgCrkIlATp3fCLua3X6krXNMp/BvEzg X4jW/cJcrIXLshKwFAi+ceQQ8C1gS+jO/6u4PkOxZ3aqxO0qdyFVVJ9B74UUDLbd 3bai6yw7jpxLCyq0wKnncd/A1OTSjCaemmK2cHYiDYzZe10rqQEpY+W/qV9yW1yA rGpv2UNpkZXVzVJRzqSaqYg64M85yA== =vNRO -----END PGP SIGNATURE-----pgpaZ_RlPJzvS.pgp
Description: PGP signature
--- End Message ---