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: Zack Weinberg <zackw at panix dot com>
- To: Joseph Myers <joseph at codesourcery dot com>
- Cc: javier--CbphpPOVok9WFxGWvC7CbkqlsxDZyT at jasp dot net, GNU C Library <libc-alpha at sourceware dot org>
- Date: Mon, 5 Feb 2018 15:03:47 -0500
- Subject: Re: Multiarch interpreter names for traditional architectures
- Authentication-results: sourceware.org; auth=none
- References: <1517756479.29018.96.camel@sempati.menos4> <CAKCAbMiO=_0VBy-E3dgmDkxQjH+U2hetbWi1rnQWNn5cqta4HA@mail.gmail.com> <alpine.DEB.2.20.1802051802490.4209@digraph.polyomino.org.uk>
On Mon, Feb 5, 2018 at 1:05 PM, Joseph Myers <joseph@codesourcery.com> wrote:
> On Sun, 4 Feb 2018, Zack Weinberg wrote:
>
>> extended to more complicated scenarios. There are multiarch
>> subdirectories of /usr/lib and /usr/include as well as /lib. I would
>
> Unfortunately, glibc support for this has not been contributed upstream
> and I don't think binutils support has been either (ld knows about lib64
> etc. directories in the form of LIBPATH_SUFFIX settings). (GCC support
> *is* upstream.)
Javier, perhaps that is something you would be interested in working
on? You would need to coordinate with the Debian maintainers of
binutils and glibc. It would probably be best to get binutils support
completely upstreamed before doing anything with glibc.
zw