From: primus <rprimus@gmail.com>
To: Ludovic Court?s <ludo@gnu.org>
Cc: bug-guile@gnu.org
Subject: Re: [1.9.12] configure and --with-libltdl-prefix ...
Date: Mon, 6 Sep 2010 06:47:30 +0100 [thread overview]
Message-ID: <20100906054730.GP32103@x.lence.net> (raw)
In-Reply-To: <87wrqzzumu.fsf@gnu.org>
On Mon, Sep 06, 2010 at 12:35:21AM +0200, Ludovic Court?s wrote:
> > Sun Sep 5 22:01:44 BST 2010
> >
> > The README implies that the option is available.
>
> What in the README makes you think so?
Mon Sep 6 06:39:36 BST 2010
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,
It lists each library and states that there is a corresponding
'with-XXX-prefix'.
# grep 'with-' configure | grep prefix
--with-libiconv-prefix[=DIR] search for libiconv in DIR/include and DIR/lib
--with-libunistring-prefix[=DIR] search for libunistring in DIR/include and DIR/lib
--with-libgmp-prefix[=DIR] search for libgmp in DIR/include and DIR/lib
--with-libintl-prefix[=DIR] search for libintl in DIR/include and DIR/lib
--with-libreadline-prefix[=DIR] search for libreadline in DIR/include and DIR/lib
The following *do not* exist in configure (as implied from README):
--with-libltdl-prefix
--with-libffi-prefix
--with-libbgc-prefix
--
-primus
"It isn't what you make, it's what you don't lose!"
next prev parent reply other threads:[~2010-09-06 5:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-05 17:12 [1.9.12] configure and --with-libltdl-prefix primus
2010-09-05 20:51 ` Ludovic Courtès
2010-09-05 21:20 ` primus
2010-09-05 22:35 ` Ludovic Courtès
2010-09-06 5:47 ` primus [this message]
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=20100906054730.GP32103@x.lence.net \
--to=rprimus@gmail.com \
--cc=bug-guile@gnu.org \
--cc=ludo@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).