From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/14346 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Florian Weimer Newsgroups: gmane.linux.lib.musl.general Subject: Re: Detecting musl at compile and/or configure time Date: Tue, 02 Jul 2019 14:19:13 +0200 Message-ID: <874l444oji.fsf@oldenburg2.str.redhat.com> References: <26f5537f-a876-209c-a27c-cd2619f5c834@gmch.uk> <3767f116-4a52-e9ef-a2ee-df1c23719e34@gmch.uk> Reply-To: musl@lists.openwall.com Mime-Version: 1.0 Content-Type: text/plain Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="135861"; mail-complaints-to="usenet@blaine.gmane.org" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.2 (gnu/linux) Cc: musl@lists.openwall.com, Chris Hall To: Samuel Holland Original-X-From: musl-return-14362-gllmg-musl=m.gmane.org@lists.openwall.com Tue Jul 02 14:19:43 2019 Return-path: Envelope-to: gllmg-musl@m.gmane.org Original-Received: from mother.openwall.net ([195.42.179.200]) by blaine.gmane.org with smtp (Exim 4.89) (envelope-from ) id 1hiHl8-000ZBN-0B for gllmg-musl@m.gmane.org; Tue, 02 Jul 2019 14:19:42 +0200 Original-Received: (qmail 27921 invoked by uid 550); 2 Jul 2019 12:19:39 -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 27899 invoked from network); 2 Jul 2019 12:19:38 -0000 In-Reply-To: (Samuel Holland's message of "Sun, 30 Jun 2019 07:28:48 -0500") X-Scanned-By: MIMEDefang 2.79 on 10.5.11.16 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.26]); Tue, 02 Jul 2019 12:19:26 +0000 (UTC) Xref: news.gmane.org gmane.linux.lib.musl.general:14346 Archived-At: * Samuel Holland: > The Linux UAPI is stable, so you can use whatever features you want as long as > you gracefully handle ENOSYS/EINVAL (or document a minimum supported version). Note that this only applies to the numbered syscall interface. For example, it is not true for vsyscall (which is now considered optional, despite part of the userspace ABI at first, and really hard to detect properly). Netlink packet layout also keeps changing for some subsystems. Thanks, Florian