[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAH8yC8kLh6_AaYbZJ36XtQH=DY7hH41e=1AaD4=VNBv0VKzfOQ@mail.gmail.com>
Date: Mon, 15 Jun 2020 21:25:15 -0400
From: Jeffrey Walton <noloader@...il.com>
To: Rich Felker <dalias@...c.org>
Cc: musl@...ts.openwall.com
Subject: Re: Is Musl responsible for runpath parsing in an elf file?
On Mon, Jun 15, 2020 at 9:16 PM Rich Felker <dalias@...c.org> wrote:
>
> On Mon, Jun 15, 2020 at 08:45:18PM -0400, Jeffrey Walton wrote:
> > Hi Everyone,
> >
> > Please forgive my ignorance... Is Musl responsible for runpath parsing
> > during elf loading? If it matters, I'm working on Alpine Linux.
>
> Yes, loading of all libraries except the dynamic linker itself (which
> includes libc on musl) is the responsibility of the dynamic linker and
> is performed in userspace.
>
> When searching for a given library as a dependency (DT_NEEDED), musl's
> processing of rpath/runpath uses the runpath of the shared object
> that's depending on it and causing it to be pulled in, and continues
> this resolution recursively backwards, potentially up to the main
> program's runpath, if not found.
Thanks Rich.
I may have mis-filed this against Alpine:
https://gitlab.alpinelinux.org/alpine/aports/-/issues/11655.
Is it expected behavior? Should I move it to Musl bug tracker?
Jeff
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.
