Bug#754146: [bug-gettext] Bug#754146: gettext: fix FTBFS on ppc64el with autoreconf or libtool patch (provided) (fwd)

2014-07-20 Thread Daiki Ueno
Mauricio Faria de Oliveira mauri...@linux.vnet.ibm.com writes:

 Just clarifying for a broader audience:

Thanks for the clarification.

 On Debian, using autoreconf required a change to one upstream file [1]
 because the libtool macros are shipped with 'link_all_libdeps=no'.

 Therefore that patch [2] just added in *_LDADD the missing libdep listed
 in *_DEPENDENCIES (libgettextlib.la), plus libunistring in one case.

 It's reasonable for upstream not to consider it, since it is required
 due to a change downstream.

 So: Would be possible to release a gettext version using latest
 libtool so that I do not need to add any special hack in the Debian
 package? (Or maybe this is not even fixed in libtool yet?)

 This was fixed in libtool (as of [3]), and incorporated in v2.4.2.418.

So, yes, probably we should skip the Makefile.am changes (in upstream).

For the patch to libtool.m4, I'd also like to wait until a new libtool
stable release, but if it takes long time and the change is trivial
enough, I think it could be backported (like [1]).

Footnotes: 
[1]  http://git.savannah.gnu.org/cgit/gettext.git/commit/?id=73acab39


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#754146: gettext: fix FTBFS on ppc64el with autoreconf or libtool patch (provided) (fwd)

2014-07-17 Thread Mauricio Faria de Oliveira

Hi,

On 07/16/2014 09:05 PM, Santiago Vila wrote:

The report included two patches to choose from. One of them is a patch
to the Debian packaging so that it uses autoreconf.


Just clarifying for a broader audience:

On Debian, using autoreconf required a change to one upstream file [1]
because the libtool macros are shipped with 'link_all_libdeps=no'.

Therefore that patch [2] just added in *_LDADD the missing libdep listed
in *_DEPENDENCIES (libgettextlib.la), plus libunistring in one case.

It's reasonable for upstream not to consider it, since it is required
due to a change downstream.


So: Would be possible to release a gettext version using latest
libtool so that I do not need to add any special hack in the Debian
package? (Or maybe this is not even fixed in libtool yet?)


This was fixed in libtool (as of [3]), and incorporated in v2.4.2.418.

Regards,

[1] gettext-tools/src/Makefile.am
[2] http://bugs.debian.org/754146#5
[3] 
http://git.savannah.gnu.org/cgit/libtool.git/commit?id=8a8dfaec78790ab3193c2751b3188925339fdacb


--
Mauricio Faria de Oliveira
IBM Linux Technology Center


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#754146: gettext: fix FTBFS on ppc64el with autoreconf or libtool patch (provided)

2014-07-07 Thread Mauricio Faria de Oliveira

Package: src:gettext
Version: 0.18.3.2-3
Tags: patch
User: debian-powe...@lists.debian.org
Usertags: ppc64el
User: debian-de...@lists.debian.org
Usertags: autoreconf

Hi Santiago,

Either of the attached patches fix a FTBFS on ppc64el due to shared
libraries not being built (due to old libtool.m4/configure script).

Would you please consider one of them for an upload?


One is a simple patch (fixes only ppc64el). The other is a more complete
dh-autoreconf thing (fixes ppc64el and other new arches, but uses dh_,
which AFAICT the package is not using, but does build successfully).

With either of them applied, the contents of the built packages (i.e.,
dpkg-deb -c) are equivalent to those of powerpc packages (i.e., no diff
in file listings, accounting for GNU arch name difference).


Thank you,

--
Mauricio Faria de Oliveira
IBM Linux Technology Center


gettext-autoreconf.debdiff.gz
Description: GNU Zip compressed data


gettext-ppc64el-libtool.debdiff.gz
Description: GNU Zip compressed data