From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-3.3 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, MAILING_LIST_MULTI,NICE_REPLY_A,RCVD_IN_DNSWL_MED,RCVD_IN_MSPIKE_H3, RCVD_IN_MSPIKE_WL autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 8325 invoked from network); 20 Aug 2021 21:44:48 -0000 Received: from mother.openwall.net (195.42.179.200) by inbox.vuxu.org with ESMTPUTF8; 20 Aug 2021 21:44:48 -0000 Received: (qmail 3291 invoked by uid 550); 20 Aug 2021 21:44:45 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-ID: Reply-To: musl@lists.openwall.com Received: (qmail 3273 invoked from network); 20 Aug 2021 21:44:44 -0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=decentral.ch; s=rsa1; h=Content-Transfer-Encoding:Content-Type:In-Reply-To:From:References:To:Subject:MIME-Version:Date:Message-ID; bh=jQI17C9lLfJpDNoYyUNY8qCeUQDNs6+9ltucRcH+4pU=; b=Iuft26NKJyVJRb4La1MjuqjNQxUjeULDDvzVZp9sze2tNBJMRjkm8WlmKEof4Jk8F/fyca6hYP7wFHj+mQqrnQHFVeSqBW/ojkuSXVMfzQz/qVxcj6HIR5uFkaWgsjtz; Message-ID: <509ff9aa-5d76-397e-20db-ed2b10dfad5c@decentral.ch> Date: Fri, 20 Aug 2021 23:44:32 +0200 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.0.1 Content-Language: en-US To: musl@lists.openwall.com References: From: Tim Tassonis In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Subject: Re: [musl] Is systemd in scope for musl? On 8/20/21 20:55, Olivier Galibert wrote: >   Hi, > > I'm trying to build a kinda-distribution of linux on arm64 where all the > userspace is done with clang and which uses systemd[1].  I can either > use glibc or musl.  Glibc aggressively does not want to be compiled by > anything else than gcc.  Musl is missing a bunch of stuff systemd wants. > > I have two possibilities, either make glibc work but not contribute the > changes (because I don't want to give my copyright to the fsf[2]) or > extend musl until it has all the missing APIs and contribute them.  I'd > rather do the latter. > > Some APIs (qsort_r) are clearly going to be added in the future.  Others > are very glibc, e.g. printf configurability stuff, and do not come from > any standard.  So, is "this API is used by systemd" a good enough reason > to accept it as in-scope for musl[3] or will there be things that are > "never" going to be accepted? Without wanting to bitch about SystemD, their maintainer has repeatedly proven to not give one fuck about any standards or portability, he actually deliberately enforced non-portability to other libraries than glibc and kernels than Linux. So, I doubt very much this is the way to go. Chasing a deliberately moving target is no fun. Bye Tim