Re: autoconf 2.49 on UNICOS

[Johan Danielsson]

Akim Demaille <address@hidden> writes:

> Could you try to see what happened?  Rerun the corresponding debug.sh,
> and run `../autoupdate -A .. -<configure.in; echo $?'.  It should end
> with `77'.

$ ./debug-111.sh 

==================================
./debug-111.sh: Testing autoupdate
==================================
/tmp/joda/autoconf-2.49a/tests/tools.m4:180: testing...
--- -   Wed Nov 22 19:48:28 2000
+++ stdout      Wed Nov 22 19:48:27 2000
@@ -1,6 +1,4 @@
 AC_INIT
 dnl The doc says 27 is a valid fubar.
 fubar=27
-AC_CONFIG_FILES([Makefile])
-AC_CONFIG_COMMANDS([default],[[echo $fubar]],[[fubar=$fubar]])
-AC_OUTPUT
+AC_OUTPUT(Makefile, echo $fubar, fubar=$fubar)
$ ../autoupdate -A .. < configure.in ; echo $?
sed: 1: "s/[^/]*$//": RE error: [ ] imbalance or syntax error
sh-56 ../autoupdate[220]: /usr/gnu/bin/autoconf: not found.
sh-56 ../autoupdate[228]: /usr/gnu/bin/autoconf: not found.
sh-56 ../autoupdate[241]: /usr/gnu/bin/autoconf: not found.
autoupdate: `configure.in' is unchanged
0

If I change the sed command, I get:

sed: 1: /tmp/au7118/au-del.sed: command a expects \ followed by text
autoupdate: `configure.in' is unchanged
0

But this looks more like other problems. Should it work to build with
separate obj dir, and run make check?

/Johan