Opened 6 years ago
Closed 6 years ago
#5033 closed defect (invalid)
gloox fails to build on OpenSuse
Reported by: | elexis | Owned by: | |
---|---|---|---|
Priority: | Must Have | Milestone: | |
Component: | Build & Packages | Keywords: | |
Cc: | Itms | Patch: |
Description
As reported on https://bugzilla.opensuse.org/show_bug.cgi?id=1078834 gloox does not build on OpenSuse.
Change History (6)
comment:1 by , 6 years ago
Cc: | added |
---|---|
Component: | Multiplayer lobby → Build & Packages |
comment:2 by , 6 years ago
Milestone: | Alpha 23 |
---|---|
Resolution: | → worksforme |
Status: | new → closed |
The issue is that the gloox anonymous gnutls client/server implementation doesn't pass a specific option to gnutls, which needs to be explicitly requested for gnutls >= 3.6.0.
We don't have anything to do since the bundled gloox for Windows doesn't use gnutls. For Linux, the fix will have to be applied by package maintainers if they depend on a recent gnutls, until the patch is merged upstream (the gloox bugtracker is unreachable at the moment). For macOS, we don't build with gnutls, which is an indication we do not use that code at all.
comment:4 by , 6 years ago
This bug only affected gloox unit tests. Since 0 A.D. doesn't run these, I don't see this affecting the 0 A.D. code in any way on any platform.
Reported the gloox test failure for GnuTLS 3.6.0 regardless at https://bugs.camaya.net/ticket/?id=279 now that the bugtracker is online again. So maintainers won't have to be bothered again when they want to build gloox only for 0 A.D.
TLS in use as of r21875. But reading the INSTALL file and the gloox FAQ https://camaya.net/gloox/faq/ it seems one cannot compile without TLS support, but only has the choice between OpenSSL and GnuTLS. (I asked Imarok who built the last gloox windows build to confirm the TLS use on windows)
comment:5 by , 6 years ago
Resolution: | worksforme |
---|---|
Status: | closed → reopened |
comment:6 by , 6 years ago
Resolution: | → invalid |
---|---|
Status: | reopened → closed |
(nitpicking - valid bugreport but for upstream.)
I am moving the Component as that actually doesn't break the lobby for us, but rather prevents the packaging of 0 A.D. on OpenSuse.