This is the mail archive of the mailing list for the glibc project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Multiarch interpreter names for traditional architectures

On Sun, Feb 4, 2018 at 11:25 AM, Javier Serrano Polo <> wrote:
> Dear list,
> Multiarch systems allow to run programs from other architectures. ELF
> executables for traditional architectures depend on interpreter names
> that may conflict with each other. For instance, it is complicated to
> run alpha programs on x86 systems.
> Simpler systems use multiarch interpreter names. I am looking for
> consensus since I would like to avoid, e.g., having,
>,, and for x86.
> What would be the proper multiarch names for the following
> architectures? I present suggestions:

Debian's version of "multiarch" (see uses /lib/$(CANONICAL_HOST)/
where $(CANONICAL_HOST) is a slightly adjusted version of the GNU
canonical system identifier.  Historical infixes in the name of
are preserved, but new subarchitectures don't need one. I think this
is better than trying to come up with lname infixes for everything,
since it also gives you somewhere to put all the _other_ files that
are subarchitecture-specific, and it's easy to see how it should be
extended to more complicated scenarios.  There are multiarch
subdirectories of /usr/lib and /usr/include as well as /lib.  I would
like to see it adopted more widely, perhaps even become the GNU-wide


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]