[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: autoconf test failures - how to react?
From: |
Jerker Bäck |
Subject: |
Re: autoconf test failures - how to react? |
Date: |
Sun, 7 May 2006 14:47:29 +0200 |
> 225: AC_TYPE_INT64_T Windows NT Exception (core dumped)
> That's an interesting diagnostic.
I suspect this come from GNU sed since it disappear with BSD sed I need to
recompile sed more carefully
> 12: autoupdating AC_PREREQ FAILED (tools.at:570)
> makes it look like the Perl system function cannot run /bin/m4 Perhaps
> Perl cannot run system("echo foo | /bin/m4")
$ perl -v
This is perl, v5.6.1 built for x86-interix
How to test the system command?
$ perl system("echo foo | /bin/m4")
/bin/ksh: syntax error: `(' unexpected
$ perl
system("echo foo | /bin/m4")
<nothing>
> I suspect that your 'diff' program is buggy, and sometimes dumps core.
> You might try substituting GNU diff.
I'm doing that right now along with a new sed
86: Define a newline expected failure (torture.at:632)
$ cd tests/testsuite.dir/086
$ ls -l state-ls.before state-ls.after
-rw-r--r-- 1 Jerker Domänanvändare 74 May 4 15:16 state-ls.after
-rw-r--r-- 1 Jerker Domänanvändare 74 May 4 15:15 state-ls.before $ file
state-ls.before state-ls.after
state-ls.before: ascii text
state-ls.after: ascii text
$ diff -u state-ls.before state-ls.after $ diff state-ls.before
state-ls.after
(Not so very enlightening?)
- autoconf test failures - how to react?, Jerker Bäck, 2006/05/03
- autoconf test failures - how to react?, Jerker Bäck, 2006/05/03
- Re: autoconf test failures - how to react?, Paul Eggert, 2006/05/04
- Re: autoconf test failures - how to react?,
Jerker Bäck <=
- Re: autoconf test failures - how to react?, Paul Eggert, 2006/05/07
- Re: autoconf test failures - how to react?, Eric Blake, 2006/05/08
- Re: autoconf test failures - how to react?, Jerker Bäck, 2006/05/09
- Re: autoconf test failures - how to react?, Ralf Wildenhues, 2006/05/09
- SV: autoconf test failures - how to react?, Jerker Bäck, 2006/05/09