Multiarch interpreter names for traditional architectures

Zack Weinberg zackw@panix.com
Fri Feb 9 15:24:00 GMT 2018


On Fri, Feb 9, 2018 at 9:56 AM, Javier Serrano Polo <javier@jasp.net> wrote:
> El dv 09 de 02 de 2018 a les 14:34 +0000, Joseph Myers va escriure:
>> I think your present advocacy is an effective argument *against* any
>> additions to multiarch support in the GNU toolchain.
>
> My ability to implement multiarch solutions, just like I did in the
> past, is an argument in favor. Your inability to provide interpreter
> names that solve file conflicts in multiarch systems is a proof of your
> competence about this matter.

Both of these statements are pushing the boundary between technical
debate and personal attacks. Please take a step back, both of you, and
calm down a little.

It is true that the ELF psABI for x86-64/linux/glibc specifies
/lib64/ld-linux-x86-64.so.2 as the mandatory name of the program
interpreter, but that doesn't have to be set in stone forever.
Changes are difficult and have to be carefully staged, but I don't see
that it's on the level of, oh, changing libc.so's SONAME.  It seems
more like merging / and /usr, which is a thing at least some groups
are actively working on.

zw



More information about the Libc-alpha mailing list