Bug 425470 - kxmlgui build failure on master [kde neon]
Summary: kxmlgui build failure on master [kde neon]
Status: RESOLVED NOT A BUG
Alias: None
Product: frameworks-kxmlgui
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: unspecified
Platform: Neon Linux
: NOR normal
Target Milestone: ---
Assignee: kdelibs bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-08-17 18:57 UTC by amit
Modified: 2020-09-08 14:38 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description amit 2020-08-17 18:57:07 UTC
SUMMARY

Building from kio (and therefore kxmlgui) from master on 17-8-2020. I get a compile error when build system hits ksendbugmail/smtp[.h/.cpp]. Line 13 of .h #includes <TcpSocket> and line 163 of .cpp tries to initialise sock member with "new QSslSocket(this)".

STEPS TO REPRODUCE
1. kdesrc-build kxmlgui

OBSERVED RESULT

kxmlgui fails to build.

EXPECTED RESULT

Successful build.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: KDE Neon 5.19 ubuntu codename focal version id 20.04
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: master as at 17-8-2020 
Qt Version: 5.14

ADDITIONAL INFORMATION

Openssl version 1.1.1f
Comment 1 amit 2020-08-19 13:08:43 UTC
I now believe this is caused by the Qt5.14 package used having been configured without an openssl option. Conditional compilation detects the lack of openssl but sadly leads to the mismatch reported. It would be probably preferable to have a successful build - assuming that it's not more complicated than lining up the socket types in .h/.cpp.
Comment 2 Christoph Feck 2020-09-03 11:47:18 UTC
Are you sure Qt on neon is configured without OpenSSL?
Comment 3 amit 2020-09-03 13:26:36 UTC
Hi Christoph, sorry, that is not what I am saying. The problem arose
when I built Qt5 from source *myself* without linking to OpenSSL.  So
it's not a "this is broken on Neon" it's "if someone happens to (be
silly enough?) to build Qt without linking in OpenSSL, then the
problem will occur". Didn't take me long to work out the problem but a
younger me might well have struggled and given up.

A

On Thu, 3 Sep 2020 at 12:47, Christoph Feck <bugzilla_noreply@kde.org> wrote:
>
> https://bugs.kde.org/show_bug.cgi?id=425470
>
> --- Comment #2 from Christoph Feck <cfeck@kde.org> ---
> Are you sure Qt on neon is configured without OpenSSL?
>
> --
> You are receiving this mail because:
> You reported the bug.
Comment 4 Christoph Feck 2020-09-08 10:32:12 UTC
Thanks for the update; changing status.

KDE Frameworks require a correctly configured Qt; compilations with a reduced feature set are not supported, and given the vast amount of possibilities to reduce the feature set make it unfeasible to detect and report them.
Comment 5 amit 2020-09-08 14:38:17 UTC
Ok - thanks for letting me know...
A

On Tue, 8 Sep 2020 at 11:32, Christoph Feck <bugzilla_noreply@kde.org> wrote:
>
> https://bugs.kde.org/show_bug.cgi?id=425470
>
> Christoph Feck <cfeck@kde.org> changed:
>
>            What    |Removed                     |Added
> ----------------------------------------------------------------------------
>          Resolution|---                         |NOT A BUG
>              Status|REPORTED                    |RESOLVED
>
> --- Comment #4 from Christoph Feck <cfeck@kde.org> ---
> Thanks for the update; changing status.
>
> KDE Frameworks require a correctly configured Qt; compilations with a reduced
> feature set are not supported, and given the vast amount of possibilities to
> reduce the feature set make it unfeasible to detect and report them.
>
> --
> You are receiving this mail because:
> You reported the bug.