[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20230717152103.GK4163@brightrain.aerifal.cx>
Date: Mon, 17 Jul 2023 11:21:04 -0400
From: Rich Felker <dalias@...c.org>
To: Dave Blanchard <dave@...lthe.net>
Cc: musl@...ts.openwall.com
Subject: Re: musl -- FFS get your shit together, please
On Mon, Jul 17, 2023 at 01:17:58AM -0500, Dave Blanchard wrote:
> There's a lot to like about musl, but damn, there's some absolutely ridiculous aspects also:
>
> 1) How in the hell are you going to make a MAJOR change like
> changing #ifdefs from defined(_LARGEFILE64_SOURCE) ||
> defined(_GNU_SOURCE) to just defined(_LARGEFILE64_SOURCE) in a PATCH
> level increment, from 1.2.3 to 1.2.4? What the hell is wrong with
> you? You just broke my entire build! Yet another patch had to be
> created on my end to UNDO this crazy change; the only alternative
> was patching half the packages on my system to fix their now-broken
> build! Do you know NOTHING about proper versioning???
Our versioning system works like this: in x.y.z,
- increment of x, likely to never happen, would indicate a completely
different ABI
- increment of y indicates a change whereby programs compiled for the
new y, even without use of any new features added in new y, may not
run with an older y. canonical example: time64.
- increment of z indicates a change whereby programs built for the new
z should still run on older z (modulo any bugs that might be present
in the older version) as long as they're not using new interfaces
introduced in the new z.
All of these conditions are assuming the program used the public
interfaces and did not poke at unspecified internals, etc.; if it did,
all bets are off and any version change may be fully-breaking to the
program.
Note that all of these deal with ABI compatibility, not compile-time
compatibility.
> 2) Did it occur to anyone involved in this project to maybe actually
> organize and COMMENT the system header files, instead of just
> randomly throwing a random assortment of shit into an .H file and
> calling it good?
The header files intentionally do not contain nontrivial creative
content.
> 3) Why in the hell does musl duplicate/change(!) internal structures
> from Linux kernel headers instead of just #include'ing the damn
> Linux headers (and relevant structures) and be done with it?
Because we are defining the interface between an application and the
standard library functions not between libc and the kernel or the
application and the kernel.
Sometimes the types will be the same; sometimes they *cannot* (e.g.
when the kernel type is wrong or does not meet the specified
requirements).
Even when the types do match, the Linux uapi headers are generally not
namespace-safe.
> 4) Would it kill you to add in various simple #defines and such in
> the headers which greatly improve compatibility with GNU code,
> without actually requiring any support in the libc library code??
I'm not sure what this question even means. Are you talking about the
LFS64 stuff again or something else? The LFS64 macros were removed
(by default) because they were a repeated source of breakage that was
*our fault* compiling C++ programs (where GCC makes _GNU_SOURCE the
default), and thereby our responsibility to fix. The only reason they
were ever added to begin with was because of configure scripts wrongly
detecting LFS64 via link-only tests, resulting in failed builds or
(more often) broken binaries when the LFS64 symbols, which were only
there as ABI-compat for glibc-linked code, got used without any
declarations ("implicit function").
The way this was fixed, very little should have broken. From reports
so far, it seems to have been only a very small amount of
Linux-specific code or code that hard-coded "Linux implies LFS64",
most of which already has patches fixing it.
> Between the above, plus the 6-7 "musl addon" support packages
> required to be installed alongside to make my Linux system build
> with musl, at this point I have essentially FORKED musl!
>
> Musl is clearly not designed with Linux workstation usage in mind!
*eyeroll*
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
