From: "Laurent Bercot" <firstname.lastname@example.org>
Subject: Re: [musl] ITT: Nothing but a bunch of excuses and no solutions
Date: Mon, 17 Jul 2023 17:23:49 +0000 [thread overview]
Message-ID: <email@example.com> (raw)
>Translated: our code is an uncommented, disorganized mess and we love it.
Would you kindly give us a pointer to *your* code, so we can go study
and learn from what is doubtlessly a paragon of clarity, cleanliness and
>Translated: the end user will need to patch the musl headers to stop defining custom, bespoke, incompatible versions of kernel structures and just include the damn kernel header files so that their system will actually build properly.
You do, of course, realize that the initial reason why some software
has trouble with mixing musl and linux headers is that Linux itself
generally does not favor including kernel headers in userspace, and the
whole uapi system is an ifdef forest that is still, as of today, full
of glibcisms, right?
How long have you been building systems? Because doing wild stuff like
*building a Linux system with another libc* is a piece of cake today.
Back in 2002, it was downright impossible; the ecosystem has made a
lot of progress since.
I would never dare suggest that the obstacles you seem to be bumping
into stem from your own inexperience - not in a million years. However,
now is really a good time to relax and enjoy the relative ease of
building systems, and it is a shame that you do not seem to be relaxing
and enjoying it.
>Maybe you should try building your own Linux distribution so you will get a clue!
This is definitely strange, because I have been building my own systems
with musl for a while now, and I have not experienced half of the
you seem to be running into - and when I have run into obstacles, the
issues were usually with the rest of the software, not with musl.
I wonder why our experiences differ so much. It certainly cannot be a
skill or knowledge issue.
>Translation: the end user will now need to apply heavy patches to his/her system, and/or patch musl 1.2.4 to revert the old behavior, in order to get their damn system to actually build correctly.
This end user disagrees, and wonders why you seem to have so much
difficulty using a computer. Have you tried turning it off and on again?
>Once again: MUSL IS CLEARLY NOT DESIGNED WITH LINUX WORKSTATION USAGE IN MIND!
You know what? You're absolutely right - it is, at least, clearly not
designed with *your* Linux workstation usage in mind. The best path for
you is clearly to write down your musl usage attempt as a failure, and
give it up entirely. You should go back to using glibc, which will be
much easier, and you can make their mailing-list benefit from your
insightful, constructive, and heart-warming comments!
There is no reason for you to keep interacting with a community that
does not understand your genius or address your so eloquently worded
concerns. We're not worthy of your presence, you should leave us to
next prev parent reply other threads:[~2023-07-17 17:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-17 6:17 [musl] musl -- FFS get your shit together, please Dave Blanchard
2023-07-17 7:20 ` (GalaxyMaster)
2023-07-17 12:14 ` Daniel Gutson
2023-07-17 15:21 ` Rich Felker
2023-07-17 15:43 ` [musl] ITT: Nothing but a bunch of excuses and no solutions Dave Blanchard
2023-07-17 15:50 ` Joakim Sindholt
2023-07-17 17:12 ` Rich Felker
2023-07-17 17:23 ` Laurent Bercot [this message]
2023-07-17 16:01 ` [musl] musl -- FFS get your shit together, please Jeffrey Walton
2023-07-17 16:10 ` Joakim Sindholt
2023-07-17 16:55 ` Rich Felker
2023-07-17 15:32 ` Markus Wichmann
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).