[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <beb6c4cb-7227-4634-86b4-cfa04db1b983@redhat.com>
Date: Thu, 13 Nov 2025 12:50:38 -0500
From: Carlos O'Donell <codonell@...hat.com>
To: musl@...ts.openwall.com, Rich Felker <dalias@...c.org>,
Fredrik Orderud <forderud@...il.com>
Subject: Re: Safe to load musl shared lib into glibc executable?
On 11/12/25 9:47 AM, Rich Felker wrote:
> You probably need to be doing what most folks doing this with glibc
> hosts do, and linking your library dynamically against an ancient
> version of glibc to avoid pulling in versioned symbol deps on newer
> versions. This also requires committing to supporting whatever bugs
> the old versions of the affected interfaces might have. Unfortunately
> I don't think there's a way musl can help make this situation any
> better.
I agree that this isn't a "musl" problem, but rather a general toolchain
question.
You need a curated sysroot and you need your tools configured to use
that sysroot if you have these specific needs.
--
Cheers,
Carlos
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.
