From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: lib64 in fedora glibc
Date: Fri, 28 May 2004 22:14:54 +0000 [thread overview]
Message-ID: <16567.47582.153249.521155@napali.hpl.hp.com> (raw)
In-Reply-To: <20040528214105.GK9115@mustard.zk3.dec.com>
>>>>> On Fri, 28 May 2004 17:41:05 -0400, Aron Griffis <aron@HP.COM> said:
Aron> These snippets from the current fedora glibc.spec look suspicious to
Aron> me.. I was under the impression that ia64 would use /lib for 64-bit
Aron> and /lib32 for 32-bit (or something like that), but it looks like RH
Aron> is preparing to transition to lib64.
I'm no Fedora expert but here it says:
Aron> %changelog:
Aron> * Thu May 20 2004 Jakub Jelinek <jakub@redhat.com> 2.3.3-29
Aron> - use lib64 instead of lib on ia64 if %%{_lib} is defined to lib64
So I guess the question is what would make %%{_lib} be defined as lib64.
IMHO, it would be a bad mistake to create such a disruption.
--david
next prev parent reply other threads:[~2004-05-28 22: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 [this message]
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
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=16567.47582.153249.521155@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