Summary: | dev-libs/weston - weston-launch fails: failed to load module: /usr/lib64/weston/drm-backend.so: undefined symbol: launcher_logind_iface | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Philipp Middendorf <pmidden+gentoo> |
Component: | Current packages | Assignee: | Gentoo X packagers <x11> |
Status: | RESOLVED FIXED | ||
Severity: | normal | ||
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | weston-1.10-launcher_logind_iface.patch |
Description
Philipp Middendorf
2016-03-23 08:52:43 UTC
Might be an --as-needed problem. Possibly fallout from https://lists.freedesktop.org/archives/wayland-devel/2015-March/020701.html Can you try building weston with --no-as-needed ? I copied the ebuild and added "append-ldflags "--no-as-needed"" and later even "append-flags "--no-as-needed"" before the econf line but to no avail. create a file /etc/portage/env/no-as-needed containing LDFLAGS="-Wl,-O1 -Wl,--no-as-needed" and then add the line dev-libs/weston no-as-needed to /etc/portage/package.env https://wiki.gentoo.org/wiki/Knowledge_Base:Overriding_environment_variables_per_package Okay, thank you. I did that and I could see the linker command line being used while linking. However, the problem persists. Can you set EXTRA_ECONF="--enable-systemd-login" and try again? I don't fully understand how drm-backend.so gets to require the launcher_logind_iface symbol, but it seems that symbol will only exist if that option is passed to configure. Created attachment 429930 [details, diff]
weston-1.10-launcher_logind_iface.patch
or try this patch
I've tried both, in all combinations, still the same issue (I see the patch being applied before configure and I also see the system-login configure flag being used, so that works in principle). Then I don't know. Best report a bug upstream at https://bugs.freedesktop.org/ so they can have a look. removing blocker to Xorg stabilization in bug 579266 Can you try again with weston-1.11.0? I can on monday. Stay tuned. Seems to be fixed. |