Your message dated Mon, 25 Oct 2021 06:33:23 +0000
with message-id <[email protected]>
and subject line Bug#997807: fixed in hyperic-sigar 1.6.4+dfsg-6
has caused the Debian Bug report #997807,
regarding hyperic-sigar: FTBFS on riscv64: gcc: 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 [email protected]
immediately.)
--
997807: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997807
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: hyperic-sigar
Version: 1.6.4+dfsg-5
Severity: wishlist
Tags: ftbfs patch upstream
User: [email protected]
Usertags: riscv64
Dear maintainer,
hyperic-sigar fails to build from source on riscv64:
| jni-compile:
|
| jni-cc:
| [mkdir] Created dir:
/<<PKGBUILDDIR>>/bindings/java/build/obj/riscv64-linux/lib
| [echo] jni libname=sigar
| [cc] 13 total files to be compiled.
| [cc] gcc: error: unrecognized command-line option ‘-m64’
|
| BUILD FAILED
| /<<PKGBUILDDIR>>/bindings/java/hyperic_jni/jni-build.xml:224: The following
error occurred while executing this line:
| /<<PKGBUILDDIR>>/bindings/java/hyperic_jni/jni-build.xml:270: gcc failed with
return code 1
|
| Total time: 1 minute 21 seconds
| dh_auto_build: error: cd bindings/java && ant -Duser.name debian returned
exit code 1
| make: *** [debian/rules:6: binary-arch] Error 25
| dpkg-buildpackage: error: debian/rules binary-arch subprocess returned exit
status 2
The full build log is available there:
https://buildd.debian.org/status/fetch.php?pkg=hyperic-sigar&arch=riscv64&ver=1.6.4%2Bdfsg-5&stamp=1630049820&raw=0
The issue is that -m64 is not understood by GCC on riscv64. This is also
the case on a few other architectures, and I have noticed that you
already have a patch for that. I have tried to extend it (see attached
patch), and hyperic-sigar builds fine on riscv64. Could you please
consider applying it in the future uploads?
Note however that instead of maintaining a long list of architectures
where -m64 is not needed might not be the best way, as this flag is
basically understood only on x86, p(ower)pc*, sparc* and s390*. In
addition this flag is basically not needed for a standard Debian
installation, where gcc already defaults to the correct bitness. You
might therefore want to simply drop those few lines.
Regards,
Aurelien
--- hyperic-sigar-1.6.4+dfsg/debian/patches/no-m64-mips-arm.diff
+++ hyperic-sigar-1.6.4+dfsg/debian/patches/no-m64-mips-arm.diff
@@ -2,13 +2,14 @@
===================================================================
---
hyperic-sigar-1.6.4+dfsg.orig/bindings/java/hyperic_jni/src/org/hyperic/jni/ArchNameTask.java
2014-11-03 13:25:30.620030459 +0800
+++
hyperic-sigar-1.6.4+dfsg/bindings/java/hyperic_jni/src/org/hyperic/jni/ArchNameTask.java
2014-11-03 13:25:30.608030459 +0800
-@@ -75,7 +75,8 @@
+@@ -75,7 +75,9 @@
if (ArchName.is64()) {
getProject().setProperty("jni.arch64", "true");
if (ArchLoader.IS_LINUX) {
- if (!osArch.equals("ia64")) {
+ if (!osArch.equals("ia64") && !osArch.equals("mips64el")
-+ && !osArch.equals("mips64") &&
!osArch.equals("aarch64")) {
++ && !osArch.equals("mips64") && !osArch.equals("aarch64")
++ && !osArch.equals("riscv64")) {
getProject().setProperty("jni.gccm", "-m64");
}
}
--- End Message ---
--- Begin Message ---
Source: hyperic-sigar
Source-Version: 1.6.4+dfsg-6
Done: Andrius Merkys <[email protected]>
We believe that the bug you reported is fixed in the latest version of
hyperic-sigar, 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.
Andrius Merkys <[email protected]> (supplier of updated hyperic-sigar 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: Mon, 25 Oct 2021 02:02:47 -0400
Source: hyperic-sigar
Architecture: source
Version: 1.6.4+dfsg-6
Distribution: experimental
Urgency: medium
Maintainer: Debian Java Maintainers
<[email protected]>
Changed-By: Andrius Merkys <[email protected]>
Closes: 997807
Changes:
hyperic-sigar (1.6.4+dfsg-6) experimental; urgency=medium
.
* Team upload.
* Disabling cc -m64 cc flag on all architectures (Closes: #997807).
* Renaming no-m64-mips-arm.diff -> no-m64.patch.
Checksums-Sha1:
5806ae45458ac42fd3aa6f42fe5a44c102da6308 2096 hyperic-sigar_1.6.4+dfsg-6.dsc
9a4fe9d59d8f92883049ecd32230bfa0fd506c03 4940
hyperic-sigar_1.6.4+dfsg-6.debian.tar.xz
f20765eefe9e22e5f619532465e52a6db23a0d25 9088
hyperic-sigar_1.6.4+dfsg-6_source.buildinfo
Checksums-Sha256:
425191e845e118c8875196206299cf940eee7d977bbdf4606f050f90a75e193d 2096
hyperic-sigar_1.6.4+dfsg-6.dsc
ca8b6af899c1d2231e775eb135909ed3bbe70b1d38c0e50097cfac7680b0bf23 4940
hyperic-sigar_1.6.4+dfsg-6.debian.tar.xz
8262470b7b004eeb2b0f0abf727343e744dd4917d9a8e9deaf598e590182a414 9088
hyperic-sigar_1.6.4+dfsg-6_source.buildinfo
Files:
5aa618fa917cd8ca27ed6403f660ebe1 2096 java optional
hyperic-sigar_1.6.4+dfsg-6.dsc
23ecf12fec7457833c16aad62774c5d0 4940 java optional
hyperic-sigar_1.6.4+dfsg-6.debian.tar.xz
24af9746e66b1e2161d570f9c715e03c 9088 java optional
hyperic-sigar_1.6.4+dfsg-6_source.buildinfo
-----BEGIN PGP SIGNATURE-----
iQJGBAEBCgAwFiEEdyKS9veshfrgQdQe5fQ/nCc08ocFAmF2Sk4SHG1lcmt5c0Bk
ZWJpYW4ub3JnAAoJEOX0P5wnNPKHFNYP/ilBb5hVQTws1CLYR7ewzRbYNePpFdzk
+qJmADjq50xgUQGKs+nHlRCage//eIxlHdMGKyC/5rW096dHP5Qa8093HboKbLrK
iXgYCoY+hdJ0JPawBVKAmiyU84z3AcFLozzAAUpjIYAusXr9zsfMjtrRLTRQlnzf
gLEi7F82e99Zr5VqLNKVKGT1SsX08Nt0TOniiQsa5iC9INcDVN8xS6hYt2tYhXr6
KAVbM168FJZOo0bvC3if8bLuQs6/T7WN0dV16MMdOAUKcQ19PMYzPgemArKMIqmx
ys/pW6AiB0nEgbJB918RORdtF4Y5gJDvPQHcygtlgNp/965Bk+nazAnG1PEtXPty
isajDjN3dwT+Cnafs0RPBCQcav4rtOkBI72iduSk4XcDy7qrXgnP9T8jxRyOI5U+
BngfIKxF3LKnHYssCl1u4nND1KBG6EncAoOXHGTIXnucTuSkHEPvcPAaYxS5N8Ce
YO3Tajf9HWoTpjjJZTyr4WVSprqI6RIVAIgZtWm9zzktRDAYQuwfw7sMBZy1AVMU
CVXHxA0c4NhZfc5KLDg+IV1XtaoQZZeweoIsUinZkyUKCMZOPAiDMo/v0Ez9LEKU
9TW86bZs4FZNI1nRwQmzXkIB5u0I/Rm0H13khtIZhsaiVeGg06PbcMK/PaZrfOWS
lK88vAdDrF7n
=9UiQ
-----END PGP SIGNATURE-----
--- End Message ---
__
This is the maintainer address of Debian's Java team
<https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-java-maintainers>.
Please use
[email protected] for discussions and questions.
