mailing list of musl libc
 help / color / mirror / code / Atom feed
From: "A. Wilcox" <awilfox@adelielinux.org>
To: musl@lists.openwall.com
Subject: Re: Missing definitions for UTMP(x)
Date: Mon, 28 Aug 2017 21:09:00 -0500	[thread overview]
Message-ID: <59A4CCBC.3010300@adelielinux.org> (raw)
In-Reply-To: <20170828185658.74f2552f@prometeo.example.org>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 28/08/17 16:57, Matias Fonzo wrote:
> sessreg.h:110:21: error: '_PATH_UTMPX' undeclared (first use in
> this function) # define UTMPX_FILE _PATH_UTMPX ^ sessreg.c:308:16:
> note: in expansion of macro 'UTMPX_FILE' utmpx_file = UTMPX_FILE; 
> ^~~~~~~~~~


> # define UTMPX_FILE     _PATH_UTMPX


> Please, include it.


If you'll notice, this would cause preprocessor recursion.

The musl libc does not actually support utmpx or wtmpx.  For better
support you need to add another library such as libutx:

https://code.foxkit.us/adelie/libutx

This library is not yet fully functional, as it does not yet provide
wtmp(x).  It does however fully implement utmp(x).  It may give clues
as to what you'll need to do to make this functional on musl libc.

What we do in Adélie is actually put these two files in the musl
codebase itself as a patch, so that all programs can have it
available.  An eventual goal is to make it a separate library, and
have programs that can use utmpx features attempt to dlopen the
library.  If the library exists on the system, they use it; if the
library does not exist on the system, the user has chosen to disable
it and that part of the software is disabled.

Unfortunately that is going to require a massive effort and the
cooperation of many disparate upstreams.  I don't hold my breath for
such a time.  Until then, having it always available with a simple
solution for those who do not want it (symlink /var/run/utmp ->
/dev/null) is what we are using.


Best,
- --arw


- -- 
A. Wilcox (awilfox)
Project Lead, Adélie Linux
http://adelielinux.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAEBCAAGBQJZpMy5AAoJEMspy1GSK50U3AYQAJWNqpkl2eWCLnxpU+p2cAmv
9yzWQe2sPjCo+1hISq4u8Xt1c0KMbBGaKLhgA9yh1wtQT21QdWm+Xk3wIaETZd3v
EnMH3ZzxbbYXYImYmyytUUicDbCJVHWvBe4kG9wQtgoTqijw7WIkDR6MuyKwTC7Q
Ax2U+QXQ25bnjGekW6OWVoCDDDrfYM1NZvz8DUh74ovxL3ceqKnUOmoNxJRWZS0w
a3z80c5LiB9/ilOuzQc/ijeDFjm/ST2A99vKutzTdEM05kcsrzsNEVLC47SFZfOg
+s0SCXVpEsXvXSkS1ECXANSt6b1HACO1VPZ+aBsyKApi8D/UnO2uzIwV1fQox6XE
4Gt9XPV7mP8WL9ycsNW7WXRhledHvtncGHaIqCiG6md/kSdPQEgP/KzeXJeAv+FH
bmRJTSbhDB0o2SeUxrCVLHLaPGWTYtshNg6/C/l2dyZqwctgmTmmUeVkXFnADiGW
ytwhzLfaUjE3eh8nqHd8BHXZtRweiaxtTZaOo7HmJF8TH1s1a3s9o4sfTHF8js+U
GKaXaIrBNDBD2/XMvt5w0/WDZjw/INyNPcXwV2aXCBuofPtQpFi1cvDjPHfZVWZx
irLrGTBVffgBuTNb19ZLWN+RC5JmAFuSGaTvpNWnMF0kaZD/pQ3ubYFHKJOMyBHY
sZd8C2Hq1ePbcs/qd9KH
=T+QY
-----END PGP SIGNATURE-----


  reply	other threads:[~2017-08-29  2:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-28 21:57 Matias Fonzo
2017-08-29  2:09 ` A. Wilcox [this message]
2017-08-29 18:53   ` Matias Fonzo
2017-08-29 11:05 ` u-uy74
2017-08-29 18:51   ` Matias Fonzo

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=59A4CCBC.3010300@adelielinux.org \
    --to=awilfox@adelielinux.org \
    --cc=musl@lists.openwall.com \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/musl/

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).