From: Junio C Hamano <gitster@pobox.com>
To: git@vger.kernel.org
Subject: [PATCH/RFC] FreeBSD iconv function signature is "old"
Date: Sat, 26 Dec 2009 01:09:08 -0800 [thread overview]
Message-ID: <7vr5qi6r0r.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: 7v7hxysie9.fsf@alter.siamese.dyndns.org
Junio C Hamano <gitster@pobox.com> writes:
> I noticed that my build on FreeBSD-7.2-RELEASE-i386 fails without
> OLD_ICONV=YesPlease.
>
> Is it just me and my installation (i.e. I might have failed to install
> saner iconv from the port that everybody uses), or is everybody who runs
> on FreeBSD using this option himself because our Makefile doesn't do that
> automatically for them?
>
> Just in case it is the latter, here is a proposed patch.
By the way, FreeBSD-8.0-RELEASE-i386 has the same issue. I'll queue it to
'maint' unless anybody objects...
> Makefile | 1 +
> 1 files changed, 1 insertions(+), 0 deletions(-)
>
> diff --git a/Makefile b/Makefile
> index bde27ed..9a25c08 100644
> --- a/Makefile
> +++ b/Makefile
> @@ -777,6 +777,7 @@ ifeq ($(uname_O),Cygwin)
> endif
> ifeq ($(uname_S),FreeBSD)
> NEEDS_LIBICONV = YesPlease
> + OLD_ICONV = YesPlease
> NO_MEMMEM = YesPlease
> BASIC_CFLAGS += -I/usr/local/include
> BASIC_LDFLAGS += -L/usr/local/lib
next prev parent reply other threads:[~2009-12-26 9:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-24 5:30 [PATCH/RFC] SunOS grep does not understand -C<n> Junio C Hamano
2009-07-24 5:41 ` Jeff King
2009-07-24 6:27 ` Junio C Hamano
2009-07-24 7:09 ` Jeff King
2009-07-24 6:29 ` [PATCH/RFC] FreeBSD iconv function signature is "old" Junio C Hamano
2009-12-26 9:09 ` Junio C Hamano [this message]
2009-07-24 15:43 ` [PATCH/RFC] SunOS grep does not understand -C<n> Brandon Casey
2009-07-24 15:55 ` Junio C Hamano
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=7vr5qi6r0r.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.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 NNTP newsgroup(s).