Martin Oberhuber wrote: > Hello, > > I have found a problem with the automake and autoconf scripts installed > in /usr/bin for switching between the DEVEL and STABLE versions of > automake and autoconf. > > The bug leads to breaking automake or aclocal on scripts where some > text follows the AC_PREREQ line (like, for instance, in the DDD > configuration script). > > In Detail: automake allows a line like > AC_PREREQ(2.13)dnl > where some text follows the closing parenthesis after the version number. > The trailing text is not correctly eliminated by the SED script > which extracts the version number in the automake/autoconf scripts > distributed. > > For correcting the bug, replace the following line: > VER=`sed -n -e '/AC_PREREQ/s/[^(]*(\([[:digit:]\.]*\))/\1/p' < $infile` > with the corrected line: > VER=`sed -n -e '/AC_PREREQ/s/[^(]*(\([[:digit:]\.]*\)).*$/\1/p' < $infile` > > in all autoconf/automake scripts: > aclocal autoheader autoreconf autoupdate autoconf automake autoscan ifnames > > corrected versions of these scripts are in the attached tarfile.
Thanks -- I've corrected this in the primary source packages here: http://www.neuro.gatech.edu/users/cwilson/auto-wrapper/ automake-scripts-1.5b.tar.bz2 autoconf-scripts-2.52a.tar.bz2 Also, I've put updated cygwin-style packages for Corinna here: http://www.neuro.gatech.edu/users/cwilson/cygutils/testing/ automake-1.5b-1.tar.bz2 automake-1.5b-1-src.tar.bz2 autoconf-2.52a-1.tar.bz2 autoconf-2.52a-1-src.tar.bz2 Finally, I've also made a note to correct this in the (very very experimental) libtool scripts. Next time, however, it would be better to generate a patch against the source code (automake.in, aclocal.in) and not simply create new output files. (That's kinda like shipping a corrected '.exe' file without incuding the source. Not quite, because THESE ".exe" files are just text, but still...) And also a changelog. Thanks, Chuck -- 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/