From: Andreas Jaeger <aj@suse.de>
To: linux-ia64@vger.kernel.org
Subject: Re: lib64 in fedora glibc
Date: Tue, 01 Jun 2004 09:48:56 +0000 [thread overview]
Message-ID: <hollj7wquv.fsf@reger.suse.de> (raw)
In-Reply-To: <20040528214105.GK9115@mustard.zk3.dec.com>
[-- Attachment #1: Type: text/plain, Size: 1026 bytes --]
Grant Grundler <iod00d@hp.com> writes:
> 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.
Just a clarification: AMD64 [1] has most of user space 64-bit. Only a
few applications are 32-bit - but this lib/lib64 is the best way to
handle 32-bit packages (no need to change files).
> Moving to lib32 and lib64 makes sense in that environment.
Not lib32, just lib.
Andreas
Footnotes:
[1] at least the SUSE distribution but I assume others as well.
--
Andreas Jaeger, aj@suse.de, http://www.suse.de/~aj
SUSE Linux AG, Maxfeldstr. 5, 90409 Nürnberg, Germany
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
[-- Attachment #2: Type: application/pgp-signature, Size: 188 bytes --]
next prev parent reply other threads:[~2004-06-01 9:48 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 [this message]
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=hollj7wquv.fsf@reger.suse.de \
--to=aj@suse.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.