In message <[EMAIL PROTECTED]>, Joel Reicher writes: > > Unless I've misunderstood the other posts in the thread, it is not > nmh requiring GNU m4, but autoconf for when you regenerate the configure > script. It is, indeed, the case that GNU autoconf requires GNU m4. > > This would be an "issue" for any package where you wanted to regenerate > the configure script, but doing so is not part of a standard build.
Indeed, it seems that GNU m4 is required to regenerate the configure script; that is not a problem at all as the nmh source code will include a ready to use autoconf script. But once applied the patch that fixes the issues with nmh-1.2, non-GNU m4 flavours (at least the one in BSDs) complain about an unmatched bracket. Previously, I was able to run "./configure", "make" and "make install" on machines that do not have GNU m4 installed (e.g., machines with a fresh NetBSD install). Again, I believe that it is possible I did something wrong when regenerating the configure script. Why is m4 required to run "./configure"? It can be my fault, perhaps I did an incomplete configure script regeneration. What I see is that, after regenerating the configure script and making a new "tarball" with an updated "configure", I need GNU m4 to run the configure script and compile nmh. Cheers, Igor. _______________________________________________ Nmh-workers mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/nmh-workers
