Bug#753521: libmatio: FTBFS in new archs. Update libtool.m4

[Breno Leitao]

Package: libmatio
Version: 1.5.2-1
Severity: normal
Tags: patch
User: debian-powerpc at lists.debian.org
Usertags: ppc64el

Dear Maintainer,

The package libmatio does not build on new architecture because the libtool
files is not updated automatically by either autoreconf (just updates the
config files) and the autoreconf is simply calling autogen.sh. 

This makes the unknown architectures to have shared libraries disabled, as happen on ppc64el in the following error:

http://ftp.unicamp.br/pub/ppc64el/debian/buildd-upstream/build_logs/logs/libmatio_1.5.2-1_ppc64el.build

This patch simply update the libtool.m4 file to add support for the new
architectures.  Altough this update solves the problem for now, the prefered
way to solve it is having autoreconf updating those files and then calling
autogen.sh, which is something that I don't know how to do.

Thank you,
Breno


-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: ppc64el (ppc64le)

Kernel: Linux 3.13-1-powerpc64le (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
-------------- next part --------------
A non-text attachment was scrubbed...
Name: libmatio_update_libtool.m4
Type: text/x-diff
Size: 6072 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/debian-science-maintainers/attachments/20140702/db905457/attachment.diff>