From: Junio C Hamano <junkio@cox.net>
To: Jakub Narebski <jnareb@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: What does "properly support iconv" in git Makefile (NO_ICONV) mean?
Date: Mon, 04 Sep 2006 16:31:13 -0700 [thread overview]
Message-ID: <7v4pvnky4e.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <200609050126.56423.jnareb@gmail.com> (Jakub Narebski's message of "Tue, 5 Sep 2006 01:26:56 +0200")
Jakub Narebski <jnareb@gmail.com> writes:
> Gaah, I have some problems accessing the Gentoo bug database.
> Is the problem that iconv does not exist in libc, or it exist but
> misbehaves?
In small configurations that do not care about i18n, it is often
done to give iconv routines that is noop/ident in order to make
the programs compile and run.
next prev parent reply other threads:[~2006-09-04 23:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200609050108.57695.jnareb@gmail.com>
2006-09-04 23:16 ` What does "properly support iconv" in git Makefile (NO_ICONV) mean? Fernando J. Pereda
2006-09-04 23:26 ` Jakub Narebski
2006-09-04 23:31 ` Junio C Hamano [this message]
2006-09-04 23:41 ` Fernando J. Pereda
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7v4pvnky4e.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=jnareb@gmail.com \
/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 NNTP newsgroup(s).