My project is using autoconf 2.63 and recently I have noticed a
strange problem due to a definition of ac_cr in the configure script.
It seems that this definition is expecting that 'configure' is now a
immutable binary file format rather than a text file format. This
causes problems if the configure script is stored in CVS and then
checked out under Windows. The following difference was caused after
someone checked out the configure script under Windows and then did a
'cvs commit' of the unexpected change caused by the checkout:
cvs diff -D yesterday configure
Index: configure
===================================================================
RCS file: /GraphicsMagick/GraphicsMagick/configure,v
retrieving revision 1.664
retrieving revision 1.665
diff -u -r1.664 -r1.665
--- configure 3 Jan 2009 17:06:59 -0000 1.664
+++ configure 11 Jan 2009 14:11:54 -0000 1.665
@@ -41855,7 +41855,8 @@
if test -n "$CONFIG_FILES"; then
'ac_cr='
+ac_cr='
+'
ac_cs_awk_cr=`$AWK 'BEGIN { print "a\rb" }' </dev/null 2>/dev/null`
if test "$ac_cs_awk_cr" = "a${ac_cr}b"; then
ac_cs_awk_cr='\\r'
======================================
Bob Friesenhahn
bfriesen@xxxxxxxxxxxxxxxxxxx, http://www.simplesystems.org/users/bfriesen/
GraphicsMagick Maintainer, http://www.GraphicsMagick.org/
_______________________________________________
Autoconf mailing list
Autoconf@xxxxxxx
http://lists.gnu.org/mailman/listinfo/autoconf
