[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20220926220449.GE9709@brightrain.aerifal.cx>
Date: Mon, 26 Sep 2022 18:04:49 -0400
From: Rich Felker <dalias@...c.org>
To: musl@...ts.openwall.com
Subject: Re: Revisiting LFS64 removal
On Sun, Sep 25, 2022 at 09:03:40PM -0400, Rich Felker wrote:
> [...]
> Of course these interfaces should not be used, and we never intended
> for them to be used just there for linking-compat. So, I've wanted to
> get rid of them for a long time now.
>
> I believe the simplest short-term way is probably going to be just
> having the dynamic linker symbol lookup error path make one final
> check before bailing out with an error:
>
> - If the symbol to lookup ends in "64"..
> - ..and it's in a hard-coded list of LFS64-compat symbols..
> - ..and looking up the name with the "64" removed in libc succeeds..
>
> Then use the version without the "64" suffix and go on with relocation
> processing.
Proposed patch attached.
View attachment "0001-remove-LFS64-symbol-aliases-replace-with-dynamic-lin.patch" of type "text/plain" (23425 bytes)
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.
