From: "Torsten Bögershausen" <tboegi@web.de>
To: Junio C Hamano <gitster@pobox.com>
Cc: "Torsten Bögershausen" <tboegi@web.de>,
"Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
git@vger.kernel.org
Subject: Re: Re*: [PATCH/RFC] Change t0204-gettext-reencode-sanity.sh to pass under Mac OSX
Date: Sun, 11 Mar 2012 22:10:37 +0100 [thread overview]
Message-ID: <4F5D14CD.6080507@web.de> (raw)
In-Reply-To: <7vzkbnvt6m.fsf@alter.siamese.dyndns.org>
On 03/11/2012 08:22 PM, Junio C Hamano wrote:
> Torsten Bögershausen<tboegi@web.de> writes:
>
>> Here the results of my investigations:
>> a) git-sh-i18n is used by the test suite, not git-sh-i18n.sh
>> git-sh-i18n is generated from git-sh-i18n.sh when running make
>
> Yeah, that is the correct behaviour.
>
>> b) When running
>> make clean&& make USE_GETTEXT_SCHEME=gnu&& (cd t&& make)
>> the log of t0204 looks like this:
>> ...
>> Summary: test OK,
>
> Now, the last remaining issues appear to be these:
>
> * Is USE_GETTEXT_SCHEME=gnu the right thing for Mac OS X? It may
> make this test pass, but does it not break other things? Does
> Mac OS X come with a working gettext.sh to help i18n of shell
> scripts? Does it also give eval_gettext?
When I remember it right, the following comes from the Fink installation
on my machine:
which gettext
/sw/bin/gettext
which gettext.sh
/sw/bin/gettext.sh
None of the machines here (Mac OS X, Ubuntu 10.04.4 LTS, OpenSuse 12.1)
has a eval_gettext
> * If so, Mac OS X users shouldn't have to say that from the command
> line of "make". Do we need a Makefile update?
Good question.
I couldn't find any setup of USE_GETTEXT_SCHEME in Makefile
(except when NO_GETTEXT is set), do I need to run configure?
So far the Makefile worked for all my systems here.
>
> * If not, what is the appropriate value for USE_GETTEXT_SCHEME on=
> Mac OS X? If the answer is not "fallthrough", do we need a
> Makefile update?
My guess is that "gettext_without_eval_gettext" would be right
(if we have Fink installed)
But again, what did I overlook in the Makefile?
Should there be some hard coded default for e.g. Darwin?
With a switch when Fink is installed?
next prev parent reply other threads:[~2012-03-11 21:10 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-05 19:39 [PATCH/RFC] Change t0204-gettext-reencode-sanity.sh to pass under Mac OSX Torsten Bögershausen
2012-03-05 20:39 ` Junio C Hamano
2012-03-07 21:03 ` Ævar Arnfjörð Bjarmason
2012-03-07 21:34 ` Junio C Hamano
2012-03-07 21:43 ` Ævar Arnfjörð Bjarmason
2012-03-07 21:58 ` Junio C Hamano
2012-03-07 22:04 ` Ævar Arnfjörð Bjarmason
2012-03-07 23:36 ` Junio C Hamano
2012-03-07 23:42 ` Junio C Hamano
2012-03-08 5:54 ` Torsten Bögershausen
2012-03-08 7:23 ` Johannes Sixt
2012-03-08 9:21 ` Torsten Bögershausen
2012-03-08 12:07 ` Torsten Bögershausen
2012-03-09 22:30 ` Re*: " Junio C Hamano
2012-03-10 22:28 ` Torsten Bögershausen
2012-03-11 6:36 ` Junio C Hamano
2012-03-11 15:11 ` Torsten Bögershausen
2012-03-11 19:22 ` Junio C Hamano
2012-03-11 21:10 ` Torsten Bögershausen [this message]
2012-03-11 21:38 ` Junio C Hamano
2012-03-12 20:58 ` Torsten Bögershausen
2012-03-12 21:25 ` Junio C Hamano
2012-03-13 19:19 ` Torsten Bögershausen
2012-03-13 19:32 ` Junio C Hamano
2012-03-12 5:46 ` 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=4F5D14CD.6080507@web.de \
--to=tboegi@web.de \
--cc=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).