From: ludo@gnu.org (Ludovic Courtès)
To: e_sheibley@verizon.net
Cc: 14550@debbugs.gnu.org
Subject: bug#14550: libltdl not found during configure of Guile 2.0.9
Date: Wed, 05 Jun 2013 23:27:04 +0200 [thread overview]
Message-ID: <87d2s0xn87.fsf@gnu.org> (raw)
In-Reply-To: <32823289.1061192.1370438007143.JavaMail.root@vms170015> (e. sheibley's message of "Wed, 05 Jun 2013 08:13:27 -0500 (CDT)")
Eric,
(Please keep 14550@debbugs.gnu.org Cc'd.)
e_sheibley@verizon.net skribis:
> It doesn't even get that far. It stops at checking for libltdl and
> says to view the README file for more information.
I know. Yet, ‘configure’ creates a ‘config.log’ file with additional
details, as I explained. Can you please check its contents according to
the recommendations I gave?
Thanks in advance,
Ludo’.
next prev parent reply other threads:[~2013-06-05 21:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-03 19:38 bug#14550: libltdl not found during configure of Guile 2.0.9 Eric Sheibley
2013-06-04 10:24 ` Ludovic Courtès
2013-06-04 18:33 ` Eric Sheibley
2013-06-05 10:56 ` Ludovic Courtès
2013-06-05 13:13 ` bug#14550: " e_sheibley
2013-06-05 21:27 ` Ludovic Courtès [this message]
2013-06-10 19:50 ` Eric Sheibley
2013-06-10 20:48 ` Mark H Weaver
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=87d2s0xn87.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=14550@debbugs.gnu.org \
--cc=e_sheibley@verizon.net \
/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).