Mail Archives: cygwin-announce/2002/05/19/18:44:15
Version 2.53-1 of the autoconf-devel package is now available.
It contains GNU autoconf-2.53, installed into /usr/autotool/devel.
GNU Autoconf-2.53a contains some bugfixes that cropped up in the
2.53 release.
Changes since 2.53-1
o update to the GNU 2.53a release
o all 163 self tests successful (3 skipped)
o There DOES seem to a problem in BOTH 2.53 and 2.53a, where
seemingly valid configure.in/acinclude.m4 files lead to buggy
configure scripts. This bug ALSO exists in 2.52. So, in that
respect, 2.53a-1 is no worse than any other cygwin release
of autoconf-devel.
o See NOTES below.
--
Chuck Wilson
To update your installation, click on the "Install Cygwin now" link
on the http://cygwin.com/ web page. This downloads setup.exe to
your system. Save it and run setup, answer the questions and pick
up 'autoconf-devel' from the 'Devel' category.
Note that downloads from sources.redhat.com (aka cygwin.com) aren't
allowed due to bandwidth limitations. This means that you will need
to find a mirror which has this update.
In the US, ftp://mirrors.rcn.net/mirrors/sources.redhat.com/cygwin/
is a reliable high bandwidth connection.
In Japan, ftp://ftp.u-aizu.ac.jp/pub/gnu/gnu-win32/ is already
updated.
In DK, http://mirrors.sunsite.dk/cygwin/ is usually up-to-date.
If one of the above doesn't have the latest version of this package
you can either wait for the site to be updated or find another
mirror.
Please send questions or comments to the Cygwin mailing list at:
cygwin AT sources DOT redhat DOT com . If you want to subscribe go to:
http://cygwin.com/lists.html I would appreciate if you would use
this mailing list rather than emailing me directly. This includes
ideas and comments about the setup utility or Cygwin in general.
If you want to make a point or ask a question the Cygwin mailing
list is the appropriate place.
*** CYGWIN-ANNOUNCE UNSUBSCRIBE INFO ***
To unsubscribe to the cygwin-announce mailing list, look at the
"List-Unsubscribe: " tag in the email header of this message. Send
email to the address specified there. It will be in the format:
cygwin-announce-unsubscribe-YOU=YOURDOMAIN DOT COM AT cygwin DOT com
NOTES:
Although autoconf-2.53a passes all of its own self tests on cygwin,
it still misbehaves in some cases. In general, if autoconf
completes without error, it should NEVER create a configure script
with syntax errors. autoconf-2.53a, autoconf-2.53, and autoconf-2.52
ALL do so in a specific case.
I've been working with cvs-1.11.2, and when re-autoconf'ing, autoconf
gets really confused. I mean, it totally loses track of what it's doing,
and puts in comments without '#' marks, drops 'help' text in the
middle of the running script, etc. To give you a clue, here are the
fixes I had to apply by hand to configure:
1) the --enable-client help text was not put into the help section,
but rather just dropped willy-nilly into the script itself.
2) case statements were completely hosed (no closing ')', a random
'fi' just dropped in there...
3) if statements not closed: 'fi' or 'else' ommitted...
However, I must reiterate: I get similar errors with 2.52 and
2.53(no a). This is not a bug specific to this latest release.
Second, it is not a bug in my configure.in/acinclude.m4 code --
autoconf should either generate a syntactically correct configure
script, or generate an error message itself. It should never
generate buggy script and not report an error.
--- cvs-1.11.2-orig/configure 2002-05-19 06:46:53.000000000 -0400
+++ cvs-1.11.2/configure 2002-05-19 06:16:46.000000000 -0400
@@ -848,6 +848,8 @@
--disable-dependency-tracking Speeds up one-time builds
--enable-dependency-tracking Do not reject slow dependency extractors
--enable-encryption enable encryption support
+ --enable-client include code for running as a remote client
+ (default)
--enable-server include code for running as a server (default)
Optional Packages:
@@ -6037,6 +6039,7 @@
#define HAVE_GETSPNAM 1
_ACEOF
+fi
echo "$as_me:$LINENO: checking whether utime accepts a null argument" >&5
echo $ECHO_N "checking whether utime accepts a null argument...
$ECHO_C" >&6
@@ -6307,9 +6310,7 @@
# So? What about this header?
case $ac_header_compiler:$ac_header_preproc in
- yes:no
-fi
-
+ yes:no )
{ echo "$as_me:$LINENO: WARNING: $ac_header: accepted by the
compiler, rejected by the preprocessor!" >&5
echo "$as_me: WARNING: $ac_header: accepted by the compiler, rejected
by the preprocessor!" >&2;}
{ echo "$as_me:$LINENO: WARNING: $ac_header: proceeding with the
preprocessor's result" >&5
@@ -9124,18 +9125,14 @@
:
else
LIBOBJS="$LIBOBJS hostname.$ac_objext"
+fi
-
- --enable-client include code for running as a remote client
- (default)
# Check whether --enable-client or --disable-client was given.
if test "${enable_client+set}" = set; then
enableval="$enable_client"
case "${enableval}" in
- yes
-fi
- client=yes;;
+ yes) client=yes;;
no) client=no;;
*) { { echo "$as_me:$LINENO: error: bad value ${enableval} for
client option" >&5
echo "$as_me: error: bad value ${enableval} for client option" >&2;}
@@ -9529,9 +9526,7 @@
# So? What about this header?
case $ac_header_compiler:$ac_header_preproc in
- yes:no
-fi
-
+ yes:no )
{ echo "$as_me:$LINENO: WARNING: gdbm.h: accepted by the compiler,
rejected by the preprocessor!" >&5
echo "$as_me: WARNING: gdbm.h: accepted by the compiler, rejected by
the preprocessor!" >&2;}
{ echo "$as_me:$LINENO: WARNING: gdbm.h: proceeding with the
preprocessor's result" >&5
@@ -9566,13 +9561,12 @@
echo "$as_me: error: cannot find gdbm.h" >&2;}
{ (exit 1); exit 1; }; }
fi
-
-,
+ else
{ { echo "$as_me:$LINENO: error: cannot find libgdbm" >&5
echo "$as_me: error: cannot find libgdbm" >&2;}
- { (exit 1); exit 1; }; })
+ { (exit 1); exit 1; }; }
fi
-
+fi
fi # cygwin
test -f src/options.h && (
- Raw text -