[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [PATCH] gettext: update macros to version 0.19

From: Pádraig Brady
Subject: Re: [PATCH] gettext: update macros to version 0.19
Date: Thu, 10 Jul 2014 00:26:43 +0100
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130110 Thunderbird/17.0.2

On 07/09/2014 11:52 PM, Daiki Ueno wrote:
> Pádraig Brady <address@hidden> writes:
>>   make[2]: Entering directory `/home/padraig/git/coreutils/po'
>>   *** error: gettext infrastructure mismatch: using a Makefile.in.in from 
>> gettext version 0.18 but the autoconf macros are from gettext version 0.19
>>   make[2]: *** [check-macro-version] Error 1
>> I can easily update gettext and can confirm 0.19 works as expected.
>> Other have often expressed disdain for non readily available
>> distro requiremnts like this. Should we consider reverting
>> this until gettext-0.19 packages are easily available?
> I feel it rather strange that bootstrap replaces m4/po.m4, already
> pulled by autopoint.  As coreutils explicitly specifies the gettext
> infrastructure version as 'AM_GNU_GETTEXT_VERSION([0.18.1])' in
> configure.ac, IMO it should still be able to use the 0.18.1 macros even
> after running bootstrap.
> The file replacement happens because of some Gnulib tests depending on
> the gettext module.  How about removing the dependencies?

Thanks a lot for looking at this!
It wasn't obvious to me why the change mandated a matching version in coreutils.

I'm not sure that removing the gettext dependencies is OK because
they're used to provide @LIB_INTL@ which was added to support solaris 2.[67]
Now these dependencies are not ideal at all, and it would be great
to avoid them otherwise, especially as introduced only to support
this older platform, and only for tests at that.
Teasing out these dependencies is always worth doing as an on going effort
lest one end up with a hairball amalgamating everything.

Now that I have an idea what's going on though, this shouldn't be
a blocking issue for coreutils at least.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]