Re: check4.test consistently failing
Hello Philipp, * Philipp Thomas wrote on Wed, Apr 29, 2009 at 03:05:04PM CEST: * Ralf Wildenhues [20090428 22:42]: Note that you can rerun this one test only with either cd tests make check VERBOSE=yes TESTS=check4.test I figured that out myself :) I'll do the test and will report. BTW, you can see the logs for yourself in the openSUSE buildservice. Just go to https://build.opensuse.org/package/show?package=automakeproject=openSUSE%3AFactory and choose a log of any of the failing builds. That just is an interesting statement. I had to create an account with Novell, then had to click through more pages. I find the buildservice quite complex at first, not knowing where the actual logs would be. Anyway, found at least one log with one failing test, but it was check10.test not check4.test. You need to search for ^FAIL:.*\.test$ to avoid being tricked by testsuite runs inside of testsuite runs. Automake 1.11 logs will be easier to analyze (I hope). The specific failure I found was due to /bin/sh being a ksh variant, and fixed with this post-1.10.2 patch. commit 319305db77dfdcbba3d5a1703c781750affdb20a Author: Ralf Wildenhues ralf.wildenh...@gmx.de Date: Wed Nov 12 07:07:31 2008 +0100 Testsuite fix for ksh. * tests/check10.test: Add ':' as last command in subshell, for zero exit status of the subshell. Missing backport from master reported by Tim Rice. Second, do you have a testcase that shows what the require_file_internal patch is required for? See https://bugzilla.novell.com/show_bug.cgi?id=64822 Even with an account, I am not allowed to see this. Wonder what kind of policy is behind that. The problem AFAICS from the sources of patchutils 0.2.30 was that configure.in had Can you please send a full bug report containing all necessary information from above PR to bug-automake, including a reproducible test case, in a separate thread? Thanks. Cheers, Ralf
Script configure failed unexpectedly
This file contains any messages produced by compilers while
running configure, to aid debugging if configure makes a mistake.
It was created by GNU Automake configure 1.10.1, which was
generated by GNU Autoconf 2.61. Invocation command line was
$ ./configure --program-suffix=-1.10 --prefix=/usr/local
--mandir=/usr/local/man --infodir=/usr/local/info/
--build=i386-portbld-freebsd6.1
## - ##
## Platform. ##
## - ##
hostname = vpn1.postmet.com
uname -m = i386
uname -r = 6.1-RELEASE
uname -s = FreeBSD
uname -v = FreeBSD 6.1-RELEASE #1: Mon Feb 26 16:52:43 PST 2007
r...@12699-29928:/usr/src/sys/i386/compile/customekernel
/usr/bin/uname -p = i386
/bin/uname -X = unknown
/bin/arch = unknown
/usr/bin/arch -k = unknown
/usr/convex/getsysinfo = unknown
/usr/bin/hostinfo = unknown
/bin/machine = unknown
/usr/bin/oslevel = unknown
/bin/universe = unknown
PATH: /sbin
PATH: /usr/sbin
PATH: /bin
PATH: /usr/bin
PATH: /usr/local/sbin
PATH: /usr/local/bin
PATH: /usr/X11R6/bin
## --- ##
## Core tests. ##
## --- ##
configure:1704: checking build system type
configure:1722: result: i386-portbld-freebsd6.1
configure:1766: checking for a BSD-compatible install
configure:1822: result: /usr/bin/install -c -o root -g wheel
configure:1833: checking whether build environment is sane
configure:1876: result: yes
configure:1904: checking for a thread-safe mkdir -p
configure:1943: result: /usr/local/bin/gmkdir -p
configure:1956: checking for gawk
configure:1972: found /usr/local/bin/gawk
configure:1983: result: gawk
configure:1994: checking whether make sets $(MAKE)
configure:2015: result: yes
configure:2225: checking for perl
configure:2243: found /usr/local/bin/perl
configure:2255: result: /usr/local/bin/perl
configure:2283: checking for tex
configure:2313: result: no
configure:2325: checking whether autoconf is installed
configure:2330: eval /usr/local/bin/autoconf-2.62 --version
autoconf (GNU Autoconf) 2.62
Copyright (C) 2008 Free Software Foundation, Inc.
License GPLv2+: GNU GPL version 2 or later
http://gnu.org/licenses/old-licenses/gpl-2.0.html
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Written by David J. MacKenzie and Akim Demaille.
configure:2333: $? = 0
configure:2341: result: yes
configure:2351: checking whether autoconf works
configure:2358: cd conftest eval /usr/local/bin/autoconf-2.62 -o
/dev/null conftest.ac
exec: /usr/local/bin/autom4te-2.62: not found
configure:2361: $? = 127
configure:2370: result: no
configure:2373: error: The installed version of autoconf does not work.
Please check config.log for error messages before this one.
## ##
## Cache variables. ##
## ##
ac_cv_build=i386-portbld-freebsd6.1
ac_cv_env_build_alias_set=set
ac_cv_env_build_alias_value=i386-portbld-freebsd6.1
ac_cv_env_host_alias_set=''
ac_cv_env_host_alias_value=''
ac_cv_env_target_alias_set=''
ac_cv_env_target_alias_value=''
ac_cv_path_PERL=/usr/local/bin/perl
ac_cv_path_mkdir=/usr/local/bin/gmkdir
ac_cv_prog_AWK=gawk
ac_cv_prog_make_make_set=yes
am_cv_autoconf_installed=yes
am_cv_autoconf_works=no
lt_cv_sys_max_cmd_len=262144
## - ##
## Output variables. ##
## - ##
ACLOCAL='perllibdir=/usr/ports/devel/automake110/work/automake-1.10.1/lib:./lib
/usr/ports/devel/automake110/work/automake-1.10.1/aclocal --acdir=m4 -I m4'
AMTAR='${SHELL}
/usr/ports/devel/automake110/work/automake-1.10.1/lib/missing --run tar'
APIVERSION='1.10'
AUTOCONF='/usr/local/bin/autoconf-2.62'
AUTOHEADER='/usr/local/bin/autoheader-2.62'
AUTOMAKE='perllibdir=/usr/ports/devel/automake110/work/automake-1.10.1/lib:./lib
/usr/ports/devel/automake110/work/automake-1.10.1/automake --libdir=lib'
AWK='gawk'
CYGPATH_W='echo'
DEFS=''
ECHO_C=''
ECHO_N='-n'
ECHO_T=''
EGREP=''
FGREP=''
GREP=''
INSTALL_DATA='install -o root -g wheel -m 444'
INSTALL_PROGRAM='install -s -o root -g wheel -m 555'
INSTALL_SCRIPT='install -o root -g wheel -m 555'
INSTALL_STRIP_PROGRAM='$(install_sh) -c -s'
LIBOBJS=''
LIBS=''
LN=''
LTLIBOBJS=''
MAKEINFO='makeinfo --no-split'
MODIFICATION_DELAY=''
PACKAGE='automake'
PACKAGE_BUGREPORT='bug-automake@gnu.org'
PACKAGE_NAME='GNU Automake'
PACKAGE_STRING='GNU Automake 1.10.1'
PACKAGE_TARNAME='automake'
PACKAGE_VERSION='1.10.1'
PATH_SEPARATOR=':'
PERL='/usr/local/bin/perl'
SET_MAKE=''
SHELL='/bin/sh'
STRIP=''
TEX=''
VERSION='1.10.1'
am_AUTOCONF='/usr/local/bin/autoconf-2.62'
am__isrc=''
am__leading_dot='.'
am__tar='${AMTAR} chof - $$tardir'
am__untar='${AMTAR} xf -'
bindir='${exec_prefix}/bin'
build='i386-portbld-freebsd6.1'
build_alias='i386-portbld-freebsd6.1'
build_cpu='i386'
build_os='freebsd6.1'
build_vendor='portbld'
datadir='${datarootdir}'
Re: Script configure failed unexpectedly
Hello Alexander, thanks for the report. * Alexander Kozyrev wrote on Wed, Apr 29, 2009 at 11:22:46PM CEST: It was created by GNU Automake configure 1.10.1, which was generated by GNU Autoconf 2.61. Invocation command line was $ ./configure --program-suffix=-1.10 --prefix=/usr/local --mandir=/usr/local/man --infodir=/usr/local/info/ --build=i386-portbld-freebsd6.1 [...] configure:1704: checking build system type configure:1722: result: i386-portbld-freebsd6.1 [...] configure:2325: checking whether autoconf is installed configure:2330: eval /usr/local/bin/autoconf-2.62 --version autoconf (GNU Autoconf) 2.62 configure:2333: $? = 0 configure:2341: result: yes configure:2351: checking whether autoconf works configure:2358: cd conftest eval /usr/local/bin/autoconf-2.62 -o /dev/null conftest.ac exec: /usr/local/bin/autom4te-2.62: not found So, where is autom4te-2.62, and why was it not installed alongside autoconf-2.62? Looks like a ports packaging issue to me. Cheers, Ralf
Re: script timestamps
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Ralf Wildenhues on 4/28/2009 11:36 PM: To make sure I understand the branching rules correctly, I would simply apply this first to origin/branch-1-10, then merge that onto origin/master? No. branch-1-10 was started before the move to git, and I never fake-merged the common parts of it and master. Please commit to master, then cherry-pick into branch-1-10. I've just pushed a couple of pending cherry-picks in branch-1-10. OK, done. - -- Don't work too hard, make some time for fun as well! Eric Blake e...@byu.net -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Cygwin) Comment: Public key at home.comcast.net/~ericblake/eblake.gpg Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkn4QnwACgkQ84KuGfSFAYCnVQCZAUdWEo7AELN3e7ij3TcXgBgD itIAoJwy3jnuU6/F67mPhmKONdBeqabJ =uJm8 -END PGP SIGNATURE-
noinst_TEXINFOS
Hi List! Could it be that a primary noinst_TEXINFOS does not work with automake 1.10.2? I tried to use it in my project but nothin gets build on make. greetings, Stefan
Re: noinst_TEXINFOS
Stefan Bienert bien...@zbh.uni-hamburg.de writes: Could it be that a primary noinst_TEXINFOS does not work with automake 1.10.2? This seems likely. I reported the same problem some time ago: http://permalink.gmane.org/gmane.comp.sysutils.automake.bugs/4046 My report did not receive any replies. -- Ben Pfaff http://benpfaff.org
Re: noinst_TEXINFOS
On 4/29/2009 5:27 PM, Ben Pfaff wrote: Stefan Bienertbien...@zbh.uni-hamburg.de writes: Could it be that a primary noinst_TEXINFOS does not work with automake 1.10.2? This seems likely. I reported the same problem some time ago: http://permalink.gmane.org/gmane.comp.sysutils.automake.bugs/4046 My report did not receive any replies. I believe this should work, there's no reason for it not to that I can think of, but I'm wondering: Why would you create texinfos, and then not install them? This is probably how the bug got there - it's not a very likely use case, is it? John
Re: noinst_TEXINFOS
Hello, * John Calcote wrote on Thu, Apr 30, 2009 at 01:54:17AM CEST: On 4/29/2009 5:27 PM, Ben Pfaff wrote: Stefan Bienertbien...@zbh.uni-hamburg.de writes: Could it be that a primary noinst_TEXINFOS does not work with automake 1.10.2? Yes; neither with git master. This seems likely. I reported the same problem some time ago: http://permalink.gmane.org/gmane.comp.sysutils.automake.bugs/4046 My report did not receive any replies. Sorry. I haven't forgotten the issue, although I forgot to reply. I believe this should work, there's no reason for it not to that I can think of, It doesn't work, never did IIRC. There are a few issues that could use a rework around TEXINFOS handling. Maybe a good post-1.11 project, but nothing I have time to start before. If anyone wants to work on it, I can list a few of the complications involved. Cheers, Ralf
