> autogen.sh hasn't been modified, that I can see, since
> February 2 of this year. I haven't run into the problem (on
> either my BSD systems or on SuSE 8.2) so I'm not sure why
> autogen.sh isn't running autoheader for some folks. Perhaps
That prompted me to look why lately it has stopped working for me too. I
was thinking that my autoconf update messed things up.
well, it appears autogen.sh was not updated to match with the replacement
AM_CONFIG_HEADER --> AM_CONFIG_HEADER in configure.in. Here is a "one
line" patch.
--- autogen.sh.orig Sat Jun 7 11:47:17 2003
+++ autogen.sh Sat Jun 7 11:50:01 2003
@@ -126,7 +126,7 @@
fi
echo "Running aclocal $aclocalinclude ..."
aclocal $aclocalinclude
- if grep "^AM_CONFIG_HEADER" configure.in >/dev/null; then
+ if grep "^AC_CONFIG_HEADER" configure.in >/dev/null; then
echo "Running autoheader..."
autoheader
fi
Wonder why this does not affect everyone? May be because config.h.in will
be absent only for fresh cvs trees or after a "make maintainer-clean"..
Selva
-------------------------------------------------------
This SF.net email is sponsored by: Etnus, makers of TotalView, The best
thread debugger on the planet. Designed with thread debugging features
you've never dreamed of, try TotalView 6 free at www.etnus.com.
_______________________________________________
Mjpeg-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/mjpeg-users
