Comment 12 for bug 271919

On Fri, 2008-10-03 at 15:55 +0000, Mariuz wrote:
> On debian box the build went without problems (experimental one) and it
> produces the right binaries (debs)
>
> I test now the build for hardy and configure part it works also the
> compiling
>
> So it must be something only related to intrepid libtool/autoconf
> changes in intrepid

Hi,

This is probably due to the fact that we have a new libtool in Intrepid.

autogen.sh does this:

# Generate configure from configure.in
echo "Running libtoolize ..."
LIBTOOL_M4=`$LIBTOOLIZE --copy --force --dry-run|grep 'You should add the contents of'|sed "s,^[^/]*\(/[^']*\).*$,\1,"`
if test "x$LIBTOOL_M4" != "x"; then
 rm -f aclocal.m4
 cp $LIBTOOL_M4 aclocal.m4
fi
$LIBTOOLIZE --copy --force || exit 1

so it expects the libtoolize to tell it from where to retrieve
libtool.m4.

However, the output it gets is

cp: target `aclocal.m4' is not a directory
libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, `builds/make.new/config'.
libtoolize: copying file `builds/make.new/config/ltmain.sh'
libtoolize: You should add the contents of the following files to `aclocal.m4':
libtoolize: `/usr/share/aclocal/libtool.m4'
libtoolize: `/usr/share/aclocal/ltoptions.m4'
libtoolize: `/usr/share/aclocal/ltversion.m4'
libtoolize: `/usr/share/aclocal/ltsugar.m4'
libtoolize: `/usr/share/aclocal/lt~obsolete.m4'
libtoolize: Consider adding `AC_CONFIG_MACRO_DIR([m4])' to configure.in and
libtoolize: rerunning libtoolize, to keep the correct libtool macros in-tree.
libtoolize: Consider adding `-I m4' to ACLOCAL_AMFLAGS in Makefile.am.

so it gets a list of files and tries to do the wrong thing with the
different line that it gets.

I think this indicates a broken assumption about the output of libtool.
I don't know enough to make libtool and autotools do the right thing
without needing this hack though.

Thanks,

James