From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/9218 Path: news.gmane.org!not-for-mail From: Rich Felker Newsgroups: gmane.linux.lib.musl.general Subject: Re: Missing defines in utmpx.h Date: Wed, 27 Jan 2016 19:04:48 -0500 Message-ID: <20160128000448.GO238@brightrain.aerifal.cx> References: <56A8857E.1030003@decentral.ch> Reply-To: musl@lists.openwall.com NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1453939506 3770 80.91.229.3 (28 Jan 2016 00:05:06 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 28 Jan 2016 00:05:06 +0000 (UTC) To: musl@lists.openwall.com Original-X-From: musl-return-9233-gllmg-musl=m.gmane.org@lists.openwall.com Thu Jan 28 01:05:06 2016 Return-path: Envelope-to: gllmg-musl@m.gmane.org Original-Received: from mother.openwall.net ([195.42.179.200]) by plane.gmane.org with smtp (Exim 4.69) (envelope-from ) id 1aOa5A-0000NI-FY for gllmg-musl@m.gmane.org; Thu, 28 Jan 2016 01:05:04 +0100 Original-Received: (qmail 22272 invoked by uid 550); 28 Jan 2016 00:05:01 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-ID: Original-Received: (qmail 22254 invoked from network); 28 Jan 2016 00:05:01 -0000 Content-Disposition: inline In-Reply-To: <56A8857E.1030003@decentral.ch> User-Agent: Mutt/1.5.21 (2010-09-15) Original-Sender: Rich Felker Xref: news.gmane.org gmane.linux.lib.musl.general:9218 Archived-At: On Wed, Jan 27, 2016 at 09:53:18AM +0100, Tim Tassonis wrote: > Hi all > > > I just tried to compile the latest busybox with musl and failed > because of a change in busybox to include utmpx.h in case of UTMP > support and header presence. > > The problem seems to be that busybox assumes some defines in utmpx.h > that are usually in utmp.h and glibc (and possibly other libc's) set > them in utmpx.h, but musl doesn't. > > I think it were > > _PATH_UTMP and _PATH_WTMP > > > I worked around the issue by disabling UTMP support, but maybe this > could be fixed in musl? I don't think it would hurt to change this (I'll check later) but generally you should disable utmp support on musl-based systems anyway. musl's utmp is intentionally stubbed out to do nothing, and some programs print spurious runtime warnings/errors too if it's enabled. Rich