| Darth Vader |
09-23-2018 10:55 PM |
Quote:
Originally Posted by chrisVV
(Post 5907092)
Ah, the good news is that the latest recompilation of skype (version 8.31.76.88) fixes the problem with glibc-2.28. So you need to get elogind working. What compilation error are you getting?
|
This one: https://github.com/elogind/elogind/issues/74
Code:
ninja -C build
ninja: Entering directory `build'
[1/323] Compiling C object 'src/libelogind/src@libelogind@@elogind@sta/sd-bus_bus-error.c.o'.
FAILED: src/libelogind/src@libelogind@@elogind@sta/sd-bus_bus-error.c.o
ccache cc -Isrc/libelogind/src@libelogind@@elogind@sta -Isrc/libelogind -I../src/libelogind -Isrc/basic -I../src/basic -Isrc/shared -I../src/shared -Isrc/systemd -I../src/systemd -Isrc/login -I../src/login -Isrc/core -I../src/core -I../src/libelogind/sd-bus -I../src/libelogind/sd-id128 -Isrc/sleep -I../src/sleep -Isrc/update-utmp -I../src/update-utmp -I. -I../ -fdiagnostics-color=always -pipe -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -std=gnu99 -O0 -g -Wextra -Werror=undef -Wlogical-op -Wmissing-include-dirs -Wold-style-definition -Wpointer-arith -Winit-self -Wdeclaration-after-statement -Wfloat-equal -Wsuggest-attribute=noreturn -Werror=missing-prototypes -Werror=implicit-function-declaration -Werror=missing-declarations -Werror=return-type -Werror=incompatible-pointer-types -Werror=format=2 -Wstrict-prototypes -Wredundant-decls -Wmissing-noreturn -Wimplicit-fallthrough=5 -Wshadow -Wendif-labels -Wstrict-aliasing=2 -Wwrite-strings -Werror=overflow -Wdate-time -Wnested-externs -ffast-math -fno-common -fdiagnostics-show-option -fno-strict-aliasing -fvisibility=hidden -fstack-protector -fstack-protector-strong --param=ssp-buffer-size=4 -fPIE -Wno-unused-parameter -Wno-missing-field-initializers -Wno-unused-result -Wno-format-signedness -Wno-error=nonnull -Werror=shadow -include config.h -fPIC -pthread -fvisibility=default -MD -MQ 'src/libelogind/src@libelogind@@elogind@sta/sd-bus_bus-error.c.o' -MF 'src/libelogind/src@libelogind@@elogind@sta/sd-bus_bus-error.c.o.d' -o 'src/libelogind/src@libelogind@@elogind@sta/sd-bus_bus-error.c.o' -c ../src/libelogind/sd-bus/bus-error.c
In file included from ../src/basic/util.h:47,
from ../src/libelogind/sd-bus/bus-error.c:34:
../src/basic/missing.h:1387:8: error: redefinition of ‘struct statx_timestamp’
struct statx_timestamp {
^~~~~~~~~~~~~~~
In file included from /usr/include/sys/stat.h:446,
from ../src/basic/util.h:38,
from ../src/libelogind/sd-bus/bus-error.c:34:
/usr/include/bits/statx.h:25:8: note: originally defined here
struct statx_timestamp
^~~~~~~~~~~~~~~
In file included from ../src/basic/util.h:47,
from ../src/libelogind/sd-bus/bus-error.c:34:
../src/basic/missing.h:1392:8: error: redefinition of ‘struct statx’
struct statx {
^~~~~
In file included from /usr/include/sys/stat.h:446,
from ../src/basic/util.h:38,
from ../src/libelogind/sd-bus/bus-error.c:34:
/usr/include/bits/statx.h:36:8: note: originally defined here
struct statx
^~~~~
[2/323] Compiling C object 'src/libelogind/src@libelogind@@elogind@sta/sd-bus_bus-container.c.o'.
FAILED: src/libelogind/src@libelogind@@elogind@sta/sd-bus_bus-container.c.o
Quote:
Originally Posted by chrisVV
(Post 5907092)
The only problem I have experienced with elogind is that running it can stop xfce's shutdown/reboot options working correctly, possibly because it interferes with ConsoleKit, so it is best to start it in the skypeforlinux script and stop it when skype is closed.
|
I believe that the issue of ELOGIND is bigger than this and our Dutch Overlord stopped his experiments with elogind for Plasma5 for a very reason:
The systemd-logind (hence the elogind) is a evolution of ConsoleKit which we use today even in -current, and offer a similar functionality as basis.
Then you cannot use them simultaneous, because they will step on each other shoes.
The real issue with Slackware looks like is that we are stuck from whatever reasons on this "old" ConsoleKit which apparently is about of being abandoned.
Please look there: https://github.com/ConsoleKit2/ConsoleKit2
The last activity is from 11 months ago.
I believe they they moved to systemd-logind with all family, including the dog and chickens.
-------------------------------------
However, I wonder if that elogind is the proper solution and replacement of systemd-logind while looking there: https://github.com/elogind/elogind/issues/70
Yes, people! There are many other software which uses its functionalities. And which shall be adapted eventually to elogind. |
