Gary, I'm afraid I don't understand the failure of modpath2 :(
Here is the relevant snippet from testsuite.log:
21. ./others.at:646: testing modpath2...
./others.at:654: M4PATH=$top_srcdir LTDL_LIBRARY_PATH=$top_builddir/modules $M4
-m load -d modules/modtest.m4
--- - Sat Aug 18 11:09:11 2001
+++ at-stderr Sat Aug 18 11:09:11 2001
@@ -1,2 +1,2 @@
-test: <test>
+lt-m4: ERROR: module `load' has no entry points
--- - Sat Aug 18 11:09:11 2001
+++ at-stdout Sat Aug 18 11:09:11 2001
@@ -1,4 +1 @@
-Test module loaded.
-Test module called.
-Dumpdef: .
./others.at:654: exit code was 1, expected 0
21. ./others.at:646: FAILED near `others.at:654'
The other modpath tests work fine, I perfectly understand the other failures,
due to Autotest, but this one, I really have no clue.
This is with CVS M4 as of yesterday.
## -------- ##
## modpath2 ##
## -------- ##
# Written by Gary V. Vaughan <[EMAIL PROTECTED]>
AT_SETUP([modpath2])
AT_CHECK([M4PATH=$top_srcdir LTDL_LIBRARY_PATH=$top_builddir/modules $M4 -m load -d
modules/modtest.m4], 0,
[[Test module loaded.
Test module called.
Dumpdef: .
]],
[[test: <test>
]])
AT_CLEANUP
_______________________________________________
Bug-m4 mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/bug-m4
