retitle 630376 cpu: package FTBFS if automake1.7 is installed
David Adam wrote:
On Mon, 19 Sep 2011, peter green wrote:
I have just tested this and I can't reproduce the issue in any of the
following environments
1: my dirty squeeze chroot
2: my dirty wheezy chroot
3: my dirty sid chroot
4: my fairly clean sid pbuiler
Could you provide more information on the environment in which you encounted
this bug. In particular what combination of autotools (autoconf, automake,
autoheader etc) were installed?
autoconf 2.67-2
automake 1:1.11.1-1
automake1.7 1.7.9-9.1
automake1.9 1.9.6+nogfdl-3.1
Interestingly if I build on a machine that does not have the automake1.7
package installed things seem to go fine.
Mmm, autotools has this "feature" of doing automatic regeneration if it
finds the tools to do it but skipping the autoregeneration if it can't
find the tools. Leading to a situation where the package builds fine if
the relavent autotool is not installed but fails if the tool is installed.
I've just confirmed that the trigger is having automake1.7 installed and
the issue impacts squeeze wheezy and sid.
Afaict the simplest and lowst risk fix would be to declare a
build-conflict on automake1.7 . Other fixes may include regenerating all
the autotools stuff or somehow patching it to prevent autoregeneration.
Thanks for investigating,
Note that i'm just doing flyby rc bug investigation, I don't have any
relationship to this package
David Adam
[email protected]
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
