| Summary: | dev-qt/qtnetwork-5.9.4 with dev-qt/qtcore-5.9.4 - macro redefinition of QT_LINKED_OPENSSL in /usr/include/qt5/Gentoo/gentoo-qconfig.h differs from definition in /usr/include/qt5/QtNetwork/qtnetwork-config.h | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | paul |
| Component: | Current packages | Assignee: | Qt Bug Alias <qt> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | bertrand, dev, drmccoy, sam |
| Priority: | Normal | Keywords: | InOverlay |
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
Happens for me as well, when compiler user-code that uses QtMultimedia, because that depends on QtNetwork. /usr/include/qt5/QtNetwork/qtnetwork-config.h:8 defines QT_LINKED_OPENSSL as true, while /usr/include/qt5/Gentoo/gentoo-qconfig.h:12 just defines QT_LINKED_OPENSSL without a value. Which, of course, clashes. This bug makes development using the Portage-installed version of QT impossible for projects that use pedantic compiler options (-Werror). There also a forum post about this bug: https://forums.gentoo.org/viewtopic-t-1099482-start-0.html It looks like this is due to qt5_install_module_config() in qt5-build.eclass It has the faulty assumption that the features get #defined without a value, but QtNetwork/qtnetwork-config.h breaks that assumption by #defining its flags with either true or 1 as the value So far I've been working around this by manually editing gentoo-qconfig.h, when this comes up, and changing QT_LINKED_OPENSSL to true I can confirm that this bug is still present. I encountered it while compiling monero-gui and could workaround it by removing the duplicate definition in /usr/include/qt5/Gentoo/gentoo-qconfig.h manually. After recent update to stabilized Qt-5.15.1 gentoo packages I get the subject error with the gitqlient (use -Werror option) from Guru repo while recently I successfully merged both mentioned ebuilds. I have no ( qtnetwork-config.h:6: error: "QT_LINKED_OPENSSL" redefined [-Werror] ) errors while compiling that with dev-qt/qtnetwork-5.14.2-r1 like with dev-qt/qtnetwork-5.15.1 The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/proj/qt.git/commit/?id=dcc79770bc78ebb3855a50a6397862828f9a93e3 commit dcc79770bc78ebb3855a50a6397862828f9a93e3 Author: Andreas Sturmlechner <asturm@gentoo.org> AuthorDate: 2020-11-17 23:38:39 +0000 Commit: Andreas Sturmlechner <asturm@gentoo.org> CommitDate: 2020-11-18 21:05:22 +0000 dev-qt/qtnetwork: Fix macro redefinition of QT_LINKED_OPENSSL warning Bug: https://bugs.gentoo.org/652650 Package-Manager: Portage-3.0.9, Repoman-3.0.2 Signed-off-by: Andreas Sturmlechner <asturm@gentoo.org> dev-qt/qtnetwork/qtnetwork-5.15.9999.ebuild | 9 +++++++++ 1 file changed, 9 insertions(+) So, should be fixed in 5.15.2. |
gentoo build of QtCore (/usr/include/qt5/Gentoo/gentoo-qconfig.h:10) defines QT_LINKED_OPENSSL in conflict with the upstream definition in QtNetwork (/usr/include/qt5/QtNetwork/qtnetwork-config.h:8) Build is from binary package dev-qt/qtdeclarative-5.9.4 with USE="jit widgets xml -debug (-gles2) -localstorage {-test}" System is x86_64 with gentoo 2.4.1 of Linux 4.9.76