[php-maint] Bug#527004: remctl: FTBFS: LTOPTIONS_VERSION is m4_require'd but not m4_defun'd

[Russ Allbery]

This appears to be php5-dev breakage as near as I can tell.  It looks
like phpize is only copying over libtool.m4 and not all of the other
supporting libtool M4 files as required for the libtool 2.x.

I've reassigned the bug to php5-dev.

Kurt Roeckx <kurt at roeckx.be> writes:

> Source: remctl
> Version: 2.13-3
> Severity: serious

> There was an error while trying to autobuild your package:
>
>> Start Time: 20090504-2100
>
> [...]
>
>> Build-Depends: debhelper (>= 5.0.61), dpkg-dev (>= 1.14.9), libkrb5-dev, libtest-pod-perl, php5-dev, python-all-dev, python-support (>= 0.6)
>
> [...]
>
>> Toolchain package versions: libc6-dev_2.9-9 linux-libc-dev_2.6.29-3 g++-4.3_4.3.3-8 gcc-4.3_4.3.3-8 binutils_2.19.1-1 libstdc++6_4.4.0-3 libstdc++6-4.3-dev_4.3.3-8
>> 
>
> [...]
>
>> cd php && /usr/bin/phpize --clean && /usr/bin/phpize
>> Cleaning..
>> Configuring for:
>> PHP Api Version:         20041225
>> Zend Module Api No:      20060613
>> Zend Extension Api No:   220060519
>> configure.in:144: warning: LTOPTIONS_VERSION is m4_require'd but not m4_defun'd
>> aclocal.m4:2921: LT_INIT is expanded from...
>> aclocal.m4:2956: AC_PROG_LIBTOOL is expanded from...
>> configure.in:144: the top level
>> configure.in:144: warning: LTSUGAR_VERSION is m4_require'd but not m4_defun'd
>> configure.in:144: warning: LTVERSION_VERSION is m4_require'd but not m4_defun'd
>> configure.in:144: warning: LTOBSOLETE_VERSION is m4_require'd but not m4_defun'd
>> configure:5079: error: possibly undefined macro: m4_ifval
>>       If this token and others are legitimate, please use m4_pattern_allow.
>>       See the Autoconf documentation.
>> configure:7939: error: possibly undefined macro: _LT_SET_OPTIONS
>> configure:7939: error: possibly undefined macro: LT_INIT

LTOPTIONS_VERSION is in ltoptions.m4, not libtool.m4.  You'll need to
copy over all of ltoptions.m4, ltsugar.m4, ltversion.m4, and
lt~obsolete.m4 as well as libtool.m4.

The m4_ifval error may be more serious; I'm not sure what's going on
with that.

-- 
Russ Allbery (rra at debian.org)               <http://www.eyrie.org/~eagle/>