I have been trying to build the latest version of xrdp and have run into a problem. Previous versions have included a instfiles/xrdp.sh file that is processed by the SlackBuild to become /etc/rc.d/rc.xrdp. I did ask at https://gitter.im/neutrinolabs/xrdp, but got a terse response that the file has been removed in the latest version. Simply adding the missing file to the latest version tarball still causes the SlackBuild to fail, which suggests that support has also been removed from the build system. Perhaps this is an example of projects dropping support for non-systemd distros?

The easiest fix is probably to add a big here string to the SlackBuild to generate the required /etc/rc.d/rc.xrdp, but that seems rather ugly. Any other ideas?

What stops you to just store this (now) custom "rc.xrdp" script in the SlackBuild directory?

2 members found this post helpful.

I thought the same thing when I was trying to get libratbag built, which is required by piper (GTK tool for configuring Logitech gaming mice). Luckily the devs added support for elogind late in 2018 so I could disable the systemd check in the meson invocation.


I don't use xrdp but I built 0.9.4 using the SlackBuild from SBo, grabbed the rc.xrdp from that, edited the build script with a few "if" statements and then built 0.9.12 with that. I compared the package contents and file sizes of 0.9.4 and 0.9.12 and everything seems fine. Also, none of the binaries or libraries seem "contaminated" by libelogind. The output from running the configure command with and without "--with-systemdsystemunitdir=no" doesn't seem to change functionally.

1 members found this post helpful.

@ZhaoLin1457 - Thanks for the suggestion. That is what I have done.
@fskmh - Thanks for the testing effort. Rather than using "if" statements, I have simply edited the script to suit the 0.9.12 version.

I added ' --enable-fuse ' as a configure option when I built the 0.9.10 version to allow for drive direction and it has not caused me any problems, unlike with version 0.9.4, so I have also enabled that in my 0.9.12 build. The build seems to be working on my 32-bit and 64-bit home machines running -current. I now want to test on a work server running Slackware64-14.2 that is still running version 0.9.4.