[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAOUYtQAEgBss_mGiOL=rt5YATQkahEa417aMYibpQr4mKsdajw@mail.gmail.com>
Date: Wed, 11 Mar 2026 12:11:07 +0000
From: Jon Chesterfield <jonathanchesterfield@...il.com>
To: musl@...ts.openwall.com
Subject: Path for deploying clang on glibc systems
Hello Musl,
Clang and llvm have relatively complete support for musl now. I.e. the
glibc dependencies are gone. A statically linked clang works.
Some years ago I tried to ship llvm dynamically linked against musl and
failed - couldn't install the musl loader globally, interp path wanted an
absolute string and I don't know the target filesystem layout.
Dynamic linking of libLLVM.so and libclang-cpp.so has a drastic impact on
toolchain size so dropping that is a tough sell.
It seems obvious that musl could be statically linked into the main
executable, do the dynlib setup work as usual, then branch to the
executable main to get a self contained path independent distribution.
I haven't seen this done though. Am I unobservant in and such a trick is
already available, is it a case of patches considered, or is this just a
dumb thing I shouldn't do?
Context is people wanting to run on weird kernel configurations and I don't
want exposure to glibc bugs circa two decades ago.
Thanks all!
Jon
Content of type "text/html" skipped
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.
