From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: elogind: disable utmp for musl
Date: Sun, 06 Oct 2019 23:15:49 +0200 [thread overview]
Message-ID: <20191006211549.XhuWWorbdoOC6pf-YzE76vHV1_rRBOJVsKWhgQ56Cfg@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-15138@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 607 bytes --]
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.
prev parent reply other threads:[~2019-10-06 21:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-05 17:47 [PR PATCH] " voidlinux-github
2019-10-06 21:15 ` voidlinux-github [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20191006211549.XhuWWorbdoOC6pf-YzE76vHV1_rRBOJVsKWhgQ56Cfg@z \
--to=voidlinux-github@inbox.vuxu.org \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).