From: Tim Tassonis <stuff@decentral.ch>
To: musl@lists.openwall.com
Subject: Re: [musl] Is systemd in scope for musl?
Date: Fri, 20 Aug 2021 23:44:32 +0200 [thread overview]
Message-ID: <509ff9aa-5d76-397e-20db-ed2b10dfad5c@decentral.ch> (raw)
In-Reply-To: <CAMFK0gsKYoNkoX_M1V4uMWhfTtSWqB4V90YBHMHmZVem-ZujpQ@mail.gmail.com>
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
next prev parent reply other threads:[~2021-08-20 21:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-20 18:55 Olivier Galibert
2021-08-20 19:48 ` Max Rees
2021-08-20 20:29 ` Rich Felker
2021-08-20 21:44 ` Tim Tassonis [this message]
2021-08-20 22:02 ` Ariadne Conill
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=509ff9aa-5d76-397e-20db-ed2b10dfad5c@decentral.ch \
--to=stuff@decentral.ch \
--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).