This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: Multiarch interpreter names for traditional architectures
- From: Andreas Schwab <schwab at suse dot de>
- To: Javier Serrano Polo <javier at jasp dot net>
- Cc: libc-alpha at sourceware dot org, javier--CbphpPOVok9WFxGWvC7CbkqlsxDZyT at jasp dot net
- Date: Mon, 05 Feb 2018 10:19:18 +0100
- Subject: Re: Multiarch interpreter names for traditional architectures
- Authentication-results: sourceware.org; auth=none
- References: <1517756479.29018.96.camel@sempati.menos4> <9d0835f0-4999-a901-8c9b-6c7256711161@redhat.com> <1517768205.29018.129.camel@sempati.menos4> <32928025-73aa-dd3b-40c0-05ab9850debc@redhat.com> <1517816006.21342.52.camel@sempati.menos4>
On Feb 05 2018, Javier Serrano Polo <javier@jasp.net> wrote:
> We are still in the alpha on x86 example. What happens today on your
> systems:
>
> 1. Kernel starts the alpha emulator.
> 2. The emulator looks for /lib/ld-linux.so.2.
> 3. The program fails.
>
> What happens today on my systems:
>
> 1. Kernel starts the alpha emulator.
> 2. The emulator looks for /lib/ld-linux.so.2.
> 3. User has configured the emulator to redirect all file operations
> to /lib/ld-linux-alpha.so.2.
> 4. The program runs, but the path /lib/ld-linux.so.2 will not work
> as expected.
Why hasn't the emulator been configured to look in a sysroot first?
Andreas.
--
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."