mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Olivier Galibert <galibert@pobox.com>
To: musl@lists.openwall.com
Subject: [musl] Is systemd in scope for musl?
Date: Fri, 20 Aug 2021 20:55:43 +0200	[thread overview]
Message-ID: <CAMFK0gsKYoNkoX_M1V4uMWhfTtSWqB4V90YBHMHmZVem-ZujpQ@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1079 bytes --]

  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?

Best regards,

  OG.

[1] This list is not the place to bitch about systemd or my hobby choices
[2] This list is not the place to bitch about the FSF copyright policies
either
[3] Patches have to be good by themselves, of course

[-- Attachment #2: Type: text/html, Size: 1328 bytes --]

             reply	other threads:[~2021-08-20 18:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-20 18:55 Olivier Galibert [this message]
2021-08-20 19:48 ` Max Rees
2021-08-20 20:29 ` Rich Felker
2021-08-20 21:44 ` Tim Tassonis
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=CAMFK0gsKYoNkoX_M1V4uMWhfTtSWqB4V90YBHMHmZVem-ZujpQ@mail.gmail.com \
    --to=galibert@pobox.com \
    --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).