Bug 442708

Summary:	build error libkscreen since commit d24df22 "add rgb range setting"
Product:	[Plasma] KScreen	Reporter:	desaparecido <luis.davila.pc>
Component:	libkscreen	Assignee:	kscreen-bugs-null <kscreen-bugs-null>
Status:	RESOLVED WORKSFORME
Severity:	normal	CC:	nicolas.fella
Priority:	NOR
Version First Reported In:	git-master
Target Milestone:	---
Platform:	Arch Linux
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description desaparecido 2021-09-19 20:53:16 UTC

SUMMARY


STEPS TO REPRODUCE
1. build a commit before and builds is ok
2. build commit d24df22 and error
3. trying since some days building each time all KF5 and plasma dependencies from git, same result.

OBSERVED RESULT
error in console:

/usr/bin/ld: CMakeFiles/KF5Screen.dir/output.cpp.o: in function `KScreen::Output::setRgbRange(KScreen::Output::RgbRange)':
/tmp/makepkg/libkscreen-git/src/libkscreen/src/output.cpp:650: undefined reference to `KScreen::Output::rgbRangeChanged(KScreen::Output::RgbRange)'
collect2: error: ld returned 1 exit status
make[2]: *** [src/CMakeFiles/KF5Screen.dir/build.make:365: bin/libKF5Screen.so.5.22.90] Error 1
make[1]: *** [CMakeFiles/Makefile2:587: src/CMakeFiles/KF5Screen.dir/all] Error 2
make: *** [Makefile:136: all] Error 2
==> ERROR: A failure occurred in build().


EXPECTED RESULT
builds fine

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 5.23.80
KDE Frameworks Version: 5.87.0
Qt Version: 5.15.2

ADDITIONAL INFORMATION
using Archlinux with testing repo enable
KF5 and Plasma builded from git

Comment 1 Nicolas Fella 2021-09-20 15:07:29 UTC

Are you building plasma-wayland-protocols for git?

Comment 2 desaparecido 2021-09-20 19:46:16 UTC

yes, I'm building from git too, I have the v1.4.0.r2.g07e6f76-1 version.  I don't know if I can give more information about it. I use git version since some years building all kf5 and Plasma stuffs, i know that some times there are errors but this time i have this error since that commit and this time I'd take care to report it, If there are some clues to discover the problem, advices are welcome :-)

Comment 3 Bug Janitor Service 2021-10-05 04:36:08 UTC

Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!

Comment 4 Bug Janitor Service 2021-10-20 04:35:37 UTC

This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!