From: Grant Grundler <iod00d@hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: lib64 in fedora glibc
Date: Sat, 29 May 2004 05:21:49 +0000 [thread overview]
Message-ID: <20040529052149.GA3177@cup.hp.com> (raw)
In-Reply-To: <20040528214105.GK9115@mustard.zk3.dec.com>
On Fri, May 28, 2004 at 11:33:36PM -0400, Aron Griffis wrote:
> > So I guess the question is what would make %%{_lib} be defined as lib64.
>
> Right, that's why I suggested it appears they're preparing for the
> transition.
"the transition" might be necessary to support x86_64.
Ie most of user space is 32-bit (using /lib) but some apps
will run substantially better as native x86_64 binaries.
Moving to lib32 and lib64 makes sense in that environment.
Hypothetically, it shouldn't matter for ia64 if /lib
is an alias for /lib64. Or do I see that wrong?
I thought ia64 already has from /lib32-like thing to
support ia32 binaries but I'm not the tool chain expert.
grant
next prev parent reply other threads:[~2004-05-29 5: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 [this message]
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
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=20040529052149.GA3177@cup.hp.com \
--to=iod00d@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