From: primus <rprimus@gmail.com>
To: bug-guile@gnu.org
Subject: [1.9.12] configure and --with-libltdl-prefix ...
Date: Sun, 5 Sep 2010 18:12:23 +0100 [thread overview]
Message-ID: <20100905171223.GN32103@x.lence.net> (raw)
Sun Sep 5 18:09:09 BST 2010
Please see: http://paste.lisp.org/display/114265
Above set to expire in 1 day, so here is the info posted:
OS: OpenBSD 4.7
# pkg_info | grep ltdl
libltdl-1.5.26p0 GNU libtool system independent dlopen wrapper
# ls -la /usr/local/lib/*ltdl*
-rw-r--r-- 1 root bin 28806 Nov 1 2007 /usr/local/lib/libguile-ltdl.so.1.0
-rw-r--r-- 1 root wheel 27148 Mar 18 14:36 /usr/local/lib/libltdl.a
-rw-r--r-- 1 root wheel 783 Mar 18 14:36 /usr/local/lib/libltdl.la
-rw-r--r-- 1 root wheel 32932 Mar 18 14:36 /usr/local/lib/libltdl.so.4.5
# ./configure --with-libltdl-prefix=/usr/local 2>&1 | tee configure.l1g
# head -1 configure.l1g
configure: WARNING: unrecognized options: --with-libltdl-prefix
# tail -1 configure.l1g
configure: error: libltdl not found. See README.
from README:
Guile depends on the following external libraries.
- libgmp
- libiconv
- libintl
- libltdl
- libunistring
- libgc
- libffi
It will also use the libreadline library if it is available. For each
of these there is a corresponding --with-XXX-prefix option that you
can use when invoking ./configure, if you have these libraries
installed in a location other than the standard places (/usr and
/usr/local).
above implies that option --with-libltdl-prefix should exist.
successful configure using:
env LDFLAGS="/usr/local/lib" ./configure
--
-primus
"It isn't what you make, it's what you don't lose!"
next reply other threads:[~2010-09-05 17:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-05 17:12 primus [this message]
2010-09-05 20:51 ` [1.9.12] configure and --with-libltdl-prefix Ludovic Courtès
2010-09-05 21:20 ` primus
2010-09-05 22:35 ` Ludovic Courtès
2010-09-06 5:47 ` primus
2010-09-07 22:46 ` Ludovic Courtès
2010-09-11 7:14 ` primus
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=20100905171223.GN32103@x.lence.net \
--to=rprimus@gmail.com \
--cc=bug-guile@gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).