From: Andy Wingo <wingo@pobox.com>
To: Kiyoshi KANAZAWA <yoi_no_myoujou@yahoo.co.jp>
Cc: 19365-done@debbugs.gnu.org
Subject: bug#19365: [guile-2.0.11] libunistring with iconv required even if specify --disable-nls
Date: Wed, 22 Jun 2016 21:17:48 +0200 [thread overview]
Message-ID: <87lh1xrq1v.fsf@pobox.com> (raw)
In-Reply-To: <924286.22545.qm@web101211.mail.kks.yahoo.co.jp> (Kiyoshi KANAZAWA's message of "Sat, 13 Dec 2014 18:50:19 +0900 (JST)")
On Sat 13 Dec 2014 10:50, Kiyoshi KANAZAWA <yoi_no_myoujou@yahoo.co.jp> writes:
> Hello,
>
> Tring to make guile-2.0.11 without NLS.
>
> ./configure --disable-nls --without-libiconv-prefix
> fails with message:
> checking whether libunistring was built with iconv support... no
> configure: error: No iconv support. Please recompile libunistring with
> iconv enabled.
>
> Is this correct ?
>
> (tested on Solaris10 x86.)
Hi :)
I read this and the followup messages. This situation is correct.
--disable-nls turns of usage of `gettext', but in Guile we still need to
be able to represent all codepoints and convert between them and many
encodings, which is an independent facility. Disabling `gettext'
doesn't affect Guile's need for libiconv.
Regards,
Andy
prev parent reply other threads:[~2016-06-22 19:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-13 9:50 bug#19365: [guile-2.0.11] libunistring with iconv required even if specify --disable-nls Kiyoshi KANAZAWA
2014-12-13 13:32 ` John Darrington
2014-12-13 14:16 ` Kiyoshi KANAZAWA
2014-12-13 15:31 ` Ludovic Courtès
2014-12-13 23:19 ` Kiyoshi KANAZAWA
2014-12-13 22:38 ` Kiyoshi KANAZAWA
2016-06-22 19:17 ` Andy Wingo [this message]
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=87lh1xrq1v.fsf@pobox.com \
--to=wingo@pobox.com \
--cc=19365-done@debbugs.gnu.org \
--cc=yoi_no_myoujou@yahoo.co.jp \
/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).