Re: autoconf 2.52 testsuite fails.

[Jack Cummings]

On Fri, Aug 10, 2001 at 08:55:53AM +0200, Akim Demaille wrote:
 
> Please, keep it public.

Ooops. Used to having the list in Reply-to:.. 
 
> | Could it be related to HP-UX having a mktemp that isn't really
> | compatable with the OpenBSD mktemp derivative?
 
> No idea.  The code to create the tmp dir seemed to have been working
> up to now.  But you might be right, we'll see that afterward.

Hmm. I'm begining to suspect this more so. If the HPUX mktemp is used:

--

$ ./debug-5.sh
================================
Test suite for GNU Autoconf 2.52
================================
5. ../../tests/tools.at:201: testing autoconf: forbidden tokens, basic...
../../tests/tools.at:215: autoconf --autoconf-dir .. -l $at_srcdir
stderr:
/pkg/autoconf/autoconf__v2.52.dist/autoconf-2.52/hppa2.0w-hp-hpux11.00/autoconf[337]:
 /forbidden.rx: Cannot create the specified file.
0a1
>
../../tests/tools.at:215: exit code was 0, expected 1
5. ../../tests/tools.at:201: FAILED near `tools.at:215'

--

But if the OpenBSD mktemp is used:

--

$ export PATH=/usr/local/bin:$PATH
$ ./debug-5.sh
================================
Test suite for GNU Autoconf 2.52
================================
5. ../../tests/tools.at:201: testing autoconf: forbidden tokens, basic...
../../tests/tools.at:215: autoconf --autoconf-dir .. -l $at_srcdir
stderr:
sh: cat:  not found.
configure.ac:1: error: m4_file_append: cannot write: /tmp/acg11531/forbidden.rx
configure.ac:1: the top level
--- /dev/null   Fri Aug 10 12:05:07 2001
+++ at-stdout   Fri Aug 10 12:05:07 2001
@@ -0,0 +1 @@
+/tmp/acg11531
5. ../../tests/tools.at:201: FAILED near `tools.at:215'

--
 
> > m4trace:configure.ac:1: -1- id 7: 
> > m4_file_append([/tmp/acAc3224/forbidden.rx], [^m4_]) -> ???
> > m4trace:configure.ac:1: -1- id 7: m4_file_append(...) -> [m4_syscmd([cat 
> > >>/tmp/acAc3224/forbidden.rx <<_m4eof
> > ^m4_
> > _m4eof
> > ])
> > m4_if(m4_sysval, [0], [],
> >       [m4_fatal([m4_file_append: cannot write: 
> > /tmp/acAc3224/forbidden.rx])])]
> > m4trace:configure.ac:1: -1- id 13: m4_syscmd ...
> > m4trace:configure.ac:1: -1- id 13: m4_syscmd([cat 
> > >>/tmp/acAc3224/forbidden.rx <<_m4eof
> > ^m4_
> > _m4eof
> > ]) -> ???
> > sh: cat:  not found.
 
> This is the actual failure.  I don't understand the error msg at all.
> I doubt that the tmp dir what not created, I suppose `autoconf' would
> have failed, but who knows...
 
> To check that it was created, please run
> 
>         ./debug-5.sh
>         ../autoconf -A .. -d -v

--

$ ./debug-5.sh
================================
Test suite for GNU Autoconf 2.52
================================
5. ../../tests/tools.at:201: testing autoconf: forbidden tokens, basic...
../../tests/tools.at:215: autoconf --autoconf-dir .. -l $at_srcdir
stderr:
sh: cat:  not found.
configure.ac:1: error: m4_file_append: cannot write: /tmp/acS11732/forbidden.rx
configure.ac:1: the top level
--- /dev/null   Fri Aug 10 12:07:27 2001
+++ at-stdout   Fri Aug 10 12:07:27 2001
@@ -0,0 +1 @@
+/tmp/acS11732
5. ../../tests/tools.at:201: FAILED near `tools.at:215'
$ ../autoconf -A .. -d -v
/tmp/acp11796
autoconf: running /usr/local/bin/gm4 --nesting-limit=1024 -I .. -I . 
-Dm4_tmpdir=/tmp/acp11796 -Dm4_warnings=syntax --reload-state=../autoconf.m4f   
configure.ac
sh: cat:  not found.
configure.ac:1: error: m4_file_append: cannot write: /tmp/acp11796/forbidden.rx
configure.ac:1: the top level
$ ls /tmp/acp11796/
allowed.rx  configure  forbidden.rx

--
 
> the verbose messages should refer to the tmp dir it used, and with -d,
> it should not be removed.  So you should be able to check if it was
> created or not.
 
Looks like it was created fine. 

It would look like the ' m4_syscmd([cat...])' call is where the error message 
is coming from. 

Is my m4 installation cooked?
 
> > m4trace:configure.ac:1: -1- id 13: m4_syscmd(...)
> > m4trace:configure.ac:1: -1- id 14: m4_if ...
> > m4trace:configure.ac:1: -2- id 15: m4_sysval ...
> > m4trace:configure.ac:1: -2- id 15: m4_sysval -> ???
> > m4trace:configure.ac:1: -2- id 15: m4_sysval -> [127]
> > m4trace:configure.ac:1: -1- id 14: m4_if([127], [0], [], 
> > [m4_fatal([m4_file_append: cannot write: /tmp/acAc3224/forbidden.rx])]) -> 
> > ???
> > m4trace:configure.ac:1: -1- id 14: m4_if(...) -> [m4_fatal([m4_file_append: 
> > cannot write: /tmp/acAc3224/forbidden.rx])]
> > m4trace:configure.ac:1: -1- id 16: m4_fatal ...
> > m4trace:configure.ac:1: -1- id 16: m4_fatal([m4_file_append: cannot write: 
> > /tmp/acAc3224/forbidden.rx]) -> ???
> > m4trace:configure.ac:1: -1- id 16: m4_fatal(...) -> 
> > [m4_errprintn(m4_location[: error: m4_file_append: cannot write: 
> > /tmp/acAc3224/forbidden.rx])dnl

> Good, the error was caught.  But was it clearly displayed?  I don't
> remember...

Yeah. configure.ac:1: error: m4_file_append: cannot write: 
/tmp/acj12120/forbidden.rx

> Hm...  Just a stupid idea...  Could you try:
 
> cat >/tmp/foo <<_m4eof
> ^m4_
> _m4eof

--

$ cat >/tmp/foo <<_m4eof
> ^m4_
> _m4eof
$ cat /tmp/foo
^m4_

--

> cat >>/tmp/bar <<_m4eof
> ^m4_
> _m4eof

--

$ cat >>/tmp/bar <<_m4eof
> ^m4_
> _m4eof
$ cat /tmp/bar
^m4_

--

--Jack 

--
Jack (John) Cummings         CAD Infrastructure Engineer
address@hidden      PMC-Sierra
phone: 604 415 6100 x2351    fax:  604 415 6245
HIGH EXPLOSIVES AND SCHOOL DON'T MIX
HIGH EXPLOSIVES AND SCHOOL DON'T MIX
HIGH EXPLOSIVES AND SCHOOL DON'T MIX
HIGH EXPLOSIVES AND SCHOOL DON'T MIX

        Bart Simpson on chalkboard in episode 8F03