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 20:14:30 +0000	[thread overview]
Message-ID: <16576.55334.917601.818029@napali.hpl.hp.com> (raw)
In-Reply-To: <20040528214105.GK9115@mustard.zk3.dec.com>

>>>>> On Fri, 4 Jun 2004 15:23:19 -0400, Bill Nottingham <notting@redhat.com> said:

  Bill> Where this came out of was requests from various partners and
  Bill> We can always just live with crappy ia32 (and by extension,
  Bill> x86-64) support on ia64. :)

I don't think "crappy" is acceptable but it doesn't have to be perfect
on ia64, because you 99% of the apps on a typically Linux box will be
ia64-native binaries (I'd imagine the reverse may often be true for
x86-64).

Again, I don't think multi-arch support is ia64-specific, so whatever
can be done to improve this support will help other platforms, too.
I'm guessing that some of the ISV problems have come from the fact
that they tried to install _everything_ into /emul/ia32-linux?  That
is probably not the best approach.  For self-contained applications,
just installing in /opt or some place like that should work just fine
(and in my experience it does).  /emul/ia32-linux should probably be
reserved for use for files that are known or very likely to collide
with ia64 files of the same name (such as the gtk engine shared
libraries).

As for running shell scripts: isn't there a linux32 command that takes
care of that?

	--david

  parent reply	other threads:[~2004-06-04 20:14 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
2004-06-04  8:16 ` Christoph Hellwig
2004-06-04 19:23 ` Bill Nottingham
2004-06-04 20:14 ` David Mosberger [this message]
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.55334.917601.818029@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