top | item 41455440

(no title)

awilfox | 1 year ago

> Either way, super cool. What's the likelihood that this ends up getting upstreamed?

High: <https://github.com/systemd/systemd/pulls?q=is%3Apr+author%3A...>.

discuss

order

blueflow|1 year ago

kokada|1 year ago

I don't think Lennart changed his opinion, if you look further in this thread[1] Lenart wasn't ever against musl per se, it is more like "we use non-POSIX features from glibc that we found useful, and we are not going to reinvent them, so either convince musl to implement those features or carry patches fixing the issues". That I kind concur with him, instead of workaround missing functions it may be better to just write a compatibility library that complements musl with the missing functions. This way, any program that needs those functions could just import this library if they're compiling in a non-glibc system.

I am seeing that lots of the fixes proposed by the author are things like "missing import because glibc exposes some symbols by mistake and musl does not". And this is definitely the kind of fix that upstream would accept[2].

[1]: https://github.com/systemd/systemd/issues/10130

[2]: https://github.com/systemd/systemd/pull/34066

bhaney|1 year ago

Less than a day later and everything in this list is already merged. Congrats!

Do those PRs represent everything necessary to compile systemd against musl, or are there more PRs coming to finish the job?