http://permalink.gmane.org/gmane.comp.sysutils.automake.bugs hourly 1 1901-01-01T00:00+00:00 http://gmane.org/img/gmane-25t.png http://gmane.org http://permalink.gmane.org/gmane.comp.sysutils.automake.bugs/6453 <pre>Hi, aclocal8, acsilent and unused test cases all fail if I have the newly released perl-5.16.0 installed. The error appears to be because of a change in Perl, which now ends up outputting the following to stderr: main::scan_file() called too early to check prototype at /sources/automake-1.12/aclocal line 642. I've attached the logs. If you require any further information, just let me know. Thanks, Matt. </pre> Matt Burgess 2012-05-22T20:34:40 http://permalink.gmane.org/gmane.comp.sysutils.automake.bugs/6452 <pre>Hi! I got two failures on my Ubuntu 12.04 LTS system, see output below. ============================================================================ Testsuite summary for GNU Automake 1.12.0b ============================================================================ # TOTAL: 2921 # PASS: 2781 # SKIP: 96 # XFAIL: 42 # FAIL: 2 # XPASS: 0 # ERROR: 0 FAIL: t/remake8b ================ Running from installcheck: no Using TAP: no PATH = /home/jas/src/automake-1.12.0b/t/ax:/home/jas/src/automake-1.12.0b/t/wrap:/home/jas/bin:/usr/lib/lightdm/lightdm:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/home/jas/bin ++ pwd /home/jas/src/automake-1.12.0b/t/remake8b.dir + mv -f configure.ac configure.stub + cat + cat configure.stub - + aclocal-1.12 -Werror + autoconf + automake-1.12 --foreign -Werror -Wall + mkdir build + cd build + srcdir=.. + ../configure checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for a thread-safe</pre> Simon Josefsson 2012-05-21T12:24:48 http://permalink.gmane.org/gmane.comp.sysutils.automake.bugs/6451 <pre>Hi Stefano, Am 19.05.2012 um 16:17 schrieb Stefano Lattarini: I just tested on Solaris 9 Sparc with Sun Studio 12 and got 170 failed tests as described in the testsuite log: http://buildfarm.opencsw.org/~dam/automake-1.12.0b-test-suite.log Please let me know if you need further information or access to the buildfarm. Best regards -- Dago </pre> Dagobert Michelsen 2012-05-20T09:57:06 http://permalink.gmane.org/gmane.comp.sysutils.automake.bugs/6450 <pre>============================================================================ Testsuite summary for GNU Automake 1.12 ============================================================================ # TOTAL: 2968 # PASS: 2833 # SKIP: 89 # XFAIL: 42 # FAIL: 4 # XPASS: 0 # ERROR: 0 ============================================================================ See ./test-suite.log Please report to bug-automake&lt; at &gt;gnu.org ============================================================================ ./lib/test-driver: line 95: 8767 Segmentation fault "$&lt; at &gt;" &gt; $log_file 2&gt;&amp;1 FAIL: t/pm/Condition-t.pl ./lib/test-driver: line 95: 8815 Segmentation fault "$&lt; at &gt;" &gt; $log_file 2&gt;&amp;1 FAIL: t/pm/DisjConditions-t.pl FAIL: t/cond29.sh FAIL: t/cond29 ============== Running from installcheck: no Using TAP: no PATH = /usr/src/automake-1.12/t/ax:/usr/src/automake-1.12/t/wrap:/usr/local/bin:/usr/bin:/bin:/usr/local/sbin:/usr/sbin:/sbin ++ pwd /usr/src/automake-1.12/t/cond29.dir + echo AC_PROG_CC + cat + ulimit -v 1 + sh -c : </pre> Guido Trentalancia 2012-05-18T18:40:33 http://permalink.gmane.org/gmane.comp.sysutils.automake.bugs/6449 <pre>sön 2012-05-13 klockan 13:24 +0200 skrev Stefano Lattarini: Thank you, the patch you pushed (without the ',' typo) worked fine. /Simon </pre> Simon Josefsson 2012-05-14T09:39:09 http://permalink.gmane.org/gmane.comp.sysutils.automake.bugs/6448 <pre>For what concerns the automake issue: I haven't looked into it yet, and likely I won't anytime soon; it is very very low priority for me. Just fix the broken 'dir' file manually for the moment. Better again, use the HTML documentation instead of the info one. Sorry, Stefano </pre> Stefano Lattarini 2012-05-13T19:30:09 http://permalink.gmane.org/gmane.comp.sysutils.automake.bugs/6447 <pre>Hi Stefano , What is final solution to use texinfo pages for GNU autotools (autoconf,automake,libtool) ? Bruno Haible wrote: [SNIP] [SNIP] info automake-invocation is new stile if remember some discussion about implementation of xxxx-invocation and Xxxx Roumen </pre> Roumen Petrov 2012-05-13T17:21:11 http://permalink.gmane.org/gmane.comp.sysutils.automake.bugs/6446 <pre>I've pushed this now, and I'm thus closing the bug report. Feel free to re-open it in case the error persists. Regards, Stefano </pre> Stefano Lattarini 2012-05-13T11:24:45 http://permalink.gmane.org/gmane.comp.sysutils.automake.bugs/6445 <pre>tags 11452 + patch severity 11452 minor thanks Hi Simon, thanks for the report. On 05/11/2012 10:45 AM, Simon Josefsson wrote: [SNIP] It's a spurious failure due to internationalization/localization. Does the attached patch fix the problem for you? Regards, Stefano </pre> Stefano Lattarini 2012-05-12T06:44:06 http://permalink.gmane.org/gmane.comp.sysutils.automake.bugs/6444 <pre>I got two self-test failures with automake 1.12 on Ubuntu 12.04 LTS. The first was the 'lex-clean' issue that was already reported. The other I couldn't find any report for, so please find test-suite.log output for the failing test below. /Simon FAIL: t/parallel-tests-fork-bomb ================================ Running from installcheck: no Using TAP: no PATH = /home/jas/src/automake-1.12/t/ax:/home/jas/src/automake-1.12/t/wrap:/home/jas/bin:/usr/lib/lightdm/lightdm:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/home/jas/bin ++ pwd /home/jas/src/automake-1.12/t/parallel-tests-fork-bomb.dir + cat + using_gmake + case $am__using_gmake in + make --version -v + grep GNU GNU Make 3.81 + am__using_gmake=yes + return 0 + cond=: + cat + ulimit -t 8 + ulimit -t 8 + aclocal-1.12 -Werror + autoconf + automake-1.12 --foreign -Werror -Wall -a -Wno-portability configure.ac:2: installing './test-driver' + ./configure checking for a BSD-compatible install... /usr/bin/install -c checking whether </pre> Simon Josefsson 2012-05-11T08:45:31 http://permalink.gmane.org/gmane.comp.sysutils.automake.bugs/6443 <pre>Exactly. It seems there might be consensus on this idea: &lt;http://lists.gnu.org/archive/html/automake/2012-05/msg00012.html&gt; If it will turn out that is actually the case, I will close this bug report (the discussion will likely continue on the bug-libtool list). For now, let's wait and see how things evolve. Regards, Stefano </pre> Stefano Lattarini 2012-05-11T11:37:55 http://permalink.gmane.org/gmane.comp.sysutils.automake.bugs/6442 <pre>[adding coreutils, bug-gnulib] On 05/08/2012 04:48 AM, Akim Demaille wrote: Coreutils has code to compute relative paths; used by both 'realpath' and 'ln'; maybe it's time to graduate that to a full-blown gnulib module now that we want to use it elsewhere. </pre> Eric Blake 2012-05-08T14:21:05 http://permalink.gmane.org/gmane.comp.sysutils.automake.bugs/6439 <pre>Hi Stefano, It is a different issue. (But I happened to stumble across both bugs at the same time.) The issue on bug-texinfo is a problem with an INFOPATH that contains at least two directories. This issue here is about stale entries that refer to nonexistent nodes, when installing a new Automake release using the same --prefix as an older one. How to reproduce: 1. $ mkdir /tmp/inst 2. Install automake-1.11.2: $ tar xvfz .../automake-1.11.2.tar.gz $ (cd automake-1.11.2 &amp;&amp; ./configure --prefix=/tmp/inst &amp;&amp; make &amp;&amp; make install) 3. $ INFOPATH=/tmp/inst/share/info info automake works 4. Install automake-1.12 with the same --prefix: $ tar xvfz .../automake-1.12.tar.gz $ (cd automake-1.12 &amp;&amp; ./configure --prefix=/tmp/inst &amp;&amp; make &amp;&amp; make install) 5. $ INFOPATH=/tmp/inst/share/info info automake fails, it produces the manpage fallback. Bruno </pre> Bruno Haible 2012-05-07T23:19:20 http://permalink.gmane.org/gmane.comp.sysutils.automake.bugs/6438 <pre> My apologies for the tardy reply. I have been off working on other bugs elsewhere. In message &lt;4FA3C3F8.1010605&lt; at &gt;redhat.com&gt;, Eric Blake &lt;eblake&lt; at &gt;redhat.com&gt; wrote: OK, so sometimes Makefile target files can get only partially (and inadequattely) written. Granted. However you still haven't demonstrated how an initial `rm' would have made any difference at all to that specific problem, one way other the other. (It doesn't make the problem worse and it doesn't make the problem better either. It has no effect at all on the problem you cite.) Neither have you provided any example in which an initial `rm' at the start of the commands recipie to rebuild the target file would in fact have any deliterious effects whatsoever. In short, your assertion that doing an initial `rm' would be somehow a Bad Thing, on account of the potential ``partially written targets'' file problem simply does not stand up to scrutiny. This potential for partially-written target files exists and continues to exist entirely indepe</pre> Ronald F. Guilmette 2012-05-07T21:07:13 http://permalink.gmane.org/gmane.comp.sysutils.automake.bugs/6437 <pre>severity 11422 minor tags 11422 + moreinfo thanks On 05/06/2012 06:13 PM, Bruno Haible wrote: Hi Bruno, sorry for the delay. Am I misunderstanding something, or this is actually an issue with the format of the 'dir' files created by GNU install-info? In fact, I see this report from you on the bug-texinfo list: &lt;http://lists.gnu.org/archive/html/bug-texinfo/2012-05/msg00000.html&gt; Regards, Stefano </pre> Stefano Lattarini 2012-05-07T20:45:19 http://permalink.gmane.org/gmane.comp.sysutils.automake.bugs/6436 <pre>Hi, I have installed automake-1.12 a couple of days ago. In particular the info format documentation was installed as well: $ ls -lrt /arch/x86-linux/gnu/share/info/ ... -rw-r--r-- 1 bin bin 227199 25. Apr 11:16 standards.info -rw-r--r-- 1 bin bin 1142045 25. Apr 11:16 autoconf.info -rw-r--r-- 1 bin bin 27543 29. Apr 01:09 dir -rw-r--r-- 1 bin bin 74585 29. Apr 01:09 automake.info-3 -rw-r--r-- 1 bin bin 232045 29. Apr 01:09 automake.info-2 -rw-r--r-- 1 bin bin 296172 29. Apr 01:09 automake.info-1 -rw-r--r-- 1 bin bin 7620 29. Apr 01:09 automake.info -rw-r--r-- 1 bin bin 78461 29. Apr 01:09 automake-history.info The 'info' program finds the documentation of 'standards', 'autoconf', 'automake-history', but not the documentation of 'automake': $ export INFOPATH=/arch/x86-linux/gnu/share/info $ info --version info (GNU texinfo) 4.13 ... $ info standards (OK) $ info autoconf (OK) $ info automake-history (OK) $ info automake File: *manpages*, Node: automake, Up: (dir) AUTOMAKE(1) </pre> Bruno Haible 2012-05-06T16:13:35 http://permalink.gmane.org/gmane.comp.sysutils.automake.bugs/6434 <pre>tags 11413 + patch close 11413 thanks On 05/05/2012 05:51 PM, Stefano Lattarini wrote: Such an insight is offered by an older commit: commit 642699970e75580e0f11f5786302082e25d8f49c Author: Ralf Wildenhues &lt;Ralf.Wildenhues&lt; at &gt;gmx.de&gt; Date: Tue Mar 10 21:33:47 2009 +0100 Use append mode to capture parallel test output. * tests/lisp8.test: Use append mode for output from `make -j', to avoid dropped lines. * tests/parallel-tests3.test: Likewise. Signed-off-by: Ralf Wildenhues &lt;Ralf.Wildenhues&lt; at &gt;gmx.de&gt; I've verified (with the help of the attached script) that such an issue is indeed present on the affected systems (my Debian box and the Fedora ppc64 system offered by the GCC compile farm), and I've pushed the attached patch to fix it. I'm thus closing this bug report. Regards, Stefano </pre> Stefano Lattarini 2012-05-05T17:34:32 http://permalink.gmane.org/gmane.comp.sysutils.automake.bugs/6433 <pre>Severity: minor I'm sporadically seeing the failure below in the test 'tap-more.sh'. Anyone has an insight about what's going on? Regards, Stefano -*-*-*- tap-more: exec /bin/sh t/tap-more.sh Running from installcheck: no Using TAP: no PATH = [SNIP] ++ pwd /devel/stefano/src/am/branches/trunks/t/tap-more.dir + fetch_tap_driver + case $am_tap_implementation in + AM_TAP_AWK=gawk + export AM_TAP_AWK + sed '1s|#!.*|#! /bin/sh|' /home/stefano/src/am/branches/trunks/lib/tap-driver.sh + chmod a+x tap-driver + sed 10q tap-driver #! /bin/sh # Copyright (C) 2011-2012 Free Software Foundation, Inc. # # This program is free software; you can redistribute it and/or modify # it under the terms of the GNU General Public License as published by # the Free Software Foundation; either version 2, or (at your option) # any later version. # # This program is distributed in the hope that it will be useful, # but WITHOUT ANY WARRANTY; without even the implied warranty of + cat + cat + cat + cat + cat + chmod a+x 1.test 2.te</pre> Stefano Lattarini 2012-05-05T15:51:50 http://permalink.gmane.org/gmane.comp.sysutils.automake.bugs/6432 <pre> not my code base ;) ok, so the fact that it's warning via -Wall is new to 1.12, but the underlying issue (warning at all) is not imo, projects utilizing libtool shouldn't need to know this at all. the whole point is to hide these esoteric details behind a layer and focus on the bits that projects actually care about -- what sources to put into libraries, etc... so is the answer to update libtool to call AM_PROG_AR when it's available ? -mike </pre> Mike Frysinger 2012-05-04T19:19:49 http://permalink.gmane.org/gmane.comp.sysutils.automake.bugs/6431 <pre> See, for example, this autoconf patch: http://git.savannah.gnu.org/cgit/autoconf.git/commit/?id=e9cceec Autoconf was generating code that created a cache file by writing directly in to the target, and there were actual examples of failure in the wild where it broke because of a partially written cache file with incomplete contents and a current timestamp would not be regenerated to be complete. In fact, the problem was hit in practice so often that gcc had resorted to a per-directory config.cache just to work around the worst aspects of this failure mode. We switched things over to writing to a temporary file and atomically mv'ing it into place, and the bug disappeared. Any time you hit Ctrl-C in the middle of a make run, you might be interrupting a process that is in the middle of writing contents to an output file. Agreed, but that doesn't mean that we shouldn't advertise it as being safer than rm. Yes - in the case of autoconf's config.cache, things DO go wrong in a subsequent build if config.ca</pre> Eric Blake 2012-05-04T11:56:40 http://permalink.gmane.org/gmane.comp.sysutils.automake.bugs/6430 <pre>Hi Mike! On 2012-05-04 07:25, Mike Frysinger wrote: If you don't want *all* warnings, don't ask for *all* warnings :-) It's in NEWS, from 1.12: - The warnings in the category 'extra-portability' are now enabled by '-Wall'. In previous versions, one has to use '-Wextra-portability' to enable them. which should be read in light of this from 1.11.2: - New macro AM_PROG_AR that looks for an archiver and wraps it in the new 'ar-lib' auxiliary script if the selected archiver is Microsoft lib. This new macro is required for LIBRARIES and LTLIBRARIES when automake is run with -Wextra-portability and -Werror. You can get rid of the warning with the following (but I have not actually tested with your example): AM_INIT_AUTOMAKE([1.11 -Wall -Wno-extra-portability foreign]) Cheers, Peter </pre> Peter Rosin 2012-05-04T07:20:10 Search the mailing list at Gmane query http://search.gmane.org/?group=$group=gmane.comp.sysutils.automake.bugs