+ -Dlogind-provider=systemd \
Code: [Select]+ -Dlogind-provider=systemd \Are you saying it should have said elogind?
It honestly doesn't really matter anymore since elogind provides systemd now. Building with elogind or systemd activates exactly the same feature set (i.e. logind stuff).
I wouldn't be too sure about that. sway currently says stuff about being unable to find backend for me, and apparently I'm not the only onehttps://github.com/swaywm/sway/issues/4338This is a user of an alternative init system having the same error as mine, and the options are to either use logind or set suid. They have a wiki page on this, and in the logind section (which they recommend), they say you should build wlroots with elogind explicitly or else it will expect libsystemd.https://github.com/swaywm/sway/wiki/Running-Sway-without-systemdApparently for some things you can't just run it with systemd support and expect it to find your elogind. I have yet to try building it this way myself, but I'll report back with the results