From: Ralf Corsepius <rc040203@freenet.de>
To: Bruce Korb <bkorb@gnu.org>
Cc: Bruce Korb <bruce.korb@gmail.com>,
Noah Lavine <noah.b.lavine@gmail.com>,
Libtool List <libtool@gnu.org>,
"Nelson H. F. Beebe" <beebe@math.utah.edu>,
guile-devel@gnu.org
Subject: Re: How does one specify linking to 64 bit libraries when there is a choice?
Date: Mon, 20 Dec 2010 15:30:54 +0100 [thread overview]
Message-ID: <4D0F689E.9020309@freenet.de> (raw)
In-Reply-To: <4D0F63AC.2080303@gnu.org>
On 12/20/2010 03:09 PM, Bruce Korb wrote:
> On 12/19/10 20:40, Noah Lavine wrote:
>> Hello,
>>
>> I am not at all an expert on guile-config, but I will help if I can.
>
> Thank you to all who responded.
>
>> Usually if you have 64-bit libs in lib64, you have to pass --libdir
>> explicitly.
>
> We've now concluded that that is, indeed, the answer to the
> original question. The fallout question:
>
> How much understanding of the machinery should be expected
> of the hapless project builder?
>
> Nelson has been doing this stuff for quite a while and has
> reasonably good understanding of the process. From that
> understanding, he made the assumption that a standard 64 bit
> "Red Hat Enterprise Linux Server release 5.5 (Tikanga)"
> installation would be compatible with installing Guile via
> ./configure&& make&& sudo make install
> and not wind up with a frumitzed `guile-config link` output.
> The assumption was incorrect and we now know that.
Correct, this assumption is incorrect.
(With my Fedora Packaging Committee member hat on) In Fedora and RHEL,
users are supposed to pass
--libdir=/usr/lib64 to configure
on x86_64 and
--libdir=/usr/lib to configure
on i386.
Analogous conventions apply to other multilib'ed architectures.
Ralf
_______________________________________________
http://lists.gnu.org/mailman/listinfo/libtool
next prev parent reply other threads:[~2010-12-20 14:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CMM.0.95.0.1292615864.beebe@psi.math.utah.edu>
2010-12-17 20:10 ` How does one specify linking to 64 bit libraries when there is a choice? Bruce Korb
2010-12-20 4:40 ` Noah Lavine
2010-12-20 10:56 ` Andy Wingo
2010-12-20 14:09 ` Bruce Korb
2010-12-20 14:23 ` Andy Wingo
2010-12-20 14:30 ` Ralf Corsepius [this message]
2010-12-20 19:20 ` Ralf Wildenhues
2010-12-20 19:25 ` Ralf Wildenhues
[not found] <AANLkTik3wAm4j4mqigf3-j0Kb=3HJ3OY-_sfhsiu3k-f@mail.gmail.com>
[not found] ` <CMM.0.95.0.1292605766.beebe@psi.math.utah.edu>
2010-12-17 17:31 ` Bruce Korb
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4D0F689E.9020309@freenet.de \
--to=rc040203@freenet.de \
--cc=beebe@math.utah.edu \
--cc=bkorb@gnu.org \
--cc=bruce.korb@gmail.com \
--cc=guile-devel@gnu.org \
--cc=libtool@gnu.org \
--cc=noah.b.lavine@gmail.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).