[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200616011638.GH6430@brightrain.aerifal.cx>
Date: Mon, 15 Jun 2020 21:16:38 -0400
From: Rich Felker <dalias@...c.org>
To: Jeffrey Walton <noloader@...il.com>
Cc: musl@...ts.openwall.com
Subject: Re: Is Musl responsible for runpath parsing in an elf file?
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.
Rich
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.
