| View previous topic :: View next topic |
| Author |
Message |
dasPaul
Apprentice
Joined: 14 Feb 2012
Posts: 243
Location: Dresden
|
 Posted: Tue Jul 26, 2016 9:04 am Post subject: kscreenlocker-5.6.5 fails [Solved] |
 |
|
Hi,
again kscreenlocker-5.6.5 fails to emerge I think somewhere at linking:
| Code: |
...
[ 89%] ^[[32m^[[1mLinking CXX executable kscreenlocker_greet^[[0m
cd /var/tmp/portage/kde-plasma/kscreenlocker-5.6.5/work/kscreenlocker-5.6.5_build/greeter && /usr/bin/cmake -E cmake_link_script CMakeFiles/ks$
/usr/bin/x86_64-pc-linux-gnu-g++ -march=native -O2 -pipe -std=c++0x -fno-exceptions -Wall -Wextra -Wcast-align -Wchar-subscripts -Wformat-s$
/usr/lib64/libKF5WaylandClient.so.5.24.0: undefined reference to `wl_proxy_marshal_constructor_versioned'
collect2: error: ld returned 1 exit status
greeter/CMakeFiles/kscreenlocker_greet.dir/build.make:306: recipe for target 'greeter/kscreenlocker_greet' failed
make[2]: *** [greeter/kscreenlocker_greet] Error 1
make[2]: Leaving directory '/var/tmp/portage/kde-plasma/kscreenlocker-5.6.5/work/kscreenlocker-5.6.5_build'
CMakeFiles/Makefile2:344: recipe for target 'greeter/CMakeFiles/kscreenlocker_greet.dir/all' failed
make[1]: *** [greeter/CMakeFiles/kscreenlocker_greet.dir/all] Error 2
make[1]: *** Waiting for unfinished jobs....
[ 92%] ^[[32mBuilding CXX object CMakeFiles/KScreenLocker.dir/kscreensaversettings.cpp.o^[[0m
[ 92%] ^[[32mBuilding CXX object kcm/CMakeFiles/screenlocker_kcm.dir/screenlocker_kcm_automoc.cpp.o^[[0m
[ 92%] ^[[32mBuilding CXX object kcm/CMakeFiles/screenlocker_kcm.dir/screenlocker_kcm_automoc.cpp.o^[[0m
cd /var/tmp/portage/kde-plasma/kscreenlocker-5.6.5/work/kscreenlocker-5.6.5_build/kcm && /usr/bin/x86_64-pc-linux-gnu-g++ -DKCOREADDONS_LIB -$
/usr/bin/x86_64-pc-linux-gnu-g++ -DKCOREADDONS_LIB -DKScreenLocker_EXPORTS -DQT_CORE_LIB -DQT_DBUS_LIB -DQT_GUI_LIB -DQT_NO_DEBUG -DQT_WIDGET$
[ 93%] ^[[32mBuilding CXX object CMakeFiles/KScreenLocker.dir/powerdevilpolicyagent.cpp.o^[[0m
/usr/bin/x86_64-pc-linux-gnu-g++ -DKCOREADDONS_LIB -DKScreenLocker_EXPORTS -DQT_CORE_LIB -DQT_DBUS_LIB -DQT_GUI_LIB -DQT_NO_DEBUG -DQT_WIDGET$
[ 95%] ^[[32mBuilding C object CMakeFiles/KScreenLocker.dir/wayland-ksld-protocol.c.o^[[0m
/usr/bin/x86_64-pc-linux-gnu-gcc -DKCOREADDONS_LIB -DKScreenLocker_EXPORTS -DQT_CORE_LIB -DQT_DBUS_LIB -DQT_GUI_LIB -DQT_NO_DEBUG -DQT_WIDGET$
[ 96%] ^[[32mBuilding CXX object CMakeFiles/KScreenLocker.dir/KScreenLocker_automoc.cpp.o^[[0m
/usr/bin/x86_64-pc-linux-gnu-g++ -DKCOREADDONS_LIB -DKScreenLocker_EXPORTS -DQT_CORE_LIB -DQT_DBUS_LIB -DQT_GUI_LIB -DQT_NO_DEBUG -DQT_WIDGET$
[ 98%] ^[[32m^[[1mLinking CXX shared module screenlocker_kcm.so^[[0m
cd /var/tmp/portage/kde-plasma/kscreenlocker-5.6.5/work/kscreenlocker-5.6.5_build/kcm && /usr/bin/cmake -E cmake_link_script CMakeFiles/screen$
/usr/bin/x86_64-pc-linux-gnu-g++ -fPIC -march=native -O2 -pipe -std=c++0x -fno-exceptions -Wall -Wextra -Wcast-align -Wchar-subscripts -Wfor$
make[2]: Leaving directory '/var/tmp/portage/kde-plasma/kscreenlocker-5.6.5/work/kscreenlocker-5.6.5_build'
[ 98%] ^[[0mBuilt target screenlocker_kcm^[[0m
[100%] ^[[32m^[[1mLinking CXX shared library libKScreenLocker.so^[[0m
/usr/bin/cmake -E cmake_link_script CMakeFiles/KScreenLocker.dir/link.txt --verbose=1
/usr/bin/x86_64-pc-linux-gnu-g++ -fPIC -march=native -O2 -pipe -std=c++0x -fno-exceptions -Wall -Wextra -Wcast-align -Wchar-subscripts -Wfor$
/usr/bin/cmake -E cmake_symlink_library libKScreenLocker.so.5.6.5 libKScreenLocker.so.5 libKScreenLocker.so
make[2]: Leaving directory '/var/tmp/portage/kde-plasma/kscreenlocker-5.6.5/work/kscreenlocker-5.6.5_build'
[100%] ^[[0mBuilt target KScreenLocker^[[0m
make[1]: Leaving directory '/var/tmp/portage/kde-plasma/kscreenlocker-5.6.5/work/kscreenlocker-5.6.5_build'
Makefile:127: recipe for target 'all' failed
make: *** [all] Error 2
^[[31;01m*^[[0m ERROR: kde-plasma/kscreenlocker-5.6.5::gentoo failed (compile phase):
^[[31;01m*^[[0m emake failed
^[[31;01m*^[[0m
^[[31;01m*^[[0m If you need support, post the output of `emerge --info '=kde-plasma/kscreenlocker-5.6.5::gentoo'`,
^[[31;01m*^[[0m the complete build log and the output of `emerge -pqv '=kde-plasma/kscreenlocker-5.6.5::gentoo'`.
^[[31;01m*^[[0m The complete build log is located at '/var/tmp/portage/kde-plasma/kscreenlocker-5.6.5/temp/build.log'.
^[[31;01m*^[[0m The ebuild environment file is located at '/var/tmp/portage/kde-plasma/kscreenlocker-5.6.5/temp/environment'.
^[[31;01m*^[[0m Working directory: '/var/tmp/portage/kde-plasma/kscreenlocker-5.6.5/work/kscreenlocker-5.6.5_build'
^[[31;01m*^[[0m S: '/var/tmp/portage/kde-plasma/kscreenlocker-5.6.5/work/kscreenlocker-5.6.5'
|
| Code: | emerge --info
Portage 2.2.28 (python 2.7.10-final-0, default/linux/amd64/13.0, gcc-4.9.3, glibc-2.22-r4, 4.3.0-gentoo x86_64)
=================================================================
System uname: Linux-4.3.0-gentoo-x86_64-Intel-R-_Core-TM-_i5-4250U_CPU_@_1.30GHz-with-gentoo-2.2
KiB Mem: 8069684 total, 657480 free
KiB Swap: 0 total, 0 free
Timestamp of repository gentoo: Tue, 26 Jul 2016 06:00:01 +0000
sh bash 4.3_p42-r1
ld GNU ld (Gentoo 2.25.1 p1.1) 2.25.1
distcc 3.2rc1 x86_64-pc-linux-gnu [disabled]
app-shells/bash: 4.3_p42-r1::gentoo
dev-java/java-config: 2.2.0-r3::gentoo
dev-lang/perl: 5.20.2::gentoo
dev-lang/python: 2.7.10-r1::gentoo, 3.4.3-r1::gentoo
dev-util/cmake: 3.3.1-r1::gentoo
dev-util/pkgconfig: 0.28-r2::gentoo
sys-apps/baselayout: 2.2::gentoo
sys-apps/openrc: 0.19.1::gentoo
sys-apps/sandbox: 2.10-r1::gentoo
sys-devel/autoconf: 2.13::gentoo, 2.69::gentoo
sys-devel/automake: 1.11.6-r1::gentoo, 1.14.1::gentoo, 1.15::gentoo
sys-devel/binutils: 2.25.1-r1::gentoo
sys-devel/gcc: 4.9.3::gentoo
sys-devel/gcc-config: 1.7.3::gentoo
sys-devel/libtool: 2.4.6::gentoo
sys-devel/make: 4.1-r1::gentoo
sys-kernel/linux-headers: 4.3::gentoo (virtual/os-headers)
sys-libs/glibc: 2.22-r4::gentoo
Repositories:
gentoo
location: /mnt/c2/store/system/portage
sync-type: rsync
sync-uri: rsync://rsync.gentoo.org/gentoo-portage
priority: -1000
local-crossdev
location: /usr/local/portage-crossdev
masters: gentoo
priority: 9999
ACCEPT_KEYWORDS="amd64"
ACCEPT_LICENSE="* -@EULA"
CBUILD="x86_64-pc-linux-gnu"
CFLAGS="-march=native -O2 -pipe"
CHOST="x86_64-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/share/config /usr/share/gnupg/qualified.txt"
CONFIG_PROTECT_MASK="/etc/ca-certificates.conf /etc/dconf /etc/env.d /etc/fonts/fonts.conf /etc/gconf /etc/gentoo-release /etc/revdep-rebuild /etc/sandbox.d /etc/terminfo /etc/texmf/language.dat.d /etc/texmf/language.def.d /etc/texmf/updmap.d /etc/texmf/web2c"
CXXFLAGS="-march=native -O2 -pipe"
DISTDIR="/usr/portage/distfiles"
FCFLAGS="-O2 -pipe"
FEATURES="assume-digests binpkg-logs config-protect-if-modified distlocks ebuild-locks fixlafiles merge-sync news parallel-fetch preserve-libs protect-owned sandbox sfperms strict unknown-features-warn unmerge-logs unmerge-orphans userfetch userpriv usersandbox usersync xattr"
FFLAGS="-O2 -pipe"
GENTOO_MIRRORS="http://distfiles.gentoo.org"
LANG="de_DE.utf8"
LDFLAGS="-Wl,-O1 -Wl,--as-needed"
MAKEOPTS="-j5"
PKGDIR="/usr/portage/packages" |
any ideas?
[Moderator edit: changed quote tags to code tags since the content should be shown verbatim. -Hu]
Last edited by dasPaul on Wed Jul 27, 2016 8:22 am; edited 1 time in total |
|
| Back to top |
|
 |
Hu
Moderator
Joined: 06 Mar 2007
Posts: 21633
|
| Posted: Wed Jul 27, 2016 1:44 am Post subject: |
|
|
You are correct. It is a linking problem. Your installation of libKF5WaylandClient.so.5.24.0 is incompletely linked. It requires symbols from a supporting DSO, but assumes that the process which links to libKF5WaylandClient.so.5.24.0 will also link to that supporting DSO. The greeter does not link to the supporting DSO, so the symbol is not found. The maintainers of libKF5WaylandClient.so.5.24.0 might have intended it to work that way, but in my opinion, it is a bug in libKF5WaylandClient.so.5.24.0 since the current setup imposes an extra burden on any program which wants to link to it.
Your log looks odd. How did you capture it for posting? |
|
| Back to top |
|
|
dasPaul
Apprentice
Joined: 14 Feb 2012
Posts: 243
Location: Dresden
|
| Posted: Wed Jul 27, 2016 6:44 am Post subject: |
|
|
I just copied it from linebreak disabled nano terminal. Here is the complete log:
http://pastebin.com/raw/yKvXcK96 |
|
| Back to top |
|
|
dasPaul
Apprentice
Joined: 14 Feb 2012
Posts: 243
Location: Dresden
|
| Posted: Wed Jul 27, 2016 7:26 am Post subject: |
|
|
| So if I create a bug report it should go to kwayland and not kscreenlocker? |
|
| Back to top |
|
|
dasPaul
Apprentice
Joined: 14 Feb 2012
Posts: 243
Location: Dresden
|
| Posted: Wed Jul 27, 2016 8:20 am Post subject: |
|
|
Strange, I re-emerged kwayland-5.24.0 and kscreenlocker emerged without problems...
Solved |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Portage & Programming
