https://bugs.kde.org/show_bug.cgi?id=410474
Bug ID: 410474
Summary: kde-apps/kdepim-runtime-19.04.3 with parallel build
gives fatal error: ui_lockfilepage.h: No such file or
directory
Product: kdepim
Version: unspecified
Platform: Gentoo Packages
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: kdepim-b...@kde.org
Reporter: pio...@netscape.net
Target Milestone: ---
SUMMARY
the gentoo package kde-apps/kdepim-runtime-19.04.3:5 aborts compilation because
of above error, had no such problem in previous versions. maybe a problem of
compilation-order?
STEPS TO REPRODUCE
1. MAKEOPTS="-j6 -l6" emerge =kde-apps/kdepim-runtime-19.04.3
OBSERVED RESULT
build.log contains nothing about ui_lockfilepage.h getting built and instead I
get at the end:
...
[370/746]... -c
[...]/work/kdepim-runtime-19.04.3/resources/mbox/mboxresource.cpp
FAILED: resources/mbox/CMakeFiles/akonadi_mbox_resource.dir/mboxresource.cpp.o
In file included from
[...]/work/kdepim-runtime-19.04.3/resources/mbox/mboxresource.cpp:37:
[...]/work/kdepim-runtime-19.04.3/resources/mbox/lockmethodpage.h:25:10: fatal
error: ui_lockfilepage.h: No such file or directory
#include "ui_lockfilepage.h"
^~~~~~~~~~~~~~~~~~~
compilation terminated.
[371/746]... -c resources/mixedmaildir/mixedmaildir_debug.cpp
[372/746]... -c resources/mixedmaildir/mixedmaildirresource_debug.cpp
[373/746]... -c resources/mixedmaildir/settings.cpp
[374/746]... -c
[...]/work/kdepim-runtime-19.04.3/resources/mixedmaildir/kmindexreader/kmindexreader.cpp
[375/746]... -c
resources/mbox/akonadi_mbox_resource_autogen/mocs_compilation.cpp
ninja: build stopped: subcommand failed.
EXPECTED RESULT
correct multithreaded compilation just like from
MAKEOPTS="-j1" emerge =kde-apps/kdepim-runtime-19.04.3
SOFTWARE/OS VERSIONS
Linux/KDE Plasma:
gentoo profile: default/linux/amd64/17.0/desktop/plasma/systemd (stable)
kde-frameworks/plasma-5.60.0 is already compiled and installed
ADDITIONAL INFORMATION
haven't reported it in gentoo.
seems in past bugs of that kind the solution was to forward-declare stuff
instead of including the header-file which might not yet have been built in
parallel-builds. doesn't ninja/cmake have any kind of dependency-tracking for
that? or don't they cooperate in their dependency-tracking? maybe someone
should file a bug in cmake and ninja?
--
You are receiving this mail because:
You are watching all bug changes.
