From: ludo@gnu.org (Ludovic Courtès)
To: bug-guile@gnu.org
Subject: Re: Build Error in Latest Git
Date: Fri, 17 Dec 2010 19:52:18 +0100 [thread overview]
Message-ID: <878vzo2pwd.fsf@gnu.org> (raw)
In-Reply-To: AANLkTi=VRtwhcin6wa_Bj8Uo6e73XpDNQK4aGgbDHW0D@mail.gmail.com
Hi,
Noah Lavine <noah.b.lavine@gmail.com> writes:
> After looking at this a bit more, I think it's an issue with Gnulib,
> or possibly the configuration system. I'd like to report it to one of
> those projects, but could someone tell me how Guile's configuration
> mechanism interacts with Gnulib's? I don't really understand what is
> configuring Gnulib, since it has no configure script.
Gnulib is a library of source files, including C files, Autoconf macros,
etc.
Guile uses Gnulib’s ‘libunistring’ module, which in turn depends on the
‘iconv’ module (see m4/gnulib-cache.m4 in the Guile tree). The latter
is the one that provides the ‘--with-libiconv-prefix’ configure option
and the $(LTLIBICONV) variable used in libguile/Makefile.am. On non-GNU
systems, that variable should be non-empty.
Hopefully this is enough info to ping bug-gnulib@gnu.org. :-)
Thanks,
Ludo’.
next prev parent reply other threads:[~2010-12-17 18:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-15 6:49 Build Error in Latest Git Noah Lavine
2010-12-15 21:02 ` Andy Wingo
2010-12-15 21:19 ` Noah Lavine
2010-12-17 17:10 ` Noah Lavine
2010-12-17 18:52 ` Ludovic Courtès [this message]
2010-12-17 22:06 ` Andy Wingo
2010-12-17 22:12 ` Noah Lavine
2010-12-17 20:51 ` Ludovic Courtès
2010-12-17 18:53 ` Ludovic Courtès
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=878vzo2pwd.fsf@gnu.org \
--to=ludo@gnu.org \
--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).