This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: [PATCH][v2] Add dynamic linker support for $EXEC_ORIGIN.
- From: Benjamin Peterson <bp at benjamin dot pe>
- To: Andreas Schwab <schwab at suse dot de>, Brooks Moses <bmoses at google dot com>
- Cc: "libc-alpha" <libc-alpha at sourceware dot org>, "Carlos O'Donnell" <carlos at redhat dot com>, Paul Pluzhnikov <ppluzhnikov at google dot com>, Stan Shebs <stanshebs at google dot com>
- Date: Tue, 24 Oct 2017 23:44:20 -0700
- Subject: Re: [PATCH][v2] Add dynamic linker support for $EXEC_ORIGIN.
- Authentication-results: sourceware.org; auth=none
- References: <1386886419-18491-1-git-send-email-bmoses@google.com> <20171024050715.5F4137F94E@mailuser.nyi.internal> <CAOxa4KoidbP2n8dSFkXeDyowA0Fcsbyw7PmAR5M9Zc84h41aFQ@mail.gmail.com> <mvmr2ttyncu.fsf@suse.de>
On Tue, Oct 24, 2017, at 01:13, Andreas Schwab wrote:
> On Okt 24 2017, Brooks Moses <bmoses@google.com> wrote:
>
> > (Quick summary: $EXEC_ORIGIN in rpaths is like $ORIGIN, but it expands
> > to the executable's path as passed to execve(), rather than resolving
> > symlinks in the executable's path as $ORIGIN does.)
>
> I think the name is confusing, since both $EXEC_ORIGIN and $ORIGIN
> expand to the origin of the executable.
I suppose the $EXEC_ORIGIN token takes its name from the elf auxiliary
vector, AT_EXECFN, it's derived from.
Would $SYMBOLIC_ORIGIN be bettter?