I've been converting some of our build system to use the cygwin autotools
recently, and I think I've come across a bug in the autoconf/autoheader
wrapper scripts (I assume these may occur in the other auto* scripts, but
these are the specific ones I use).
Our build script sets up M4PATH to the location of some company-specific m4
macro files before calling autoconf; on every other UNIX we've come across,
this works fine for autoconf and also autoheader.
However, the cygwin wrappers explicitly redefine M4PATH *without* including
the original value; this is after adding to PATH in the expected way.
I don't quite understand this; the m4 documentation says M4PATH is a
colon-separated list of directory names, and I'm pretty sure it shouldn't
just be redefined in this way.
I've appended a patch for the autoconf wrapper; if I'm correct this'll need
to be applied to all the other wrapper scripts that need the extra m4 path
themselves.
Another problem I've found is that the check for AC_PREREQ in the autotools
wrappers only searches through configure.in and not any m4 files that might
be included from it. This means I have to add this line to a number of
different configure.in files rather than just changing one of the
company-specific m4 files. I can't think of an easy fix for this, though.
Cheers,
-James Harvey
--- autoconf Mon Feb 25 17:04:37 2002
+++ autoconf~ Mon Feb 25 15:25:15 2002
@@ -200,14 +200,14 @@
if [ "x${VER_MIN}" != "x" ] ; then
if (( ${VER_MIN} <= 13 )) ; then
export PATH=${AUTO_STABLE}/bin:${PATH}
+ export M4PATH=${AUTO_STABLE}/share/autoconf:${M4PATH}
- export M4PATH=${AUTO_STABLE}/share/autoconf
else
export PATH=${AUTO_DEVEL}/bin:${PATH}
+ export M4PATH=${AUTO_DEVEL}/share/autoconf:${M4PATH}
- export M4PATH=${AUTO_DEVEL}/share/autoconf
fi
else
export PATH=${AUTO_DEVEL}/bin:${PATH}
+ export M4PATH=${AUTO_DEVEL}/share/autoconf:${M4PATH}
- export M4PATH=${AUTO_DEVEL}/share/autoconf
fi
# exec the "real" autoconf
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
