public inbox for libc-ports@sourceware.org
 help / color / mirror / Atom feed
From: Jakub Jelinek <jakub@redhat.com>
To: Mike Frysinger <vapier@gentoo.org>
Cc: cross-distro@lists.linaro.org,
	Riku Voipio <riku.voipio@linaro.org>,
	       Adam Conrad <adconrad@debian.org>,
	linaro-toolchain@lists.linaro.org,
	       Steve McIntyre <steve.mcintyre@linaro.org>,
	Jeff Law <law@redhat.com>,
	       gcc-patches@gcc.gnu.org, libc-ports@sourceware.org
Subject: Re: Phone call (was Re: Armhf dynamic linker path)
Date: Thu, 12 Apr 2012 17:53:00 -0000	[thread overview]
Message-ID: <20120412175313.GQ16117@tyan-ft48-01.lab.bos.redhat.com> (raw)
In-Reply-To: <201204121349.19097.vapier@gentoo.org>

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.

	Jakub

  reply	other threads:[~2012-04-12 17:53 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20120331103406.GA17776@einval.com>
     [not found] ` <201204100019.13472.vapier@gentoo.org>
     [not found]   ` <4F83B5AD.3010302@redhat.com>
     [not found]     ` <201204100033.08853.vapier@gentoo.org>
     [not found]       ` <4F83B939.10205@redhat.com>
     [not found]         ` <4F84AC96.6020500@redhat.com>
     [not found]           ` <20120411010608.GC25263@einval.com>
     [not found]             ` <20120411223755.GD25263@einval.com>
2012-04-11 23:22               ` Michael Hope
     [not found]                 ` <CAHAq8pGbEtmu=QuOFGJpPCck6fFmb63Zm+Ax5B9Bg-m3U1UQ_w@mail.gmail.com>
2012-04-12  0:16                   ` Michael Hope
2012-04-12  1:15                     ` Paulo César Pereira de Andrade
2012-04-12  1:40                       ` Michael Hope
2012-04-12  2:15                         ` Paulo César Pereira de Andrade
     [not found]                     ` <20120412003801.GS26898@dream.aleph1.co.uk>
2012-04-12  1:27                       ` Michael Hope
2012-04-12  6:06                 ` Jakub Jelinek
     [not found]                   ` <CAAqcGHmJL4jiL8u3MMqw_B38m1HHbVGdZouiEqJV3o_JkLPf5g@mail.gmail.com>
2012-04-12  7:48                     ` Jakub Jelinek
2012-04-12 17:48                       ` Mike Frysinger
2012-04-12 17:53                         ` Jakub Jelinek [this message]
2012-04-12 18:14                           ` Mike Frysinger
2012-04-12 17:46                   ` Mike Frysinger
2012-04-12 20:33                   ` Paulo César Pereira de Andrade

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20120412175313.GQ16117@tyan-ft48-01.lab.bos.redhat.com \
    --to=jakub@redhat.com \
    --cc=adconrad@debian.org \
    --cc=cross-distro@lists.linaro.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=law@redhat.com \
    --cc=libc-ports@sourceware.org \
    --cc=linaro-toolchain@lists.linaro.org \
    --cc=riku.voipio@linaro.org \
    --cc=steve.mcintyre@linaro.org \
    --cc=vapier@gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).