[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Warnings are broken
From: |
Pavel Roskin |
Subject: |
Warnings are broken |
Date: |
Wed, 14 Feb 2001 19:49:25 -0500 (EST) |
Hello!
It appears that neighter "autoconf -Wall" nor "autoconf -Wobsolete" work
as expected in the Autoconf's configure.in on CVS.
I was trying ro add a test case:
_____________________
--- tools.at
+++ tools.at
@@ -96,6 +96,28 @@
+## ------------------- ##
+## autoconf warnings. ##
+## ------------------- ##
+
+# autoconf -Wall
+# --------------
+AT_SETUP([autoconf -Wall])
+
+AT_DATA(configure.ac,
+[[AC_INIT([foo])
+AC_MSG_ERROR([bad \"value\" found])
+AC_OUTPUT([Makefile])]])
+
+AT_CHECK_AUTOCONF([-Wall], 0, [], [some warnings ...])
+
+AT_CLEANUP
+
+
+
+
+
+
## ------------------ ##
## autoconf --trace. ##
## ------------------ ##
_____________________
But the result is very strange:
1: tools.at:29 ok
2: tools.at:75 ok
3: tools.at:105 FAILED near `tools.at:154'
testsuite: no such test: 4
5: tools.at:188 ok
6: tools.at:221 ok
I don't understand how to add new tests.
Now I'm looking into atspecific.m4 and see that in doesn't know anything
about configure.ac, only configure.in.
I don't have much time now, and actually there are few hundreds messages
in autoconf@ that I haven't read yet, so I'm sorry for lame questions.
Regards,
Pavel Roskin
- Warnings are broken,
Pavel Roskin <=