There's a merged pull request on the void-packages repository

elogind: disable utmp for musl
https://github.com/void-linux/void-packages/pull/15138

Description:
Since musl only stubs out utmp, elogind emits this warning on startup:

    "elogind[1044]: Failed to set utmp path to /dev/null/utmp: Not supported"

This patch silences that warning by building elogind on musl without utmp log handling support.

I'm not sure if this is the best method of checking for musl and updating the configure line. This is my second void contribution. I grepped for other uses of `XBPS_TARGET_LIBC` as a guide.