On 06/20/2014 09:54 AM, Jeffrey Sheen wrote: > Dear lists, > > I have run `testsuite' with the latest tar of Autoconf, and have many > failures reported. > You definitely have a broken setup, but I'm not sure what's causing it. > Please find the output logs attached for `make check' and `make > installcheck'. The errors in both are the same according to `diff'. > > If you could find the time to take a look, it'd be much appreciated. From your other mail: > # -*- compilation -*- > 5. tools.at:145: testing autom4te and whitespace in file names ... > ./tools.at:163: mkdir "$dir" "$cachedir" "$TMPDIR" && touch "$file" || exit 77 > ./tools.at:174: autom4te -C "$cachedir" -B "$dir" --language=m4sugar -o "$outfile" "$file" > ./tools.at:175: cat "$outfile" > --- - 2014-06-20 15:46:02.000000000 +0100 > +++ /Volumes/DATA/filestore/development/gnu/autoconf/extract/autoconf-2.69/tests/testsuite.dir/at-groups/5/stdout 2014-06-20 15:46:02.000000000 +0100 > @@ -1,2 +1,5 @@ > +m4trace: file with funny ' $x & #! name:1: -1- m4_pattern_forbid([^_?m4_]) > +m4trace: file with funny ' $x & #! name:1: -1- m4_pattern_forbid([^dnl$]) > +m4trace: file with funny ' $x & #! name:1: -1- m4_include([foo.m4]) > bar We need to figure out what is causing those spurious 'm4trace: ' lines to be output at the beginning of every run of autom4te. Do you have any environment variables or config.site that might be interfering with normal operation of the tools, by causing autom4te to behave as if it were being requested to trace macros instead of do its normal job? -- Eric Blake eblake redhat com +1-919-301-3266 Libvirt virtualization library http://libvirt.org
Attachment:
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Autoconf mailing list Autoconf@xxxxxxx https://lists.gnu.org/mailman/listinfo/autoconf
