Bug#329333: FTBFS on i386
On Sat, 01 Oct 2005 13:14:50 -0700 Ben Pfaff [EMAIL PROTECTED] wrote: Could you please provide complete build logs for Autoconf with and without automake1.8 installed? I have a feeling that something early in the build is different from what I'm getting here. I attached the logs. BTW: I had the opportunity now to test this on another system, but I couldn't reproduce it there. Regards, Henry build-with-am1.8.log.gz Description: Binary data build-without-am1.8.log.gz Description: Binary data config-with-am1.8.log.gz Description: Binary data config-without-am1.8.log.gz Description: Binary data
Bug#329333: FTBFS on i386
Henry Jensen [EMAIL PROTECTED] writes: After removing and purging automake1.8 it builds. Maybe a Build-Conflicts: automake1.8 would help? If it comes down to that, I can do it, but it doesn't make much sense. automake1.8 only installs a few binaries, none of which the autoconf makefile runs directly, and it shouldn't be running them via alternatives either. I don't understand why it would break anything, and I especially don't understand why it would only break it on your system. Could you please provide complete build logs for Autoconf with and without automake1.8 installed? I have a feeling that something early in the build is different from what I'm getting here. -- Long noun chains don't automatically imply security. --Bruce Schneier -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#329333: FTBFS on i386
Henry Jensen [EMAIL PROTECTED] writes: Well, I tracked it down. The problem was, that I had automake1.8 installed. (and automake1.4 and automake 1.7). Once I purged and removed automake1.8 the package builds fine. I thought the problem would be obvious with some testing, once you pointed that out, but it wasn't. Still, I came up with something that might fix the problem. Could you please try building autoconf_2.95a-5 that I've uploaded temporarily to here: http://footstool.stanford.edu/~blp/ Thanks, Ben. -- To prepare for the writing of Software, the writer must first become one with it, sometimes two. --W. C. Carlson -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#329333: FTBFS on i386
Hi, On Mon, 26 Sep 2005 22:27:01 -0700 Ben Pfaff [EMAIL PROTECTED] wrote: I thought the problem would be obvious with some testing, once you pointed that out, but it wasn't. Still, I came up with something that might fix the problem. Could you please try building autoconf_2.95a-5 that I've uploaded temporarily to here: http://footstool.stanford.edu/~blp/ Sorry, same error again: [...] Making all in bin make[2]: Entering directory `/source-etch/autoconf-2.59a/bin' rm -f autom4te autom4te.tmp sed -e 's,@SHELL\@,/bin/sh,g' -e 's,@PERL\@,/usr/bin/perl,g' -e 's,@bindir\@,/usr/bin,g' -e 's,@datadir\@,/usr/share/autoconf,g' -e 's,@prefix\@,/usr,g' -e 's,@autoconf-name\@,'`echo autoconf | sed 's,x,x,'`',g' -e 's,@autoheader-name\@,'`echo autoheader | sed 's,x,x,'`',g' -e 's,@autom4te-name\@,'`echo autom4te | sed 's,x,x,'`',g' -e 's,@M4\@,/usr/bin/m4,g' -e 's,@AWK\@,gawk,g' -e 's,@VERSION\@,2.59,g' -e 's,@PACKAGE_NAME\@,GNU Autoconf,g' -e 's,@configure_input\@,Generated from autom4te.in; do not edit by hand.,g' ./autom4te.in autom4te.tmp chmod +x autom4te.tmp chmod -w autom4te.tmp mv -f autom4te.tmp autom4te ../tests/autom4te --language M4sh --cache '' ./autoconf.as -o autoconf.in autom4te: cannot open /source-etch/autoconf-2.59a/tests/.././lib/autom4te.cfg: No such file or directory make[2]: *** [autoconf.in] Error 1 make[2]: Leaving directory `/source-etch/autoconf-2.59a/bin' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/source-etch/autoconf-2.59a' make: *** [build-stamp] Error 2 dpkg -l|grep automake ii automake1.71.7.9-7 A tool for generating GNU Standards-complian ii automake1.81.8.5-3 A tool for generating GNU Standards-complian ii automake1.91.9.5-1 A tool for generating GNU Standards-complian After removing and purging automake1.8 it builds. Maybe a Build-Conflicts: automake1.8 would help? Regards, Henry -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#329333: FTBFS on i386
On Thu, 22 Sep 2005 11:57:37 -0700 Ben Pfaff [EMAIL PROTECTED] wrote: What kind of environment are you using for the build? I cannot reproduce your problem either on a native system or using pbuilder? Well, I tracked it down. The problem was, that I had automake1.8 installed. (and automake1.4 and automake 1.7). Once I purged and removed automake1.8 the package builds fine. Regards, Henry -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#329333: FTBFS on i386
Henry Jensen [EMAIL PROTECTED] writes: On Thu, 22 Sep 2005 11:57:37 -0700 Ben Pfaff [EMAIL PROTECTED] wrote: What kind of environment are you using for the build? I cannot reproduce your problem either on a native system or using pbuilder? Well, I tracked it down. The problem was, that I had automake1.8 installed. (and automake1.4 and automake 1.7). Once I purged and removed automake1.8 the package builds fine. That's curious. I'll find out what's going on with automake. Thanks for figuring this out! -- Ben Pfaff email: [EMAIL PROTECTED] web: http://benpfaff.org -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#329333: FTBFS on i386
Henry Jensen [EMAIL PROTECTED] writes: Well, I can only compare the builds of 2.59a-3 and 2.59a-4. What kind of environment are you using for the build? I cannot reproduce your problem either on a native system or using pbuilder? Can you reproduce the problem with pbuilder (or another isolated package build environment)? -- ...dans ce pays-ci il est bon de tuer de temps en temps un amiral pour encourager les autres. --Voltaire, _Candide_ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#329333: FTBFS on i386
Package: autoconf Version: 2.59a-4 Severity: important Justification: renders package unusable autoconf 2.59a-4 doesn't build from source. I'm using gcc 3.3.5. autoconf 2.59a-3 builds fine. It fails like this: [...] dh_testdir make make[1]: Entering directory `/source-etch/autoconf-2.59a' Making all in bin make[2]: Entering directory `/source-etch/autoconf-2.59a/bin' rm -f autom4te autom4te.tmp sed -e 's,@SHELL\@,/bin/sh,g' -e 's,@PERL\@,/usr/bin/perl,g' -e 's,@bindir\@,/usr/bin,g' -e 's,@datadir\@,/usr/share/autoconf,g' -e 's,@prefix\@,/usr,g' -e 's,@autoconf-name\@,'`echo autoconf | sed 's,x,x,'`',g' -e 's,@autoheader-name\@,'`echo autoheader | sed 's,x,x,'`',g' -e 's,@autom4te-name\@,'`echo autom4te | sed 's,x,x,'`',g' -e 's,@M4\@,/usr/bin/m4,g' -e 's,@AWK\@,awk,g' -e 's,@VERSION\@,2.59,g' -e 's,@PACKAGE_NAME\@,GNU Autoconf,g' -e 's,@configure_input\@,Generated from autom4te.in; do not edit by hand.,g' ./autom4te.in autom4te.tmp chmod +x autom4te.tmp chmod -w autom4te.tmp mv -f autom4te.tmp autom4te ../tests/autom4te --language M4sh --cache '' ./autoconf.as -o autoconf.in autom4te: cannot open /source-etch/autoconf-2.59a/tests/.././lib/autom4te.cfg: No such file or directory make[2]: *** [autoconf.in] Error 1 make[2]: Leaving directory `/source-etch/autoconf-2.59a/bin' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/source-etch/autoconf-2.59a' make: *** [build-stamp] Error 2 Regards, Henry -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#329333: FTBFS on i386
Henry Jensen [EMAIL PROTECTED] writes: Package: autoconf Version: 2.59a-4 Severity: important Justification: renders package unusable autoconf 2.59a-4 doesn't build from source. I'm using gcc 3.3.5. autoconf 2.59a-3 builds fine. I can't reproduce your problem on either of my machines. Can you please try to track it down yourself? -- Ben Pfaff email: [EMAIL PROTECTED] web: http://benpfaff.org -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#329333: FTBFS on i386
Well, I can only compare the builds of 2.59a-3 and 2.59a-4.
2.59a-3:
[...]
dh_testdir
make
make[1]: Entering directory `/source-orig/autoconf-2.59a'
Making all in bin
make[2]: Entering directory `/source-orig/autoconf-2.59a/bin'
rm -f autom4te autom4te.tmp
sed -e 's,@SHELL\@,/bin/sh,g' -e 's,@PERL\@,/usr/bin/perl,g' -e
's,@bindir\@,/usr/bin,g' -e 's,@datadir\@,/usr/share/autoconf,g' -e
's,@prefix\@,/usr,g' -e 's,@autoconf-name\@,'`echo autoconf | sed 's,x,x,'`',g'
-e 's,@autoheader-name\@,'`echo autoheader | sed 's,x,x,'`',g' -e
's,@autom4te-name\@,'`echo autom4te | sed 's,x,x,'`',g' -e
's,@M4\@,/usr/bin/m4,g' -e 's,@AWK\@,awk,g' -e 's,@VERSION\@,2.59,g' -e
's,@PACKAGE_NAME\@,GNU Autoconf,g' -e 's,@configure_input\@,Generated from
autom4te.in; do not edit by hand.,g' ./autom4te.in autom4te.tmp
chmod +x autom4te.tmp
chmod -w autom4te.tmp
mv -f autom4te.tmp autom4te
rm -f autoconf autoconf.tmp
[...]
2.59a-4:
dh_testdir
make
make[1]: Entering directory `/source-etch/autoconf-2.59a'
Making all in bin
make[2]: Entering directory `/source-etch/autoconf-2.59a/bin'
rm -f autom4te autom4te.tmp
sed -e 's,@SHELL\@,/bin/sh,g' -e 's,@PERL\@,/usr/bin/perl,g' -e
's,@bindir\@,/usr/bin,g' -e 's,@datadir\@,/usr/share/autoconf,g' -e
's,@prefix\@,/usr,g' -e 's,@autoconf-name\@,'`echo autoconf | sed 's,x,x,'`',g'
-e 's,@autoheader-name\@,'`echo autoheader | sed 's,x,x,'`',g' -e
's,@autom4te-name\@,'`echo autom4te | sed 's,x,x,'`',g' -e
's,@M4\@,/usr/bin/m4,g' -e 's,@AWK\@,awk,g' -e 's,@VERSION\@,2.59,g' -e
's,@PACKAGE_NAME\@,GNU Autoconf,g' -e 's,@configure_input\@,Generated from
autom4te.in; do not edit by hand.,g' ./autom4te.in autom4te.tmp
chmod +x autom4te.tmp
chmod -w autom4te.tmp
mv -f autom4te.tmp autom4te
../tests/autom4te --language M4sh --cache '' ./autoconf.as -o autoconf.in
autom4te: cannot open /source-etch/autoconf-2.59a/tests/.././lib/autom4te.cfg:
No such file or directory
Obviuosly something changed between 2.59a-3 and -4.
After mv -f autom4te.tmp autom4te the command
../tests/autom4te --language M4sh --cache '' ./autoconf.as -o autoconf.in
occur, which complains about not finding
autoconf-2.59a/tests/.././lib/autom4te.cfg. This doesn't happen in 2.59a-3.
A diff of the two configure scripts give me this:
@@ -2910,11 +2910,6 @@
*) ac_INSTALL=$ac_top_builddir$INSTALL ;;
esac
- if test x$ac_file != x-; then
-{ echo $as_me:$LINENO: creating $ac_file 5
-echo $as_me: creating $ac_file 6;}
-rm -f $ac_file
- fi
# Let's still pretend it is `configure' which instantiates (i.e., don't
# use $as_me), people would be surprised to read:
#/* config.h. Generated by config.status. */
@@ -2953,6 +2948,12 @@
fi;;
esac
done` || { (exit 1); exit 1; }
+
+ if test x$ac_file != x-; then
+{ echo $as_me:$LINENO: creating $ac_file 5
+echo $as_me: creating $ac_file 6;}
+rm -f $ac_file
+ fi
_ACEOF
cat $CONFIG_STATUS _ACEOF
I would suspect that this change had some strange side effect.
Regards,
Henry
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
