This is the mail archive of the
mailing list for the GCC project.
Re: Phone call (was Re: Armhf dynamic linker path)
- From: Jakub Jelinek <jakub at redhat dot com>
- To: Mike Frysinger <vapier at gentoo dot org>
- Cc: cross-distro at lists dot linaro dot org, Riku Voipio <riku dot voipio at linaro dot org>, Adam Conrad <adconrad at debian dot org>, linaro-toolchain at lists dot linaro dot org, Steve McIntyre <steve dot mcintyre at linaro dot org>, Jeff Law <law at redhat dot com>, gcc-patches at gcc dot gnu dot org, libc-ports at sourceware dot org
- Date: Thu, 12 Apr 2012 19:53:13 +0200
- Subject: Re: Phone call (was Re: Armhf dynamic linker path)
- References: <email@example.com> <CAAqcGHmJL4jiL8u3MMqw_B38m1HHbVGdZouiEqJV3o_JkLPf5g@mail.gmail.com> <20120412074729.GJ16117@tyan-ft48-01.lab.bos.redhat.com> <firstname.lastname@example.org>
- Reply-to: Jakub Jelinek <jakub at redhat dot com>
On Thu, Apr 12, 2012 at 01:49:16PM -0400, Mike Frysinger wrote:
> > ia64 installs in /lib, because it isn't a multilibbed architecture.
> because distros choose not to support it. in first gen chips, there was
> hardware support for running x86. so if we were to be strict, there should
> have been /libia64/ (or whatever) while the current x86 32bit code would stay
> in /lib/. but no distro was interested in supporting that (probably due to
> the 32bit x86 layers being balls-ass slow), so it never happened.
We even carried patches (not applied) for lib64 ia64 support in our
binutils/glibc/gcc for a while, but the final decision after these were
written was that it is going to stay in /lib.