Patch to autoconf-2.53: Mention m4_pattern allow in "possibly undefined macro" error message

[Adam J. Richter]

Akim Demaille <address@hidden> wrote:
>Or tell Autoconf that this token is valid.
>
>m4_patten_allow([^AS_SPARC64_FLAG$])
>
>See the documentation.

        Developers use autoconf to save their valuable time, so please
apply the following patch that mentions m4_pattern_allow in the
message that autoconf prints out.  In general, I think you will find
that it will save time for both your users and you if you include
pointers to the most likely possible solutions in warnings and error
messages.

        Also, I still this should be a warning rather than a fatal error,
but I'm not quite clear on what change to make to effect that.

Adam J. Richter     __     ______________   4880 Stevens Creek Blvd, Suite 104
address@hidden     \ /                  San Jose, California 95129-1034
+1 408 261-6630         | g g d r a s i l   United States of America
fax +1 408 261-6631      "Free Software For The Rest Of Us."

--- autoconf-2.53/bin/autom4te.in       2002-03-08 04:05:40.000000000 -0800
+++ autoconf/bin/autom4te.in    2002-04-08 01:10:36.000000000 -0700
@@ -649,7 +649,7 @@
          last;
        }
     }
-  $message ||= "possibly undefined macro: $word";
+  $message ||= "possibly undefined macro: $word (use m4_pattern_allow to allow 
it)";
   warn "$where: error: $message\n";
 }