2009/12/1 Cyril Brulebois <k...@debian.org>:
> Jonas Smedegaard <d...@jones.dk> (01/12/2009):
>> My builds using cowdancer+pbuilder on amd64 and i386 with a fully
>> up-to-date Sid shows no such things.
>
> Note I'm talking about porter boxes, so a bit more than just chroot +
> Build-Depends.
>
>> Perhaps some environment variables makes cdbs or libtool choke, or
>> some old version of libtool makes netatalk choke. Could you please
>> tell more about the build environment (e.g. versions of installed
>> packages and environment variables set), to shed some light on what
>> is going on here?
>
> I've cleaned up all autotools packages and only installed those that
> the build system tries to use (as seen in the build log):
>
> $ dpkg -l 'autoconf*' 'automake*' libtool|grep ^ii|awk '{print $2 "/" $3}'
> autoconf/2.65-2
> automake1.10/1:1.10.2-2
> libtool/2.2.6a-4You're (well not you, the Debian build infrastructure) messing up the autotools environment. Netatalk 2.0.5 comes with: $ ./libtool --version ltmain.sh (GNU libtool) 1.5.22 Debian 1.5.22-4 (1.1220.2.365 2005/12/18 22:14:06) Copyright (C) 2005 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. So if you want to regenerate, do so completely eg run `libtoolize --force --copy` and maybe also `automake --include-deps --add-missing --foreign --copy`. The alternative is to stay away from configure.in and Makefile.am. -Frank -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
