| Summary: | dev-qt/qtnetwork-5.15.9-r1: fails to compile with net-libs/libproxy-0.5.0 (ERROR: Feature 'libproxy' was enabled, but the pre-condition 'libs.libproxy' failed.) | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Miroslav Šulc <fordfrog> |
| Component: | Current packages | Assignee: | Qt Bug Alias <qt> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | b.buschinski, eschwartz, freedesktop-bugs, mgorny, pageexec, toralf |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| See Also: |
https://bugs.gentoo.org/show_bug.cgi?id=906755 https://github.com/libproxy/libproxy/issues/226 https://invent.kde.org/qt/qt/qtbase/-/merge_requests/255 |
||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Bug Depends on: | |||
| Bug Blocks: | 907047 | ||
| Attachments: | build.log | ||
|
Description
Miroslav Šulc
2023-05-21 05:57:01 UTC
Does <net-libs/libproxy-0.5.0 work? (In reply to Sam James from comment #1) > Does <net-libs/libproxy-0.5.0 work? yes, it compiles fine with net-libs/libproxy-0.4.18 The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=17eefd7b6289ed7e523dd4d598534e474cf99f98 commit 17eefd7b6289ed7e523dd4d598534e474cf99f98 Author: Sam James <sam@gentoo.org> AuthorDate: 2023-05-24 12:45:26 +0000 Commit: Sam James <sam@gentoo.org> CommitDate: 2023-05-24 12:46:37 +0000 net-libs/libproxy: add 0.5.1 Closes: https://bugs.gentoo.org/906755 Closes: https://bugs.gentoo.org/906879 Closes: https://bugs.gentoo.org/906957 Signed-off-by: Sam James <sam@gentoo.org> net-libs/libproxy/Manifest | 1 + net-libs/libproxy/libproxy-0.5.1.ebuild | 71 +++++++++++++++++++++++++++++++++ profiles/package.mask | 5 +++ 3 files changed, 77 insertions(+) Reopening as fordfrog reports there's still an issue. I think it's a bit different now, but here: ``` Checking for libproxy... Trying source 0 (type inline) of library libproxy ... proxy.h not found in [] and global paths. => source produced no result. test config.qtbase_network.libraries.libproxy FAILED ``` Upstream have moved proxy.h to a private subdir: https://github.com/libproxy/libproxy/issues/226#issuecomment-1557064225. The basic moral of this story seems to be that Qt wasn't using the pkg-config file so they just hoped and prayed that proxy.h was in the compiler default search path. The reporter for the upstream bug decided to symlink it to the compiler default search path as a local hack for NetBSD pkgsrc, which is... definitely something. I don't think libproxy itself currently intends to solve the problem of "consumers didn't use pkg-config and assumed the header location". The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=07a156795982a897c4a30aa154e22038970af90f commit 07a156795982a897c4a30aa154e22038970af90f Author: Andreas Sturmlechner <asturm@gentoo.org> AuthorDate: 2023-05-24 18:33:52 +0000 Commit: Andreas Sturmlechner <asturm@gentoo.org> CommitDate: 2023-05-24 18:33:52 +0000 dev-qt/qtnetwork: Fix build with >=net-libs/libproxy-0.5.1 Bug: https://bugs.gentoo.org/907047 Closes: https://bugs.gentoo.org/906879 Signed-off-by: Andreas Sturmlechner <asturm@gentoo.org> .../qtnetwork-5.15.9-libproxy-0.5-pkgconfig.patch | 32 ++++++++++++++++++++++ 1 file changed, 32 insertions(+) Do I see it correctly that the latest "fix" just added a patch, but it is not used in any of the ebuilds? yes, it still isn't fixed. The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=c387a831cee977c7db88556b7a11360d1fb5f27f commit c387a831cee977c7db88556b7a11360d1fb5f27f Author: Miroslav Šulc <fordfrog@gentoo.org> AuthorDate: 2023-05-25 07:25:01 +0000 Commit: Miroslav Šulc <fordfrog@gentoo.org> CommitDate: 2023-05-25 07:25:01 +0000 dev-qt/qtnetwork: added libproxy patch to 5.15.9-r2 Closes: https://bugs.gentoo.org/906879 Signed-off-by: Miroslav Šulc <fordfrog@gentoo.org> dev-qt/qtnetwork/qtnetwork-5.15.9-r2.ebuild | 1 + 1 file changed, 1 insertion(+) Thanks for fixing my apparent git mishap there. *** Bug 906703 has been marked as a duplicate of this bug. *** |
