From: Andy Wingo <wingo@oblong.com>
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:23:19 +0100 [thread overview]
Message-ID: <m31v5cikvc.fsf@oblong.com> (raw)
In-Reply-To: <4D0F63AC.2080303@gnu.org> (Bruce Korb's message of "Mon, 20 Dec 2010 06:09:48 -0800")
Hi Bruce,
Sorry you and others have had to suffer through this.
On Mon 20 Dec 2010 15:09, Bruce Korb <bkorb@gnu.org> writes:
> How much understanding of the machinery should be expected
> of the hapless project builder?
I'm not sure, but:
> 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
This is incorrect, for RHEL and other systems which place 64-bit libs in
$prefix/lib64. You will find hacks to set --libdir in almost all
packaging scripts.
> Perhaps we can strive to make the assumption correct
> in the future?
This idea is attractive, if it can be done. But this is more an autoconf
issue (setting $libdir) than a libtool issue, and it's not a Guile issue
at all :)
Cheers,
Andy
_______________________________________________
http://lists.gnu.org/mailman/listinfo/libtool
next prev parent reply other threads:[~2010-12-20 14:23 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 [this message]
2010-12-20 14:30 ` Ralf Corsepius
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=m31v5cikvc.fsf@oblong.com \
--to=wingo@oblong.com \
--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).