public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: lib64 in fedora glibc
Date: Fri, 04 Jun 2004 06:21:00 +0000	[thread overview]
Message-ID: <16576.5324.963519.166097@napali.hpl.hp.com> (raw)
In-Reply-To: <20040528214105.GK9115@mustard.zk3.dec.com>

>>>>> On Fri, 04 Jun 2004 07:08:18 +0200, Andreas Jaeger <aj@suse.de> said:

  Andreas> We're speaking here about native code - and not emulations.
  Andreas> So, for ia64 I only see two native codes right now: 64-bit
  Andreas> code as it is and code using 32-bit pointers (don't know
  Andreas> how it's called).

That'd be ia64/ILP32, which isn't supported on Linux (or Windows,
though it is on HP-UX).

  Andreas> And x86 on ppc64 would be an emulation - not the native code - and
  Andreas> would end somewhere else.

Yep.

  Andreas> Note that what your table says about ppc64 and x86-64 above
  Andreas> is correct - and you can add s390, mips and sparc64 under
  Andreas> the same line.  Sparc has done this for a long time
  Andreas> already.

Yep.

  Andreas> I don't know what Red Hat is doing with x86 and with lib64 - and you
  Andreas> really should ask them for clarification.

Certainly.  I only wished Red Hat would be more
willing/interested/active in discussing such things on public mailing
lists.

  Andreas> Footnotes:
  Andreas> [1]  Note I'm more concerned with x86-64, I'm not advocating here
  Andreas> anything for ia64.

No problem.  I just wanted to make it clear why I think it would be
short-sighted to pub x86 libraries in /usr/lib on ia64.

	--david

  parent reply	other threads:[~2004-06-04  6:21 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-28 21:41 lib64 in fedora glibc Aron Griffis
2004-05-28 22:14 ` David Mosberger
2004-05-29  3:33 ` Aron Griffis
2004-05-29  5:21 ` Grant Grundler
2004-06-01  9:48 ` Andreas Jaeger
2004-06-04  4:58 ` David Mosberger
2004-06-04  5:08 ` Andreas Jaeger
2004-06-04  6:21 ` David Mosberger [this message]
2004-06-04  8:16 ` Christoph Hellwig
2004-06-04 19:23 ` Bill Nottingham
2004-06-04 20:14 ` David Mosberger
2004-06-04 20:21 ` Bill Nottingham
2004-06-04 22:15 ` David Mosberger
2004-06-07 20:05 ` Saxena, Sunil
2004-06-07 20:09 ` Bill Nottingham
2004-06-07 21:06 ` Andreas Schwab
2004-06-07 21:18 ` Bill Nottingham
2004-06-07 21:58 ` Andreas Schwab
2004-06-07 22:14 ` Bill Nottingham

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=16576.5324.963519.166097@napali.hpl.hp.com \
    --to=davidm@napali.hpl.hp.com \
    --cc=linux-ia64@vger.kernel.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