Ralf Wildenhues wrote: > GNU Autoconf test version 2.59d is now available. > > This is a beta release, intended to be largely identical to 2.60, > to be released very soon, if no unexpected issues turn up. So test it > now, use it with your code, and report any remaining issues, please! > > The important changes since 2.59c are listed below, but two changes > introduced earlier, in version 2.59c, require special attention: > > * Some directory variables have been added, and others adjusted to > changes in the GNU Coding Standards. If your package expands > '$datadir', '$infodir', or '$mandir' anywhere, you need to check your > package, and possibly adjust it accordingly. The URL to the older > NEWS entries below, and the FAQ node 'Defining Directories' in the > manual have more information. > > * AC_PROG_CC and AC_PROG_CXX no longer arrange for an 'exit' > function declaration. If you use this in your macros, you need to > ensure that such a declaration is in place for C99 and C++ checks, > or change the tests to 'return' from 'main' instead. > > > Here are the compressed sources: > ftp://alpha.gnu.org/gnu/autoconf/autoconf-2.59d.tar.gz (1.4MB) > > Here are the GPG detached signatures: > ftp://alpha.gnu.org/gnu/autoconf/autoconf-2.59d.tar.gz.asc > > Here are the MD5 and SHA1 signatures: > > 3c0eb03b60bad6823bd36b632b65ab94 autoconf-2.59d.tar.gz > 30efc24b8abe2f0a010b95363c17313ea24ecf26 autoconf-2.59d.tar.gz >
@top_builddir@ used to expand to ../../../ now it expands to ../../.. Parts of our Makefiles were relying on the trailing slash, so they don't work with this version of autoconf. Is this change also intentional? Thanks William
