?????????? ????????? - ??????????????? - /home/agenciai/public_html/cd38d8/autoconf.zip
???????
PK [�!\�B�\ \ TODOnu �[��� -*- outline -*- Things it might be nice to do someday. I haven't evaluated all of these suggestions... their presence here doesn't imply my endorsement. -djm & his successors. ------------------------------------------------------------------------------ * Soon ** AC_CHECK_HEADERS and the like, don't have a consistent way to handle multi-line arguments. Fix, test, and document. ** --target & AC_ARG_PROGRAM Shouldn't *any* `program' be installed as `$target_alias-program' even if AC_ARG_PROGRAM is not called? That would be much more predictable. Ian? ** AC_CHECK_TOOL... Write a test that checks that it honors the values set by the user. ** autom4te and warnings. Decide what must be done. ** AC_DEFINE(func, rpl_func) This scheme causes problems: if for instance, #define malloc rpl_malloc, then the rest of configure will use an undefined malloc. Hence some tests fail. Up to now we simply #undef these functions where we had a problem (cf. AC_FUNC_MKTIME and AC_FUNC_MMAP for instance). This is _bad_. Maybe the #define func rpl_malloc should be performed in another file than confdefs.h, say confh.h, which is used for config.h generation, but not used in configure's own tests. ** AC_PROG_CC Currently it tries to put the C compiler in ANSI C mode by default. We should change this spec so that AC_PROG_CC tries to change the compiler to be the "nicest" mode, i.e. support for the latest standard features (currently ISO C99) plus support for all vendor extensions, even if they are slightly incompatible with C99. The basic idea here is that AC_PROG_CC should disable pedanticisms and should enable extensions. Have a way to specify different default flags to try; see this thread for more information: <http://lists.gnu.org/archive/html/bug-autoconf/2008-08/msg00009.html>. * Later ** config.site This guy is really a problem. It's contents should be read before handling the options, so that the latter properly override the latter, but most people would want a means to have a config.site that depends on $prefix for instance. Some other would like config.site to be looked for in the current directory. Harlan: I'll go further. I'd like to see several layers of config.site available. I'm starting to use "modules" at more places to handle software installation, and it would be helpful to set general things like: prefix=/opt/pkg/@PACKAGE@/@VERSION@ once at a global level, and then, for example, have things like: --with-etcdir=$prefix/etc stuffed "above" the various versions of SSH so I wouldn't have to hunt for these things every time it was time to recompile a new version of a previously installed package. Something like: src/config.site Global stuff ... src/ssh/config.site package-specific stuff src/ssh/ssh-1.2.27/ the actual source code I'd like to see automake/autoconf better support packaging tools (like modules, the *BSD ports/ stuff, and others would like hooks for RPMs). ** Languages Integrate other Fortrans etc. ** AC_CHECK_FUNCS and AC_TRY_LINK_FUNC I have still not understood what's the difference between the two which requires to have two different sources: AC_LANG_CALL and AC_LANG_FUNC_LINK_TRY (which names seem to be inappropriate). Wouldn't one be enough? ** Libtool Define once for all the hooks they need, any redefinition of AC_PROG_CC etc. is way too dangerous and too limiting. The GCC team certainly has requirements too. ** AC_SEARCH_LIBS From: Tom Tromey <tromey@cygnus.com> Subject: AC_SEARCH_LIBS I think AC_SEARCH_LIBS has an unfortunate interface. ACTION-IF-FOUND is run in addition to the default action. Most autoconf macros don't work this way. This is confusing. In my case I can't use this macro because it always appends to LIBS. I don't want that. Instead I want to use ACTION-IF-FOUND to set my own macro. Also there is no documentation on the format of library names expected by the macro. Even a reference to some other function (e.g., "the library name can have the same forms as with AC_HAVE_LIBRARY" (if that is true, which I haven't looked up) would be fine. ** Revamp the language support We should probably have a language for C89, and C99. We must give the means to the users to specify some needs over the compilers, and actually look for a good compiler, instead of stopping at the first compiler we find. In fact, the AC_CHECK_PROG macro and variations have proved their limitation: we really need something more powerful and simpler too. We must take into account the specific problems of the GCC team. We must extend AC_CHECK_FUNCS in order to use the headers instead of fake declarations as we currently do. Default headers could be triggered on when C99, but not with the other languages? At the end, we should have a simple macro, such as AC_LANG_COMPILER for instance, which is built over simpler macros. Each language support should come with these simpler macros, but each language should follow the same process. We also need to check the srcext which are supported by the compiler. In fact, this macro is also probably the right place to check for objext and exeext. ** AC_PROG_CC_STDC Should be: AC_PROG_CC_ISO? Or even more specific for the ISO version? Should include more tests (e.g., AC_C_CONST etc.)? See Peter for very useful comments on the technology. Should we make this a new language? AC_LANG(ISO C). It would be great to introduce AC_LANG_COMPILER in this release too. ** autoupdate We should probably install the files which do not depend upon the user, just the Autoconf library files. But conversely autoupdate must be opened to user macros, i.e., for instance libtool itself must be able to say that AM_PROG_LIBTOOL is now AC_PROG_LIBTOOL, and have autoupdate do its job on old configure.ac. * Even later ** Pentateuch Heck, there is nothing after `Deuteronomy'! We're stuck, but we _must_ update the `history' section. Can't go to `New testament', we might hurt feelings? In addition, it means that the Messiah has come, which might be slightly presumptuous :). Still, someone fluent in English should write it. ** AC_PATH_X Hi Robert, > Hi, autoconf people. While packaging plotutils-2.2 (just released), > I noticed what looks like a small error in the autoconf-2.13 texinfo > documentation, the entry for AC_PATH_XTRA, in particular. > The documentation says that AC_PATH_XTRA > ... adds the C compiler flags that X needs to output variable > `X_CFLAGS', and the X linker flags to `X_LIBS'. If X is not > available, adds `-DX_DISPLAY_MISSING' to `X_CFLAGS'. > It doesn't seem to add -DX_DISPLAY_MISSING to X_CFLAGS. X_DISPLAY_MISSING > ends up defined in config.h, instead. That's only because you're no doubt using AC_CONFIG_HEADER(..) to send your defines to a config.h-style file. If you were to not use AC_CONFIG_HEADER and X was not available, then you would see -DX_DISPLAY_MISSING being added to @DEFS@ as your output files were being generated. But you are right--the documentation is not clear about this. I'll change it. > In fact it looks to me as if right now, X_CFLAGS is used only for > specifying directories where X include files are stored, via the `-I' option. > Maybe it should really be called X_CPPFLAGS? Well, perhaps. If you feel strongly about this, feel free to submit a change-request. There is a hyperlink to the bug tracking database from http://sourceware.cygnus.com/autoconf/. With the way it reads in the manual right now, it's designed to allow the user to set additional flags in the environment prior to running configure--and these don't need to be limited to just -I flags. Nevertheless, I can see a few clean ways to improve this. ** AC_SYS_INTERPRETER Defines $interpval. This is not a standard name. Do we want to keep this? Clarify our policy on those names. ** Allow --recursive to config.status So that --recheck does not pass --no-recursive to configure. * autoconf.texi Move the specific macro documentation blocks into the source files, and use a doc-block extraction/merge technique to get documentation into texi-file. This should help avoid bit-rot in the doc, and make the doc easier to update when people add/change macros. The name "autodoc" is probably already taken so we probably need another one. ------------------------------------------------------------------------------ * m4 ** I18n The error messages for indir and dumpdef are uselessly different. Fix this for translators. ** Tracing `builtin' F**k! --trace FOO does not catch indir([FOO], $@)! Fixed in M4 1.6, but we can't rely on it yet. ** m4 loops As of 2.63, m4_for has a fixed iteration count for speed in the common usage case. But it used to allow the user to alter iteration count by reassigning the iterator, allowing a break-like functionality (or even infloops). Does this need a new (but maybe slower) macro? Should we also provide something like m4_while([TEST], [EXPR])? Maybe an m4_break() that works inside a looping construct? http://lists.gnu.org/archive/html/autoconf-patches/2008-08/msg00121.html * Autoconf 3 ** Cache name spaces. Cf the discussion with Kaveh. One would like to AC_CHECK_FUNCS(bar) # Do something that changes the environment AC_CACHE_PUSH(foo) AC_CHECK_FUNCS(bar) AC_CACHE_POP in order not to erase the results of a check with another. ** Cache var names should depend upon the current language. ** Use m4 lists? I think one sad decision in Autoconf was to use white space separated lists for some arguments. For instance AC_CHECK_FUNCS(foo bar). I tend to think that, even if it is not as nice, we should use m4 lists, i.e., AC_CHECK_FUNCS([foo, bar]) in this case. This would ease specializing loops, and more importantly, make them much more robust. A typical example of things that can be performed if we use m4 lists instead of white space separated lists is the case of things that have a space in their names, eg, structures. With the current scheme it would be extremely difficult to loop over AC_CHECK_STRUCTS(struct foo struct bar), while it natural and well defined for m4 lists: AC_CHECK_STRUCTS([struct foo, struct bar]). I know that makes a huge difference in syntax, but a major release should be ready to settle a new world. We *can* provide helping tools for the transition. Considering the benefits, I really think it is worth thinking. --akim ** Forbid shell variables as main arguments The fact that we have to support shell variables as main argument forbids many interesting constructions (specialization are not always possible, equally for AC_REQUIRE'ing macros *with their arguments*). Any loop should be handled by m4 itself, and nothing should be hidden to it. As a consequence, shell variables on the main arguments become useless (the main reason we support shell variables is to allow the loop versions of single argument macros, eg, to go from AC_CHECK_FUNC to AC_CHECK_FUNCS). --akim ** Use the @SUBST@ technology also for headers instead of #undef. This requires that acconfig.h becomes completely obsolete: autoheader should generate all the templates. ** Specializing loops. For instance, make AC_CHECK_FUNC[S] automatically use any particular macros for the listed functions. This requires to obsolete the feature `break' in ACTION-IF, since all the loops are to be handled by m4, not sh. ** Faces of a test Each macro can potentially come with several faces: of course the configure snippet (AC_foo), a config.h snippet (AH_foo), a system.h snippet (AS_foo), documentation (AD_foo) and, why not, the some C code for instance to replace a function. The motivation for the `faces' is to encapsulate. It is abnormal that once one has a configure macro, then she has to read somewhere to find the piece of system.h to use etc. The macros should come in a self-contained way, or, said it another way, PnP. A major issue is that of specialization. AC_CHECK_HEADER (or another name) for instance, will have as an effect, via system.h to include the header. But if the test for the header is specific, the generic AS_CHECK_HEADER will still be used. Conversely, some headers may not require a specific AC_ tests, but a specialized AS_ macro. ------------------------------------------------------------------------------ * Make AC_CHECK_LIB check whether the function is already available before checking for the library. This might involve adding another kind of cache variable to indicate whether a given function needs a given library. The current ac_cv_func_ variables are intended to indicate whether the function is in the default libraries, but actually also take into account whatever value LIBS had when they were checked for. Isn't this the issue of AC_SEARCH_LIB? --akim How come the list of libraries to browse not an additional parameter of AC_CHECK_FUNC, exactly like for the headers? --akim ------------------------------------------------------------------------------ * Select the right CONFIG_SHELL automatically (for Ultrix, Lynx especially.) ------------------------------------------------------------------------------ * Doc: Centralize information on POSIX, MS-DOS, cross-compiling, and other important topics. ------------------------------------------------------------------------------ * Mike Haertel's suggestions: ** Cross compiling: *** Error messages include instructions for overriding defaults using config.site. *** Distribute a config.site corresponding to a hypothetical bare POSIX system with c89. ** Site defaults: *** Convention for consistency checking of env vars and options in config.site so config.site can print obnoxious messages if it doesn't like options or env vars that users use. ------------------------------------------------------------------------------ * Look at user contributed macros: IEEE double precision math more ------------------------------------------------------------------------------ * Provide a way to create a config.h *and* set the DEFS variable from within the same configure script. ------------------------------------------------------------------------------ In config.status comment, put the host/target/build types, if used. ------------------------------------------------------------------------------ It would be nice if I could (in the Makefile.in files) set the relative name of config.h. You have config.h ../config.h ../../config.h's all over the place, in the findutils-4.1 directory. From: "Randall S. Winchester" <rsw@eng.umd.edu> ------------------------------------------------------------------------------ ls -lt configure configure.in | sort doesn't work right if configure.in is from a symlink farm, where the symlink has either a timestamp of its own, or under BSD 4.4, it has the timestamp of the current directory, neither of which helps. Changing it to ls -Llt configure configure.in | sort works for me, though I don't know how portable that is _Mark_ <eichin@cygnus.com> ------------------------------------------------------------------------------ Here is the thing I would like the most; AC_PKG_WITH(PACKAGE, HELP_STRING, PACKAGE-ROOT, PACKAGE-LIBS, PACKAGE-DEFS, PACKAGE-CCPFLAGS) like AC_PKG_WITH(kerberos,,/usr/local/athena,-lkrb -ldes,[KERBEROS KRB4 CRYPT],include) AC_PKG_WITH(hesiod, [if hesiod is not in kerberos-root add --with-hesiod-root=somewhere] ,,-lhesiod,HESIOD,,) AC_PKG_WITH(glue,,,-lglue,GLUE,,) AC_PKG_WITH(bind,,/usr/local/bind, [lib/resolv.a lib/lib44bsd.a], ,include) After the appropriate checks, the existence of the files, and libs and such LIBS=$LIBS $PKG-LIBS DEFS=$DEFS $PKG-DEFS CPPFLAGS=$PKG-CPPFLAGS $CPPFLAGS $PKG-ROOT=$PKG-ROOT The cppflags should reverse the order so that you can have; -I/usr/local/bind/include -I/usr/local/athena/include and -L/usr/local/athena/lib -lkrb -ldes /usr/local/bind/lib/libresolv.a as order matters. also an AC_PKG_CHK_HEADER and an AC_PKG_CHK_FUNCTION so one can give alternate names to check for stuff ($PKG-ROOT/lib for example) From: Randall Winchester ------------------------------------------------------------------------------ AC_C_CROSS assumes that configure was called like 'CC=target-gcc; ./configure'. I want to write a package that has target dependent libraries and host dependent tools. So I don't like to lose the distinction between CC and [G]CC_FOR_TARGET. AC_C_CROSS should check for equality of target and host. It would be great if GCC_FOR_TARGET AR_FOR_TARGET RANLIB_FOR_TARGET would be set automatically if host != target. AC_LANG_CROSS_C would be nice too, to check header files etc. with GCC_FOR_TARGET instead of CC Here is one simple test if test "x$host" != "x$target"; then AC_CHECK_PROGS(AR_FOR_TARGET, [$target-ar, $prefix/$target/bin/ar], $target-ar) AC_CHECK_PROGS(RANLIB_FOR_TARGET, $target-ranlib, $target-ranlib) [$target-ranlib, $prefix/$target/bin/ranlib], $target-ranlib) AC_CHECK_PROGS(GCC_FOR_TARGET, $target-gcc, $target-gcc) [$target-gcc, $prefix/$target/bin/gcc], $target-gcc) fi From: nennker@cs.tu-berlin.DE (Axel Nennker) (also look in the autoconf mailing list archives for the proposed CHECK_TARGET_TOOL macro from Natanael Nerode, a gcc configury guru). ------------------------------------------------------------------------------ The problem occurs with the following libc functions in SunOS 5.4: fnmatch glob globfree regcomp regexec regerror regfree wordexp wordfree It also occurs with a bunch more libposix4 functions that most people probably aren't worried about yet, e.g. shm_open. All these functions fail with errno set to ENOSYS (89) ``Operation not applicable''. Perhaps Autoconf should have a specific macro for fnmatch, another for glob+globfree, another for regcomp+regexec+regerror+regfree, and another for wordexp+wordfree. This wouldn't solve the problem in general, but it should work for Solaris 2.4. Or Autoconf could limit itself to fnmatch and regcomp, the only two functions that I know have been a problem so far. From Paul Eggert. ------------------------------------------------------------------------------ Make easy macros for checking for X functions and libraries, such as Motif. ------------------------------------------------------------------------------ There are basically three ways to lock files lockf, fnctl, flock I'd be interested in adding a macro to pick the "right one" if you're interested. From: Rich Salz <rsalz@osf.org> ------------------------------------------------------------------------------ Timezone calculations checks. ------------------------------------------------------------------------------ Support different default file system layouts, e.g. SVR4, Linux. Of course, this can be done locally with config.site. ------------------------------------------------------------------------------ I wonder if it is possible to get the name of X11's app-defaults directory by autoconf. Moreover, I'd like to have a general way of accessing imake variables by autoconf, something like AC_DEFINE(WINE_APP_DEFAULTS, AC_IMAKE_VAR(XAPPLOADDIR)) Slaven Rezic <eserte@cabulja.herceg.de> ------------------------------------------------------------------------------ Every user running X11 usually has a directory like *X11* in his PATH variable. By replacing bin by include, you can find good places to look for the include files or libraries. From: rcb5@win.tue.nl (Richard Verhoeven) ------------------------------------------------------------------------------ In most cases, when autoscan suggests something, using the search or index command into the Info reader for autoconf manual quickly explains me what the test is about. However, for header files and functions, the search might fail, because the test is not of the specific kind. The Autoconf manual should reflect somewhere all header files or functions (non-specific features, generally) triggering autoscan to generate tests, and tell in a few words what is the problem, and the suggested approach for a solution; that is, how one should use the result of testing the feature. From: pinard@iro.umontreal.ca ------------------------------------------------------------------------------ It would be nice if the configure script would handle an option such as --x-libraries="/usr/openwin/lib /usr/dt/lib". Rick Boykin <rboykin@cscsun3.larc.nasa.gov> Under Solaris 2.4, the regular X includes and libs and the Motif includes and libs are in different places. The Emacs configure script actually allows dir1:dir2:dir3 -- if test "${x_libraries}" != NONE && test -n "${x_libraries}"; then LD_SWITCH_X_SITE=-L`echo ${x_libraries} | sed -e "s/:/ -L/g"` LD_SWITCH_X_SITE_AUX=-R`echo ${x_libraries} | sed -e "s/:/ -R/g"` fi if test "${x_includes}" != NONE && test -n "${x_includes}"; then C_SWITCH_X_SITE=-I`echo ${x_includes} | sed -e "s/:/ -I/g"` fi ------------------------------------------------------------------------------ What messages should be produced by default, if any? Probably only the few most important ones, like which configuration name was used, whether X or Xt are in use, etc. The specific decisions, and progress messages, should be recorded on the terminal only if --verbose is used. --silent just suppresses the "checking for...result" messages, not the "creating FOO" messages. I think the default should be to suppress both. From: Richard Stallman <rms@gnu.ai.mit.edu> There is no distinction now between important decisions (we have X) vs minor decisions (we have lstat). However, there are probably only a few things you deem important enough to announce and only those few things will need to be changed. Perhaps config.status could be written with comments saying what was decided. From: Roland McGrath <roland@gnu.ai.mit.edu> ------------------------------------------------------------------------------ Another thing I wish for is a macro which figures out which libraries are needed for BSD-style sockets. AC_PATH_X already detects this correctly...so it's just a matter of separating out the socket-related code. From: "Joel N. Weber II" <nemo@koa.iolani.honolulu.hi.us> ------------------------------------------------------------------------------ in order to use the AC_CANONICAL_SYSTEM macro, I have to have install-sh somewhere nearby --- why is this? I have no real reason to distribute install-sh, other than that its absence breaks this code. Shouldn't the above loop be looking for config.sub and config.guess? From: jimb@totoro.bio.indiana.edu (Jim Blandy) adding AC_CANONICAL_HOST to my configure.in script caused all sorts of odd/unexplained errors. Obviously, I had to go get copies of config.guess, config.sub and install-sh from the autoconf distribution, but the error messages and autoconf docs didn't explain that very well. From: bostic@bsdi.com (Keith Bostic) ------------------------------------------------------------------------------ Perhaps also have AC_TRY_COMPILER try to link an invalid program, and die if the compiler seemed to succeed--in which case it's not usable with autoconf scripts. ------------------------------------------------------------------------------ Copyright (C) 1994-1996, 1999-2002, 2007-2012 Free Software Foundation, Inc. Copying and distribution of this file, with or without modification, are permitted in any medium without royalty provided the copyright notice and this notice are preserved. This file is offered as-is, without warranty of any kind. PK [�!\B�j �> �> NEWSnu �[��� GNU Autoconf NEWS - User visible changes. * Noteworthy changes in release 2.69 (2012-04-24) [stable] ** Autoconf now requires perl 5.6 or better (but generated configure scripts continue to run without perl). * Noteworthy changes in release 2.68b (2012-03-01) [beta] Released by Eric Blake, based on git versions 2.68.*. ** Autoconf-generated configure scripts now unconditionally re-execute themselves with $CONFIG_SHELL, if that's set in the environment. ** The texinfo documentation no longer specifies "front-cover" or "back-cover" texts, so that it may now be included in Debian's "main" section. ** Support for the Go programming language has been added. The new macro AC_LANG_GO sets variables GOC and GOFLAGS. ** AS_LITERAL_IF again treats '=' as a literal. Regression introduced in 2.66. ** The macro AS_EXECUTABLE_P, present since 2.50, is now documented. ** Macros - AC_PROG_LN_S and AS_LN_S now fall back on 'cp -pR' (not 'cp -p') if 'ln -s' does not work. This works better for symlinks to directories. - New macro AC_HEADER_CHECK_STDBOOL. - New and updated macros for Fortran support: AC_FC_CHECK_BOUNDS to enable array bounds checking AC_F77_IMPLICIT_NONE and AC_FC_IMPLICIT_NONE to disable implicit integer AC_FC_MODULE_EXTENSION to compute the Fortran 90 module name extension AC_FC_MODULE_FLAG for the Fortran 90 module search path flag AC_FC_MODULE_OUTPUT_FLAG for the Fortran 90 module output directory flag AC_FC_PP_SRCEXT for preprocessed Fortran source files extensions AC_FC_PP_DEFINE for the Fortran preprocessor define flag * Noteworthy changes in release 2.68 (2010-09-22) [stable] Released by Eric Blake, based on git versions 2.67.*. ** AC_MSG_ERROR (and AS_ERROR) can once again be followed immediately by `dnl'. Regression introduced in 2.66. ** AC_INIT again allows URLs with '?' for its BUG-REPORT argument. Regression introduced in 2.66. ** AC_REPLACE_FUNCS again allows a non-literal argument, such as a shell variable that expands to a list of functions to check. Regression introduced in 2.66. ** AT_BANNER() with empty argument will cause visual separation from previous test category. ** The macros AC_PREPROC_IFELSE, AC_COMPILE_IFELSE, AC_LINK_IFELSE, and AC_RUN_IFELSE now warn if the first argument failed to use AC_LANG_SOURCE or AC_LANG_PROGRAM to generate the conftest file contents. A new macro AC_LANG_DEFINES_PROVIDED exists if you have a compelling reason why you cannot use AC_LANG_SOURCE but must avoid the warning. ** The macro m4_define_default is now documented. ** Symlinked config.cache files are supported; configure now tries to update non-symlinked cache files atomically, so that concurrent configure runs do not leave behind broken cache files. It is still unspecified which subset or union of results is cached though. ** Autotest testsuites should not contain long text lines any more, and be portable even when very many test groups are used. ** AT_CHECK semantics with respect to the Autotest variable $at_status and shell execution environment of the arguments are documented now. ** AC_FC_LIBRARY_LDFLAGS now tolerates output from newer gfortran. ** Newly obsolete macros The following macros have been marked obsolete. New programs should use the corresponding Gnulib modules. Gnulib not only detects a larger set of portability problems with these functions, but also provides complete workarounds. AC_FUNC_ERROR_AT_LINE AC_FUNC_LSTAT_FOLLOWS_SLASHED_SYMLINK AC_FUNC_MKTIME AC_FUNC_STRTOD * Major changes in Autoconf 2.67 (2010-07-21) [stable] Released by Eric Blake, based on git versions 2.66.*. ** AC_CONFIG_SUBDIRS with more than one subdirectory at a time works again. Regression introduced in 2.66. ** AC_CHECK_SIZEOF of a pointer type works again. Regression introduced in 2.66. ** New macro AC_FC_LINE_LENGTH to accept long Fortran source code lines. ** AC_PREPROC_IFELSE now keeps the preprocessed output in the conftest.i file for inspection by the commands in the ACTION-IF-TRUE argument. ** AC_INIT again allows parentheses and other characters that are literal in single- or double-quoted strings, and in quoted and unquoted here-documents, for its PACKAGE and VERSION arguments. Regression introduced in 2.66. ** autoreconf passes warning flags to new enough versions of aclocal. ** Running an Autotest testsuite in parallel mode no longer triggers a race condition that could cause the testsuite run to end early, fixing a sporadic failure in autoconf's own testsuite. Bug present since introduction of parallel tests in 2.63b. * Major changes in Autoconf 2.66 (2010-07-02) [stable] Released by Eric Blake, based on git versions 2.65.*. ** AC_FUNC_MMAP works in C++ mode again. Regression introduced in 2.65. ** Use of m4_divert without a named diversion now issues a syntax warning, since it is seldom right to change diversions behind autoconf's back. ** The macros AC_TYPE_INT8_T, AC_TYPE_INT16_T, AC_TYPE_INT32_T, and AC_TYPE_INT64_T work again. Regression introduced in 2.65. ** AC_PROG_INSTALL correctly uses `shtool' again. Regression introduced in 2.64. ** Autoconf should work on EBCDIC hosts. ** AC_CHECK_DECL and AC_CHECK_DECLS accept optional function argument types for overloaded C++ functions. ** AS_SET_CATFILE accepts nonliterals in its variable name argument now. ** Autotest testsuites accept an option --recheck to rerun tests that failed or passed unexpectedly during the last non-debug testsuite run. ** AC_ARG_ENABLE and AC_ARG_WITH now also accept `+' signs in `--enable-*' and `--with-*' arguments, converting them to underscores for the variable names. ** In configure scripts, loading CONFIG_SITE no longer searches PATH, and problems in loading the configuration site files are diagnosed. ** Autotest testsuites may optionally provide colored test results. ** The previously undocumented Autotest macros AT_ARG_OPTION and AT_ARG_OPTION_ARG have seen bug fixes and are documented now. AT_ARG_OPTION has been changed in that the negative of a long option --OPTION is now --no-OPTION rather than --noOPTION. ** The macro AS_LITERAL_IF is slightly more conservative; text containing shell quotes are no longer treated as literals. Furthermore, a new macro, AS_LITERAL_WORD_IF, adds an additional level of checking that no whitespace occurs in literals. ** The macros AS_TR_SH and AS_TR_CPP no longer expand their results. ** The following macros are now documented: AS_BOX ** New macro AC_FC_FIXEDFORM to accept fixed-form Fortran. * Major changes in Autoconf 2.65 (2009-11-21) [stable] Released by Eric Blake, based on git versions 2.64.*. ** Autoconf is now licensed under the General Public License version 3 or later (GPLv3+). As with earlier versions, the license includes an exception clause so that you may release a configure script generated by autoconf under the license of your own program. ** New macros to support Objective C++. AC_PROG_OBJCXX AC_PROG_OBJCXXCPP ** The following undocumented autoconf macros, removed in Autoconf 2.64, have been reinstated: AH_CHECK_HEADERS These macros are present only for backwards compatibility purposes. ** The macro AC_LANG_COMPILER no longer fails on embedded systems that lack fopen in the C library, such as AVR or RTEMS (regression introduced in 2.64). ** The AC_FC_FREEFORM macro no longer suffers from a whitespace bug that made it fail with some Fortran compilers (regression introduced in 2.64). ** The AC_TYPE_UINT64_T and AC_TYPE_INT64_T macros have been fixed to no longer mistakenly select a 32-bit type on some compilers (bug present since macros were introduced in 2.59c). ** The AC_FUNC_MMAP macro has been fixed to be portable to systems like Cygwin (bug present since macro was introduced in 2.0). ** The following documented autotest macros are new: AT_CHECK_EUNIT ** The following m4sugar macros now quote their expansion: m4_toupper m4_tolower ** The following m4sugar macros are new: m4_escape ** The m4sugar macro m4_text_wrap now copes with embedded quoting without requiring quadrigraphs. For uses like AC_ARG_VAR([a], [[b c]]), this gives the intuitive behavior of "[b c]" in the output (2.63 gave the output of "[b], [c]", and 2.64 encountered a failure). ** The `$tmp' temporary directory used in config.status is documented for public use now. ** config.status now provides a --config option to produce the configuration. ** Many cache variables used by Autoconf's macros are now documented. ** Configure scripts work better on DJGPP by avoiding a bug present in the DJGPP port of bash 2.04 in handling 'return' in a shell function (regression introduced in 2.64). * Major changes in Autoconf 2.64 (2009-07-26) [stable] Released by Eric Blake, based on git versions 2.63b.*. ** Autoconf now requires GNU M4 1.4.6 or later. Earlier versions of M4 have a bug in regular expression handling that interferes with some of the speedups provided since Autoconf 2.63. GNU M4 1.4.13 or later is recommended. ** AS_IF and AS_CASE have been taught to avoid syntax errors even when given arguments that expand to just whitespace. ** The following documented autoconf macros are new: AC_ERLANG_SUBST_ERTS_VER ** The autoheader tool now understands m4 macro arguments passed to AC_DEFINE and AC_DEFINE_UNQUOTED. ** Ensure AT_CHECK can support commands that include a # given with proper m4 quoting. For shell comments, this is a new feature; for non-shell comments, this fixes a regression introduced in 2.63b. Additionally, AT_CHECK correctly supplies shell escapes for metacharacters occurring in m4 macro expansions within the expected stdout and stderr parameters. ** The macro AT_CHECK now understands the concept of hard failure. If a test exits with an unexpected status 99, cleanup actions for the test are inhibited and the test is treated as a failure regardless of AT_XFAIL_IF. It also understands the new directives ignore-nolog, stdout-nolog, and stderr-nolog. ** The following documented autotest macros are new: AT_CHECK_UNQUOTED AT_FAIL_IF AT_SKIP_IF ** The following documented m4sugar macros are new: m4_argn m4_copy_force m4_default_nblank m4_default_nblank_quoted m4_ifblank m4_ifnblank m4_rename_force ** The autoconf testsuite now exercises all Erlang macros. * Major changes in Autoconf 2.63b (2009-03-31) [beta] Released by Eric Blake, based on git versions 2.63.*. ** The manual is now shipped under the terms of the GNU FDL 1.3. ** AC_REQUIRE now detects the case of an outer macro which first expands then later indirectly requires the same inner macro. Previously, this case led to silent out-of-order expansion (bug present since 2.50); it now issues a syntax warning, and duplicates the expansion of the inner macro to guarantee dependencies have been met. See the manual for advice on how to refactor macros in order to avoid the bug in earlier autoconf versions and avoid increased script size in the current version. ** AC_DEFUN_ONCE has improved semantics. Previously, a macro declared with AC_DEFUN_ONCE warned on a second invocation; and out-of-order expansion was still possible. Now, dependencies are guaranteed, and subsequent invocations are a silent no-op. This makes AC_DEFUN_ONCE an ideal macro for silencing AC_REQUIRE warnings. ** The following macros are now defined with AC_DEFUN_ONCE. This means a subtle change in semantics; previously, an AC_DEFUN macro could expand one of these macros multiple times or surround the macro inside shell conditional text to bypass the effects of these macros, but now the macro will expand exactly once, and prior to the start of any enclosing AC_DEFUN macro: AC_CANONICAL_BUILD AC_CANONICAL_HOST AC_CANONICAL_TARGET AC_HEADER_ASSERT AC_PROG_INSTALL AC_PROG_MKDIR_P AC_USE_SYSTEM_EXTENSIONS ** AC_LANG_ERLANG works once again (regression introduced in 2.61a). ** AC_HEADER_ASSERT is fixed so that './configure --enable-assert' no longer mistakenly disables assertions. ** AC_INIT now takes an optional fifth parameter that can be used to set AC_PACKAGE_URL, a URL for the package's home page; the URL is used in `configure --help' and is also available via AC_DEFINE. ** Autotest testsuites accept an option --jobs[=N] for parallel testing. This feature is still in testing, and may not work on every platform, help in improving it would be appreciated. ** Autotest testsuites do not attempt to write startup error messages to the log file before that is opened (regression introduced in 2.63). ** Configure scripts now use shell functions. This feature leads to smaller configure files and faster execution. ** Present But Cannot Be Compiled: Autoconf will now proceed with the compiler's result if a header is present but cannot be compiled. The warning is still printed, and you should really fix it by providing a fourth parameter to AC_CHECK_HEADER/AC_CHECK_HEADERS. ** Autoreconf added aclocal to the set of programs affected by the `autoreconf -I dir' option. ** The following documented m4sugar macros are new: m4_chomp m4_chomp_all m4_cleardivert m4_curry m4_default_quoted m4_esyscmd_s m4_map_args m4_map_args_pair m4_map_args_sep m4_map_args_w m4_set_map m4_set_map_sep m4_stack_foreach m4_stack_foreach_lifo m4_stack_foreach_sep m4_stack_foreach_sep_lifo ** The following m4sugar macros are documented now, but in some cases with slightly different semantics than what the previous undocumented version had: m4_copy m4_dumpdefs m4_rename m4_version_prereq ** The m4sugar macro m4_expand has been taught to handle unterminated comments and shell case statements. As a result, it is used internally in more places, such as AC_DEFINE and AT_CHECK. Most uses of AC_DEFINE and AT_CHECK should not behave any differently; however, it may be necessary to add double-quoting around unbalanced `(' where single-quoting used to be sufficient. ** The following documented m4sh macros are new: AS_INIT_GENERATED AS_LINENO_PREPARE AS_ME_PREPARE AS_SET_STATUS AS_VAR_APPEND AS_VAR_ARITH AS_VAR_COPY ** The following m4sh macros are documented now, but in some cases with slightly different semantics than what the previous undocumented version had: AS_ECHO AS_ECHO_N AS_ESCAPE AS_EXIT AS_LITERAL_IF AS_UNSET AS_VAR_IF AS_VAR_POPDEF AS_VAR_PUSHDEF AS_VAR_SET AS_VAR_SET_IF AS_VAR_TEST_SET AS_VERSION_COMPARE ** The m4sh macros AS_IF and AS_CASE can now be used in shell lists. The responsibility for supplying a trailing newline now belongs to the call site, but since most users did not add dnl, this generally results in fewer empty lines in configure. * Major changes in Autoconf 2.63 (2008-09-09) [stable] Released by Eric Blake, based on git versions 2.62.*. ** AC_C_BIGENDIAN does not mistakenly report "universal" for some bigendian hosts, a regression introduced with universal binary support in 2.62. ** AC_PATH_X now includes /lib64 and /usr/lib64 in its list of default library directories. ** AC_USE_SYSTEM_EXTENSIONS no longer conflicts with an external AC_DEFINE([__EXTENSIONS__]). This fixes a regression introduced in 2.62 when using macros such as AC_AIX that were made obsolete in favor of the more portable AC_USE_SYSTEM_EXTENSIONS. ** AC_CHECK_TARGET_TOOLS is usable in the non-cross-compile case. ** Newly obsolete macros The following macro has been marked obsolete, since current porting targets can safely assume C89 semantics that signal handlers return void. We have no current plans to remove the macro. AC_TYPE_SIGNAL ** The macros m4_map and m4_map_sep now ignore any list elements consisting of just empty quotes, and m4_map_sep now expands its separator. This fixes a regression in 2.62 when these macros were first documented, for the sake of clients expecting the semantics that these macros had prior to that time. The new macros m4_mapall and m4_mapall_sep, along with extra quoting of the separator, can be used to get the semantics that m4_map_sep had in 2.62. ** Clients of m4_expand, such as AS_HELP_STRING and AT_SETUP, can now handle properly quoted but otherwise unbalanced parentheses (for some macros, this fixes a regression in 2.62). ** Two new quadrigraphs have been introduced: @{:@ for (, and @:}@ for ), allowing the output of unbalanced parentheses in more contexts. ** The following m4sugar macros are new: m4_cleardivert m4_joinall m4_mapall m4_mapall_sep m4_reverse m4_set_add m4_set_add_all m4_set_contains m4_set_contents m4_set_delete m4_set_difference m4_set_dump m4_set_empty m4_set_foreach m4_set_intersection m4_set_list m4_set_listc m4_set_remove m4_set_size m4_set_union ** The following m4sugar macros now accept multiple arguments, as is the case with underlying m4: m4_defn m4_popdef m4_undefine ** The following m4sugar macros now guarantee linear scaling; they previously had linear scaling with m4 1.6 but quadratic scaling when using m4 1.4.x. All macros built on top of these also gain the scaling improvements. m4_bmatch m4_bpatsubsts m4_case m4_cond m4_do m4_dquote_elt m4_foreach m4_join m4_list_cmp m4_map m4_map_sep m4_max m4_min m4_shiftn ** AT_KEYWORDS once again performs expansion on its argument, such that AT_KEYWORDS([m4_if([$1], [], [default])]) no longer complains about the possibly unexpanded m4_if [regression introduced in 2.62]. ** Config header templates `#undef UNDEFINED /* comment */' do not lead to nested comments any more; regression introduced in 2.62. * Major changes in Autoconf 2.62 (2008-04-05) [stable] Released by Eric Blake, based on git versions 2.61a.*. ** Many optimizations have been applied to make overall execution faster. ** Autotest now makes use of shell functions. ** config.status now uses awk instead of sed also for config headers. - As a side effect, AC_DEFINE and AC_DEFINE_UNQUOTED now handle multi-line values, i.e., backslash-newline combinations are handled correctly. Further, for config headers, the total size of values is not limited by the POSIX length limit of text lines any more, only each single line. ** New config variable `top_build_prefix'. ** New Autoconf macros: AC_AUTOCONF_VERSION AC_OPENMP AC_PATH_PROGS_FEATURE_CHECK ** AC_C_BIGENDIAN now supports universal binaries a la Mac OS X. ** AC_C_RESTRICT now prefers to #define 'restrict' to a variant spelling like '__restrict' if the variant spelling is available, as this is more likely to work when mixing C and C++ code. ** AC_CHECK_ALIGNOF's type argument T is now documented better: it must be a string of tokens such that "T y;" is a valid member declaration in a struct. ** AC_CHECK_SIZEOF now accepts objects as well as types: the general rule is that sizeof (X) works, then AC_CHECK_SIZEOF (X) should work. ** AC_CHECK_TYPE and AC_CHECK_TYPES now work on any C type-name; formerly, they did not work for function types. In C++, they now work on any type-id that can be the operand of sizeof; this is similar to C, except it excludes anonymous struct and union types. Formerly, some (but not all) C++ types involving anonymous struct and union were accepted, though this was not documented. ** AC_CONFIG_LINKS now prefers to link against files in the build tree if found, and it works to link against a file of the same name in the source tree, even if both trees coincide. ** AC_INIT no longer alters $@; regression introduced in 2.60. ** AC_USE_SYSTEM_EXTENSIONS now defines _ALL_SOURCE for Interix platforms. ** AS_HELP_STRING no longer underquotes its first argument; it also handles the case where the first argument contains single-quoted commas. For example, "AS_HELP_STRING([-a, [--arg[=foo]]], [bar])" produces: " -a, --arg[=foo] bar" Additionally, the macro now takes two additional arguments, indent-column and wrap-column; these should not normally be needed, but can be used to fine-tune how the output text is wrapped. ** AC_PROG_INSTALL now requires an install program that can install multiple files into a target directory. ** The command 'autoconf -' now correctly processes a file from stdin. ** 'autoreconf -m' now honors $MAKE. ** For all of the directory arguments for 'configure', such as '--prefix' or '--bindir', trailing slashes are stripped. As an example, if tab completion in the user's shell appends trailing slashes, the command './configure --prefix=/usr/' will still result in an expanded libdir value of /usr/lib, not /usr//lib. ** `configure --help=recursive' now works in read-only trees and from unconfigured build trees. ** If precious variables differ only in whitespace, then the cache consistency check warns instead of fails, and reuses the old value. ** AT_BANNER is now documented. ** AT_SETUP now handles macro expansions properly when calculating line length. ** Autotest now determines $srcdir correctly. ** Testsuites built by autotest now accept a -C/--directory=DIR option to adjust the working directory prior to creating files. ** Autoconf now requires GNU M4 1.4.5 or later. Earlier versions of M4 have a bug in macro tracing that interferes with the interaction between Autoconf and Automake. GNU M4 1.4.11 or later is recommended. The configure search for a working M4 is improved. ** For portability with the eventual M4 2.0, macros should no longer use anything larger than $9 to refer to arguments. ** Documentation for m4sugar is improved. - The following macros were previously available as undocumented interfaces; the macros are now documented as stable interfaces. __oline__ m4_assert m4_bmatch m4_bpatsubsts m4_car m4_case m4_cdr m4_default m4_divert_once m4_divert_pop m4_divert_push m4_divert_text m4_do m4_errprintn m4_fatal m4_flatten m4_ifndef m4_ifset m4_ifval m4_ifvaln m4_location m4_n m4_shiftn m4_strip m4_warn - The following macros were previously available as undocumented interfaces, but had bug fixes or semantic changes as part of this release. Packages that relied on the undocumented behavior should be analyzed to make sure they will still work with the new documented behavior. m4_cmp m4_list_cmp m4_join m4_map m4_map_sep m4_sign m4_text_box m4_text_wrap m4_version_compare - The m4_wrap macro used to have unspecified order, but now guarantees FIFO order. m4_wrap_lifo was added to guarantee LIFO order. - Packages using the undocumented m4sugar macro m4_PACKAGE_VERSION should consider using the new AC_AUTOCONF_VERSION instead. - m4sugar macros that are not documented in the manual are still deemed experimental, and should not be used outside of Autoconf. ** The m4sugar macros m4_append and m4_append_uniq, first documented in 2.60, have been fixed to treat both the string and the separator arguments consistently with regards to quoting. Prior to this fix, m4_append_uniq could mistakenly duplicate entries if the expansion of the separator resulted in a different string (for example, if it contained quotes, a comma, or a macro name). However, it means that programs previously using m4_append([name], [string], [[, ]]) are now using a four-character separator instead of the intended comma and space. If you need portability to earlier versions of Autoconf, you can insert the following snippet after AC_INIT but before any other macro expansions, to enforce the new semantics: m4_pushdef([m4_append], [m4_define([$1], m4_ifdef([$1], [m4_defn([$1])[$3]])[$2])]) Additionally, m4_append_uniq now takes optional parameters that can be used to take action depending on whether anything was appended, and warns if a non-empty separator occurs within the string being appended, since that can lead to duplicates. ** The following m4sugar macros are new: m4_append_uniq_w m4_apply m4_combine m4_cond m4_count m4_dquote_elt m4_echo m4_expand m4_ignore m4_make_list m4_max m4_min m4_newline m4_shift2 m4_shift3 m4_unquote m4_wrap_lifo ** Warnings are now generated by default when an installer invokes 'configure' with an unknown --enable-* or --with-* option. These warnings can be disabled with the new AC_DISABLE_OPTION_CHECKING macro, or by invoking 'configure' with --disable-option-checking. ** Existing obsolete macros The documentation for the following macros is adjusted to make it more clear that they have previously been marked obsolete, as their functionality can be accomplished by other macros. We have no current plans to remove them from Autoconf. AC_ENABLE AC_STRUCT_ST_BLKSIZE AC_STRUCT_ST_RDEV AC_WITH ** Newly obsolete macros The following macros have been marked obsolete, as they only perform a subset of AC_USE_SYSTEM_EXTENSIONS. We have no current plans to remove them. AC_AIX AC_GNU_SOURCE AC_ISC_POSIX AC_MINIX ** AC_C_LONG_DOUBLE is obsolescent. The documentation now says that AC_C_LONG_DOUBLE is obsolescent: it tests for problems that are so old that it is no longer of practical importance on current systems. New programs need not use AC_C_LONG_DOUBLE. We have no current plans to remove it. ** AC_DIAGNOSE, AC_WARNING, and AC_FATAL are obsolescent. The documentation now favors the use of M4sugar macros m4_warn and m4_fatal, since the naming makes it more obvious that the diagnostics are associated with M4 expansion (ie. when running `autoconf'), and offers less confusion with the AC_MSG_ERROR, AC_MSG_FAILURE, and AC_MSG_WARN macros which manage diagnostics when running `configure'. We have no current plans to remove these macros. * Major changes in Autoconf 2.61a (2006-12-11) ** AC_FUNC_FSEEKO was broken in 2.61; it didn't make fseeko and ftello visible on many platforms. This has been fixed. ** AC_FUNC_SETVBUF_REVERSED is now obsolete. It is still defined for backward compatibility but it does nothing. The macro was already obsolescent, as the last systems to have the problem were those based on SVR2, which became obsolete in 1987. The macro had bugs on some modern systems and could no longer be maintained reliably due to lack of ancient systems to test it on. ** config.status now uses awk instead of sed for most substitutions, for speed. - As a side effect multi-line values of substituted variables no longer have a small limit in total size, though for portability each line should not exceed the POSIX length limit for text lines. - It is now documented that Makefile.in should not contain overlapping variable occurrences, e.g., @VAR1@VAR2@. Autoconf's behavior was always iffy in such cases, and the awk implementation has changed the behavior. ** Many uses of 'echo' have been rewritten so that Autoconf-generated scripts have fewer problems with strings or file names containing embedded special characters such as backslash or leading "-". This was implemented by using `printf '%s\n' "$foo"' instead of `echo "$foo"' when printf works. Due to the implementation technique used, Autoconf-generated scripts now run considerably more slowly on ancient implementations lacking printf. However, this should not be a problem, since Autoconf-generated scripts in practice invariably find a more-modern shell these days. * Major changes in Autoconf 2.61 (2006-11-17) ** New macros AC_C_FLEXIBLE_ARRAY_MEMBER, AC_C_VARARRAYS. ** AC_ARG_ENABLE and AC_ARG_WITH now allow '.' in feature and package names. * Major changes in Autoconf 2.60b (2006-10-22) ** BIN_SH Autoconf-generated shell scripts no longer export BIN_SH, due to configuration hassles with this. Installers who need BIN_SH in their environment should set it before invoking 'configure' and 'make'. As far as we know, this affects only Unixware installations. ** Obsolescent macros The documentation now says that the following macros are obsolescent, as they are superseded by Gnulib: AC_FUNC_FNMATCH AC_FUNC_FNMATCH_GNU AC_FUNC_GETLOADVG AC_REPLACE_FNMATCH New programs should use the Gnulib counterparts of these macros. We have no current plans to remove them from Autoconf. ** AC_COMPUTE_INT no longer caches or reports results. ** AC_CHECK_DECL now also works with aggregate objects. ** AC_USE_SYSTEM_EXTENSIONS now defines _TANDEM_SOURCE for NonStop platforms. ** GNU M4 1.4.7 or later is now recommended. ** m4_mkstemp New M4sugar macro, which is more secure than the POSIX M4 maketemp. ** m4_maketemp Now an alias for m4_mkstemp. * Major changes in Autoconf 2.60a (2006-08-25) ** GNU M4 1.4.6 or later is now recommended. ** The check for C99 now tests for varargs macros, as documented. It also tests that the preprocessor supports 64-bit integers. ** Autoconf now uses constructs like "#ifdef HAVE_STDLIB_H" rather than "#if HAVE_STDLIB_H", so that it now works with "gcc -Wundef -Werror". ** The functionality of the undocumented _AC_COMPUTE_INT is now provided by a public and documented macro, AC_COMPUTE_INT. The parameters to the two macros are different, so autoupdate will not change the old private name to the new one. _AC_COMPUTE_INT may be removed in a future release. ** AC_TYPE_LONG_LONG_INT and AC_TYPE_UNSIGNED_LONG_LONG_INT now require that long long types be at least 64 bits wide, as C99 and tradition requires. Formerly, they accepted implementations of any width. * Major changes in Autoconf 2.60 Released 2006-06-23, by Ralf Wildenhues. ** Autoconf no longer depends on whether m4wrap is FIFO (as Posix requires) or LIFO (as in GNU M4 1.4.x). GNU M4 2.0 is expected to conform to Posix here, so m4wrap/m4_wrap users should no longer depend on LIFO behavior. ** Provide a way to turn off warnings about the changed directory variables. * Major changes in Autoconf 2.59d Released 2006-06-05, by Ralf Wildenhues. ** GNU make now recommended for VPATH builds INSTALL now suggests VPATH builds (e.g., "sh ../srcdir/configure") only if you use GNU make. In practice, other 'make' implementations have too many subtle incompatibilities in their support for VPATH. Many packages (including Autoconf itself) are portable to other 'make' implementations, but some packages are not, and recommending GNU make keeps the installation instructions simpler. ** Even more safety checks for the new Directory variables: Warn about suspicious `${datarootdir}' found in config files output. ** AC_TRY_COMMAND, AC_TRY_EVAL, ac_config_guess, ac_config_sub, ac_configure These never-documented macros and variables have been marked with comments saying that they may be removed in a future release, because their use can lead to unintended code being executed. If you need functionality that only these macros or variables currently supply, please write bug-autoconf@gnu.org. ** AC_SUBST, AC_DEFINE Literal arguments to these are passed to m4_pattern_allow now. ** AC_PROG_CC_STDC Passing 'ac_cv_prog_cc_stdc=no' to 'configure' now sets ac_cv_prog_cc_c99 and ac_cv_prog_cc_c89 to 'no' as well, for backward compatibility with obsolete K&R tests in the Automake test suite. ** AC_PROG_CXX_C_O New macro. ** AC_PROG_MKDIR_P New macro. ** AS_MKDIR_P Now more robust with special characters in file names, or when multiple processes create the same directory at the same time. ** Obsolescent macros The documentation now says that the following macros are obsolescent: they test for problems that are so old that they are no longer of practical importance on current systems. AC_C_BACKSLASH_A AC_FUNC_MEMCMP AC_HEADER_DIRENT AC_C_CONST AC_FUNC_SELECT_ARGTYPES AC_HEADER_STAT AC_C_PROTOTYPES AC_FUNC_SETPGRP AC_HEADER_STDC AC_C_STRINGIZE AC_FUNC_SETVBUF_REVERSED AC_HEADER_SYS_WAIT AC_C_VOLATILE AC_FUNC_STAT AC_HEADER_TIME AC_FUNC_CLOSEDIR_VOID AC_FUNC_STRFTIME AC_ISC_POSIX AC_FUNC_GETPGRP AC_FUNC_UTIME_NULL AC_PROG_GCC_TRADITIONAL AC_FUNC_LSTAT AC_FUNC_VPRINTF AC_STRUCT_TM New programs need not use these macros. We have no current plans to remove them. ** autoreconf For compatibility with future Libtool 2.0, autoreconf will invoke libtoolize with the option `--ltdl' now, if LT_CONFIG_LTDL_DIR is used. * Major changes in Autoconf 2.59c Released 2006-04-12, by Ralf Wildenhues. ** The configure command now redirects standard input from /dev/null, to help avoid problems with subsidiary commands that might mistakenly read standard input. AS_ORIGINAL_STDIN_FD points to the original standard input before this redirection, if you really want configure to read from standard input. ** Directory variables adjusted to recent changes in the GNU Coding Standards. The following directory variables are new: datarootdir read-only architecture-independent data root [PREFIX/share] localedir locale-specific message catalogs [DATAROOTDIR/locale] docdir documentation root [DATAROOTDIR/doc/PACKAGE] htmldir html documentation [DOCDIR] dvidir dvi documentation [DOCDIR] pdfdir pdf documentation [DOCDIR] psdir ps documentation [DOCDIR] The following variables have new default values: datadir read-only architecture-independent data [DATAROOTDIR] infodir info documentation [DATAROOTDIR/info] mandir man documentation [DATAROOTDIR/man] This means that if you use any of `@datadir@', `@infodir@', or `@mandir@' in a file, you will have to ensure `${datarootdir}' is defined in this file. As a temporary measure, if any of those are found but no mention of `datarootdir', the substitutions will be replaced with values that do not contain `${datarootdir}', and a warning will be issued. ** @top_builddir@ is now a dir name: it is always nonempty and doesn't have a trailing slash. Similar change will be made to ac_top_builddir in a future release; the old style value, which matches (../)*, is (and will continue to be) available as ac_top_build_prefix. ** AC_C_TYPEOF New macro to check for support of 'typeof' syntax a la GNU C. ** AC_CHECK_DECLS_ONCE, AC_CHECK_FUNCS_ONCE, AC_CHECK_HEADERS_ONCE New "once-only" variants of commonly-used macros, to make 'configure' smaller and faster in common cases. ** AC_FUNC_STRTOLD New macro to check for strtold with C99 semantics. ** AC_HEADER_ASSERT New macro that lets builder disable assertions at 'configure'-time. ** AC_PATH_X Now checks for X11/Xlib.h and XrmInitialize (X proper) rather than X11/Intrinsic.h and XtMalloc (Xt). ** AC_PRESERVE_HELP_ORDER New macro that causes `configure' to display help strings for AC_ARG_ENABLE and AC_ARG_WITH arguments in one region, in the order defined. The default behavior is to group options of each classes separately. ** AC_PROG_CC, AC_PROG_CXX No longer automatically arrange to declare the 'exit' function of C, when a C++ compiler is used. Standard Autoconf macros no longer use 'exit', so this is no longer an issue for them. If you use C++, and want to call 'exit', you'll have to arrange for its declaration yourself. But we now suggest you return from 'main' instead. ** AC_PROG_CC_C89, AC_PROG_CC_C99 New macros for ISO C99 support. AC_PROG_CC_C89 and AC_PROG_CC_C99 check for ANSI C89 and ISO C99 support respectively. ** AC_PROG_CC_STDC Has been unobsoleted, and will check if the compiler supports ISO C99, falling back to ANSI C89 if not. ac_cv_prog_cc_stdc is retained for backwards compatibility, assuming the value of ac_cv_prog_cc_c99 or ac_cv_prog_cc_c89 (whichever is valid, in that order). ** AC_STRUCT_DIRENT_D_INO, AC_STRUCT_DIRENT_D_TYPE New macros for checking commonly-used members of struct dirent. ** AC_SUBST The substituted value can now contain newlines. ** AC_SUBST_FILE The substitution now occurs only when @variable@ is on a line by itself, optionally surrounded by spaces and tabs. The whole line is replaced. ** AC_TYPE_LONG_DOUBLE, AC_TYPE_LONG_DOUBLE_WIDER New macros to check for long double, and whether it is wider than double. The old macro AC_C_TYPE_LONG_DOUBLE has been marked as obsolete; applications should switch to the new macro. ** AC_TYPE_INT8_T, AC_TYPE_INT16_T, AC_TYPE_INT32_T, AC_TYPE_INT64_T, AC_TYPE_INTMAX_T, AC_TYPE_INTPTR_T, AC_TYPE_LONG_LONG_INT, AC_TYPE_SSIZE_T, AC_TYPE_UINT8_T, AC_TYPE_UINT16_T, AC_TYPE_UINT32_T, AC_TYPE_UINT64_T, AC_TYPE_UINTMAX_T, AC_TYPE_UINTPTR_T, AC_TYPE_UNSIGNED_LONG_LONG_INT New macros to check for C99 and POSIX types. ** AC_USE_SYSTEM_EXTENSIONS New macro to enable extensions to Posix. ** AH_HEADER New macro which is defined to the name of the first declared config header or undefined if no config headers have been declared yet. ** AS_HELP_STRING The macro correctly handles quadrigraphs now. ** AS_BOURNE_COMPATIBLE, AS_SHELL_SANITIZE, AS_CASE These macros are new or published now. ** AT_COPYRIGHT New macro for copyright notices in testsuite files. ** ALLOCA, LIBOBJS, LTLIBOBJS Object names added to these variables are now prefixed with `${LIBOBJDIR}', as in `${LIBOBJDIR}alloca.o'. LIBOBJDIR is meant to be defined from `Makefile.in' in case the object files lie in a different directory. The LIBOBJDIR feature is experimental. ** autoreconf Supports --no-recursive now. ** New macros to support Erlang/OTP. New macros for configuring paths to Erlang tools and libraries: AC_ERLANG_PATH_ERLC, AC_ERLANG_NEED_ERLC, AC_ERLANG_PATH_ERL, AC_ERLANG_NEED_ERL, AC_ERLANG_CHECK_LIB, AC_ERLANG_SUBST_ROOT_DIR, AC_ERLANG_SUBST_LIB_DIR. New macros for configuring installation of Erlang libraries: AC_ERLANG_SUBST_INSTALL_LIB_DIR, AC_ERLANG_SUBST_INSTALL_LIB_SUBDIR. ** The manual now mentions Gnulib more prominently. ** New macros to support Objective C. AC_PROG_OBJC, AC_PROG_OBJCPP. * Major changes in Autoconf 2.59b Released 2004-08-20, by Paul Eggert. ** AC_CHECK_ALIGNOF New macro that computes the default alignment of a type. ** AC_CHECK_TOOL, AC_PATH_TOOL, AC_CHECK_TOOLS When cross-compiling, these macros will give a warning if the tool is not prefixed. In the future, unprefixed cross tools will not be detected; please consult the info documentation for information about the reason of this change. ** AC_CHECK_TARGET_TOOL, AC_PATH_TARGET_TOOL, AC_CHECK_TARGET_TOOLS New macros that detect programs whose name is prefixed with the target type, if the build type and target type are different. ** AC_REQUIRE_AUX_FILE New trace macro that declares expected auxiliary files. ** AC_PROG_GREP New macro that tests for a grep program that accepts as a long a line as possible. ** AC_PROG_EGREP, AC_PROG_FGREP These macros now require AC_PROG_GREP, and try EGREP="$GREP -E" and FGREP="$GREP -F" respectively if possible, or else run a path search for a program that accepts as long a line as possible. ** AC_PROG_SED New macro that tests for a sed program that truncates as few characters as possible. * Major changes in Autoconf 2.59 Released 2003-11-04, by Akim Demaille ** ac_abs_builddir etc. Absolute file names were actually relative in 2.58. * Major changes in Autoconf 2.58 Released 2003-11-04, by Akim Demaille ** core.* core.* files are no longer removed, as they may be valid user files. ** autoreconf and auxiliary directory Autoreconf creates the auxiliary directory if needed. This is especially useful for initial "bootstrapping" of fresh CVS checkouts. ** AC_CONFIG_MACRO_DIR Use this macro to declare the directory for local M4 macros for aclocal. ** AC_LIBOBJS No longer includes twice the same file in LIBOBJS if invoked multiple times. ** AC_CONFIG_COMMANDS The directory for its first argument is automatically created. For instance, with AC_CONFIG_COMMANDS([src/modules.hh], [...]) $top_builddir/src/ is created if needed. ** Autotest and local.at The optional file local.at is always included in Autotest test suites. ** Warnings The warnings are always issued, including with cached runs. This became a significant problem since aclocal and automake can run autoconf behind the scene. ** autoheader warnings The warnings of autoheader can be turned off, using --warning. For instance, -Wno-obsolete disables the complaints about acconfig.h and other deprecated constructs. ** New macros AC_C_RESTRICT, AC_INCLUDES_DEFAULT, AC_LANG_ASSERT, AC_LANG_WERROR, AS_SET_CATFILE. ** AC_DECL_SYS_SIGLIST Works again. ** AC_FUNC_MKTIME Now checks that mktime is the inverse of localtime. ** Improve DJGPP portability The Autoconf tools and configure behave better under DJGPP. ** Present But Cannot Be Compiled New FAQ section dedicated to the mystic configure: WARNING: pi.h: present but cannot be compiled configure: WARNING: pi.h: check for missing prerequisite headers? configure: WARNING: pi.h: proceeding with the preprocessor's result messages. ** Concurrent executions of autom4te autom4te now locks its internal files, which enables concurrent executions of autom4te, likely to happen if automake, autoconf, autoheader etc. are run simultaneously. ** Libtool Use of Libtool 1.5 and higher is encouraged. Compatibility with Libtool pre-1.4 is not checked. ** Autotest Testsuites no longer rerun failed tests in verbose mode; instead, failures are logged while the test is run. In addition, expected failures can be marked as such. * Major changes in Autoconf 2.57 Released 2002-12-03 by Paul Eggert. Bug fixes for problems with AIX linker, with freestanding C compilers, with GNU M4 limitations, and with obsolete copies of GNU documents. The Free Documentation License has been upgraded from 1.1 to 1.2. * Major changes in Autoconf 2.56 Released 2002-11-15 by Akim Demaille. One packaging problem fixed (config/install-sh was not executable). * Major changes in Autoconf 2.55 Released 2002-11-14 by Akim Demaille. Release tips: Have your configure.ac checked by autoscan ("autoscan"). Try the warning options ("autoreconf -fv -Wall"). ** Documentation - AC_CHECK_HEADER, AC_CHECK_HEADERS More information on proper use. - Writing Test Programs This sections explains how to write good test sources to use with AC_COMPILE_IFELSE etc. It documents AC_LANG_PROGRAM and so forth. - AC_FOO_IFELSE vs. AC_TRY_FOO Explains why Autoconf moves from AC_TRY_COMPILE etc. to AC_COMPILE_IFELSE and AC_LANG_PROGRAM etc. ** autoreconf - Is more robust to different Gettext installations. - Produces messages (when --verbose) to be understood by Emacs' compile mode. - Supports -W/--warnings. - -m/--make Once the GNU Build System reinstalled, run `./config.status --recheck && ./config.status && make' if possible. ** autom4te - Supports --cache, and --no-cache. - ~/.autom4te.cfg makes it possible to disable the caching mechanism (autom4te.cache). See `Customizing autom4te' in the documentation. ** config.status Supports --quiet. ** Obsolete options Support for the obsoleted options -m, --macrodir, -l, --localdir is dropped in favor of the safer --include/--prepend-include scheme. ** Macros - New macros AC_COMPILER_IFELSE, AC_FUNC_MBRTOWC, AC_HEADER_STDBOOL, AC_LANG_CONFTEST, AC_LANG_SOURCE, AC_LANG_PROGRAM, AC_LANG_CALL, AC_LANG_FUNC_TRY_LINK, AC_MSG_FAILURE, AC_PREPROC_IFELSE. - Obsoleted Obsoleted macros are kept for Autoconf backward compatibility, but should be avoided in configure.ac. Running autoupdate is advised. AC_DECL_SYS_SIGLIST. - AC_DEFINE/AC_DEFINE_UNQUOTED We have to stop using the old compatibility scheme --that tried to avoid useless backslashes-- because Libtool 1.4.3 contains a AC_DEFINE([error_t], [int], [Define to a type to use for \`error_t' if it is not otherwise available.]) We have to quote the single quotes and backslashes with \. The old compatibility scheme saw that ` was backslashed, and therefore did not quote the single quote... Failure. Hence, Autoconf 2.54 is not compatible with Libtool. Autoconf 2.55 is, but in some cases might produce more \ than wanted. Please, note that in the future the same problem will happen with AC_MSG_*: use `autoreconf -f -Wall'. ** Bug Fixes - Portability of the Autoconf package to Solaris. - Spurious warnings caused by config.status. This bug is benign, but painful: on some systems (typically FreeBSD), warnings such as: config.status: creating Makefile mv: Makefile: set owner/group (was: 1357/0): Operation not permitted could be issued. This is fixed. - Parallel Builds Simultaneous executions of config.status are possible again. - Precious variables accumulation config.status could stack several copies of the precious variables assignments. ** Plans for later versions - ./configure <host> The compatibility hooks with the old scheme will be completely removed. Please, advice/use `--build', `--host', and `--target' only. - AC_CHECK_HEADER, AC_CHECK_HEADERS The tests will be stricter, please make sure your invocations are valid. - shell functions Shell functions will gradually be introduced, probably starting with Autotest. If you know machines which are in use that you suspect *not* to support shell functions, please run the test suite of Autoconf 2.55 on it, and report the results to bug-autoconf@gnu.org. - AC_MSG_* Special characters in AC_MSG_* need not be quoted. Currently, Autoconf has heuristics to decide when a string is escaped, or has to be escaped. This scheme is fragile, and will be removed; the only risk is uglified messages. Please, run `autoreconf -f -Wall' to find occurrences that will be affected. * Major changes in Autoconf 2.54 Released 2002-09-13 by Akim Demaille. ** Executables - autoreconf no longer changes the version of the gettext/po/intl support files. It now adds the files the correspond to the AM_GNU_GETTEXT_VERSION declared in configure.ac. Warning: It now relies on the 'autopoint' program, which is part of GNU gettext 0.11.4 and newer. Please note that you need to have a GNU gettext version that corresponds at least to the AM_GNU_GETTEXT_VERSION declared in configure.ac. You can upgrade to newer GNU gettext versions, though, without needing to change configure.ac. - The -I DIR or --include=DIR option now appends DIR to the include path instead of prepending; this is for consistency with other GNU tools. The new -B DIR or --prepend-include=DIR option has the old behavior. ** Macros - AC_OUTPUT Now handles all the gory details about LIBOBJS and LTLIBOBJS. Please, remove lines such as # This is necessary so that .o files in LIBOBJS are also # built via the ANSI2KNR-filtering rules. LIBOBJS=`echo $LIBOBJS|sed 's/\.o /\$U.o /g;s/\.o$/\$U.o/'` and read the `AC_LIBOBJ vs LIBOBJS' section. Do not define U in your Makefiles either. - AC_CONFIG_LINKS now makes copies if it can't make links. - AC_FUNC_FNMATCH now tests only for POSIX compatibility, reverting to Autoconf 2.13 behavior. The new macro AC_FUNC_FNMATCH_GNU also tests for GNU extensions to fnmatch, and replaces fnmatch if needed. - AC_FUNC_SETVBUF_REVERSED no longer fails when cross-compiling. - AC_PROG_CC_STDC is integrated into AC_PROG_CC. - AC_PROG_F77 default search no longer includes cf77 and cfg77. - New macros AC_C_BACKSLASH_A, AC_CONFIG_LIBOBJ_DIR, AC_GNU_SOURCE, AC_PROG_EGREP, AC_PROG_FGREP, AC_REPLACE_FNMATCH, AC_FUNC_FNMATCH_GNU, AC_FUNC_REALLOC, AC_TYPE_MBSTATE_T. - AC_FUNC_GETLOADAVG looks for getloadavg.c in the CONFIG_LIBOBJ_DIR. - AC_FUNC_MALLOC Now defines HAVE_MALLOC to 0 if `malloc' does not work, and asks for an AC_LIBOBJ replacement. ** Bug fixes - Spurious complaints from `m4_bmatch' about invalid regular expressions are suppressed. - Empty top_builddirs are properly handled. - AC_CHECK_MEMBER works correctly when the member is an aggregate. - AC_PATH_PROG Now colon in the optional path arguments are properly handled. ** Improved portability - Both Autoconf the package, and the scripts it produces, should run more reliably with Zsh. Bear in mind it is the default Bourne shell on Darwin. - Autoconf and the scripts it produces no longer assume the existence of the obsolescent commands egrep and fgrep. ** Documentation - Limitations of Make More of them. - GNATS The GNATS base moved to http://bugs.gnu.org/cgi-bin/gnatsweb.pl?database=autoconf (It is no longer available, though.) ** Misc. - config.log Now contains the list of output variables and files (AC_SUBST, AC_SUBST_FILES). * Major changes in Autoconf 2.53 Released 2002-03-08 by Akim Demaille. ** Requirements Perl 5.005_03 or later is required: autom4te is written in Perl and is needed by autoconf. autoheader, autoreconf, ifnames, and autoscan are rewritten in Perl. ** Documentation - AC_INIT Argument requirements, output variables, defined macros. - M4sugar, M4sh, Autotest First sketch. - Double quoting macros AC_TRY_CPP, AC_TRY_COMPILE, AC_TRY_LINK and AC_TRY_RUN. - Licensing The Autoconf manual is now distributed under the terms of the GNU FDL. - Section `Hosts and Cross-Compilation' Explains the rationale for the 2.5x changes in the cross-compilation chain, and in the relationships between build, host, and target types. Emphasizes that `cross-compilation' == `--host is given'. If you are working on compilers etc., be sure to read this section. - Section `AC_LIBOBJ vs. LIBOBJS' Explains why assigning LIBOBJS directly is now an error. Details how to update the code. ** configure - $LINENO Now used instead of hard coded line numbers. This eases the comparison of `configure's, and diminishes the pressure over control version archives. Automatic replacement for shells that don't support this feature. - New output variables @builddir@, @top_builddir@, @abs_srcdir@, @abs_top_srcdir@, @abs_builddir@, @abs_top_builddir@. ** Emacs Autoconf and Autotest modes are provided. ** Executables - autom4te New, used by the Autoconf suite to cache and speed up most processing. - --force, -f Supported by autom4te, autoconf and autoheader. - --include, -I Replaces --autoconf-dir and --localdir in autoconf, autoheader, autoupdate, and autoreconf. - autoreconf No longer passes --cygnus, --foreign, --gnits, --gnu, --include-deps: automake options are to be given via AUTOMAKE_OPTIONS. - autoreconf Runs gettextize and libtoolize when appropriate. - autoreconf --m4dir is no longer supported. - autoreconf Now runs only in the specified directories, defaulting to `.', but understands AC_CONFIG_SUBDIRS for dependent directories. Before, it used to run on all the `configure.ac' found in the current tree. Independent packages are properly updated. ** Bug fixes - The top level $prefix is propagated to the AC_CONFIG_SUBDIRS configures. - AC_TRY_RUN Under the user pressure, $? is finally available. Probably a mistake. - AC_F77_LIBRARY_LDFLAGS now supports the HP/UX f90 compiler. - Precious variables accumulation config.status could stack several copies of the precious variables assignments. - AC_PATH_PROG and family. Works properly when given a literal path. - AC_FUNC_SETPGRP Somewhere since 2.13, the result had been reversed. ** C Macros - AC_C_BIGENDIAN supports the cross-compiling case. - AC_C_BIGENDIAN accepts ACTION-IF-TRUE, ACTION-IF-FALSE, and ACTION-IF-UNKNOWN arguments. All are optional, and the default for ACTION-IF-TRUE is to define WORDS_BIGENDIAN like AC_C_BIGENDIAN always did. - AC_C_LONG_DOUBLE now succeeds only if `long double' has more range or precision than `double'. ** Generic macros - AC_INIT It now defines the preprocessor symbols PACKAGE_NAME, PACKAGE_TARNAME, PACKAGE_VERSION, PACKAGE_STRING, and PACKAGE_BUGREPORT. - AC_INIT Admits a fourth optional parameter: the tar name. - AC_CONFIG_COMMANDS, HEADERS, FILES, LINKS. Provide the user with srcdir, ac_srcdir, ac_top_srcdir, ac_builddir, ac_top_builddir, ac_abs_srcdir, ac_abs_top_srcdir, ac_abs_builddir, ac_abs_top_builddir. - AC_CONFIG_COMMANDS, HEADERS, FILES, LINKS and AC_OUTPUT. Are much less expensive when using long lists of files. - AC_PREFIX_PROGRAM Works with shell variables, and non alphanumeric names. ** Library macros - AC_FUNC_STRERROR_R now sets STRERROR_R_CHAR_P, not HAVE_WORKING_STRERROR_R, because POSIX 1003.1-200x draft 7 says strerror_r returns int, not char *. - AC_FUNC_STRTOD substitutes POW_LIB. - AC_FUNC_STRNLEN New. * Major changes in Autoconf 2.52 Released 2001-07-18 by Akim Demaille. ** Documentation - AC_ARG_VAR - Quadrigraphs This feature was present in autoconf 2.50 but was not documented. For example, `@<:@' is translated to `[' just before output. This is useful when writing strings that contain unbalanced quotes, or other hard-to-quote constructs. - m4_pattern_forbid, m4_pattern_allow - Tips for upgrading from 2.13. - Using autoscan to maintain a configure.ac. ** Default includes - Now include stdint.h. - sys/types.h and sys/stat.h are guarded. - strings.h is included if available, and not conflicting with string.h. ** Bug fixes - The test suite is more robust and presents less false failures. - Invocation of GNU M4 now robust to POSIXLY_CORRECT. - configure accepts --prefix='' again. - AC_CHECK_LIB works properly when its first argument is not a literal. - HAVE_INTTYPES_H is defined only if not conflicting with sys/types.h. - build_, host_, and target_alias are AC_SUBST as in 2.13. - AC_ARG_VAR properly propagates precious variables inherited from the environment to ./config.status. - Using --program-suffix/--program-prefix is portable. - Failures to detect the default compiler's output extension are less likely. - `config.status foo' works properly when `foo' depends on variables set in an AC_CONFIG_THING INIT-CMD. - autoheader is more robust to broken input. - Fixed Fortran name-mangling and link tests on a number of systems, e.g. NetBSD; see AC_F77_DUMMY_MAIN, below. ** Generic macros - AC_CHECK_HEADER and AC_CHECK_HEADERS support a fourth argument to specify pre-includes. In this case, the headers are compiled with cc, not merely preprocessed by cpp. Therefore it is the _usability_ of a header which is checked for, not just its availability. - AC_ARG_VAR refuses to run configure when precious variables have changed. - Versions of compilers are dumped in the logs. - AC_CHECK_TYPE recognizes use of `foo_t' as a replacement type. ** Specific Macros - AC_PATH_XTRA only adds -ldnet to $LIBS if it's needed to link. - AC_FUNC_WAIT3 and AC_SYS_RESTARTABLE_SYSCALLS are obsoleted. - AM_FUNC_ERROR_AT_LINE, AM_FUNC_FNMATCH, AM_FUNC_MKTIME, AM_FUNC_OBSTACK, and AM_FUNC_STRTOD are now activated. Be sure to read `Upgrading from Version 2.13' to understand why running `autoupdate' is needed. - AC_F77_DUMMY_MAIN, AC_F77_MAIN: new macros to detect whether a main-like routine is required/possible when linking C/C++ with Fortran. Users of e.g. AC_F77_WRAPPERS should be aware of these. - AC_FUNC_GETPGRG behaves better when cross-compiling. * Major changes in Autoconf 2.51 There was no release of Autoconf 2.51 since some packagers had used this version number without permission to ship intermediary versions of 2.50. The version was skipped to avoid confusion. * Major changes in Autoconf 2.50 Released 2001-05-21 by Akim Demaille. ** Lots of bug fixes There have been far too many to enumerate them here. Check out ChangeLog if you really want to know more. ** Improved documentation In particular, portability issues are better covered. ** Use of Automake All the standard GNU Makefile targets are supported. The layout has changed: m4/ holds the M4 extensions Autoconf needs for its configuration, doc/ contains the documentation, and tests/ contains the test suite. ** Man pages are provided For autoconf, autoreconf, autoupdate, autoheader, autoscan, ifnames, config.guess, config.sub. ** autoconf - --trace Provides a safe and powerful means to trace the macro uses. This provide the parsing layer for tools which need to `study' configure.in. - --warnings Specify what category of warnings should be enabled. - When recursing into subdirectories, try for configure.gnu before configure to adapt for packages not using autoconf on case-insensitive file systems. - Diagnostics More errors are now caught (circular AC_REQUIRE dependencies, AC_DEFINE in the action part of an AC_CACHE_CHECK, too many pops etc.). In addition, their location and call stack are given. ** autoupdate autoupdate is much more powerful, and is able to provide the glue code which might be needed to move from an old macro to its newer equivalent. You are strongly encouraged to use it to modernize both your `configure.in' and your .m4 extension files. ** autoheader The internal machinery of autoheader has completely changed. As a result, using `acconfig.h' should be considered to be obsoleted, and you are encouraged to get rid of it using the AH macros. ** autoreconf Extensive overhaul. ** Fortran 77 compilers Globally, the support for Fortran 77 is considerably improved. Support for automatically determining a Fortran 77 compiler's name-mangling scheme. New CPP macros F77_FUNC and F77_FUNC_ are provided to wrap C/C++ identifiers, thus making it easier and more transparent for C/C++ to call Fortran 77 routines, and Fortran 77 to call C/C++ routines. See the Texinfo documentation for details. ** Test suite The test suite no longer uses DejaGNU. It should be easy to submit test cases in this new framework. ** configure - --help, --help=long, -hl no longer dumps useless items. - --help=short, -hs lists only specific options. - --help=recursive, -hr displays the help of all the embedded packages. - Remembers environment variables when reconfiguring. The previous scheme to set envvar before running configure was ENV=VAL ./configure what prevented configure from remembering the environment in which it was run, therefore --recheck was run in an inconsistent environment. Now, one should run ./configure ENV=VAR and then --recheck will work properly. Variables declared with AC_ARG_VAR are also preserved. - cross-compilation $build defaults to `config.guess`, $host to $build, and then $target to $host. Cross-compilation is a global status of the package, it no longer depends upon the current language. Cross compilation is enabled iff the user specified `--host'. `configure' now fails if it can't run the executables it compiles, unless cross-compilation is enabled. - Cache file The cache file is disabled by default. The new options `--config-cache', `-C' set the cache to `config.cache'. ** config.status - faster Much faster on most architectures. - concurrent executions It is safe to use `make -j' with config.status. - human interface improved It is possible to invoke ./config.status foobar instead of the former form (still valid) CONFIG_COMMANDS= CONFIG_HEADERS= CONFIG_LINKS= \ CONFIG_FILES=foobar:foo.in:bar.in \ ./config.status The same holds for configuration headers and links. You can instantiate unknown files and headers: ./config.status --header foo.h:foo.h.in --file bar:baz - has a useful --help - accepts special file name "-" for stdin/stdout ** Identity Macros - AC_COPYRIGHT Specify additional copyright information. - AC_INIT Now expects the identity of the package as argument. ** General changes. - Uniform quotation Most macros, if not all, now strictly follow the `one quotation level' rule. This results in a more predictable expansion. - AC_REQUIRE A sly bug in the AC_REQUIRE machinery, which could produce incorrect configure scripts, was fixed by Axel Thimm. ** Setup Macros - AC_ARG_VAR Document and ask for the registration of an envvar. - AC_CONFIG_SRCDIR Specifies the file which `configure' should look for when trying to find the source tree (used to be handled by AC_INIT). - AC_CONFIG_COMMANDS To add new actions to config.status. Should be used instead of AC_OUTPUT_COMMANDS. - AC_CONFIG_LINKS Replaces AC_LINK_FILES. - AC_CONFIG_HEADERS, AC_CONFIG_COMMANDS, AC_CONFIG_SUBDIRS, AC_CONFIG_LINKS, and AC_CONFIG_FILES They now obey sh: you should no longer use shell variables as argument. Instead of test "$package_foo_enabled" = yes && $my_subdirs="$my_subdirs foo" AC_CONFIG_SUBDIRS($my_subdirs) write if test "$package_foo_enabled" = yes; then AC_CONFIG_SUBDIRS(foo) fi - AC_HELP_STRING To format an Autoconf macro's help string so that it looks pretty when the user executes `configure --help'. ** Generic Test Macros - AC_CHECK families The interface of the AC_CHECK families of macros (decl, header, type, member, func) is now uniform. They support the same set of default includes. - AC_CHECK_DECL, AC_CHECK_DECLS To check whether a symbol is declared. - AC_CHECK_SIZEOF, AC_C_CHAR_UNSIGNED. No longer need a cross-compilation default. - AC_CHECK_TYPE The test it performs is much more robust than previously, and makes it possible to test builtin types in addition to typedefs. It is now schizophrenic: - AC_CHECK_TYPE(TYPE, REPLACEMENT) remains for backward compatibility, but its use is discouraged. - AC_CHECK_TYPE(TYPE, IF-FOUND, IF-NOT-FOUND, INCLUDES) behaves exactly like the other AC_CHECK macros. - AC_CHECK_TYPES Checks whether given types are supported by the system. - AC_CHECK_MEMBER, AC_CHECK_MEMBERS Check for given members in aggregates (e.g., pw_gecos in struct passwd). - AC_PROG_CC_STDC Checks if the compiler supports ISO C, included when needs special options. - AC_PROG_CPP Checking whether the preprocessor indicates missing includes by the error code. stderr is checked by AC_TRY_CPP only as a fallback. - AC_LANG Takes a language as argument and replaces AC_LANG_C, AC_LANG_CPLUSPLUS and AC_LANG_FORTRAN77. - AC_LANG_PUSH, AC_LANG_POP Are preferred to AC_LANG_SAVE, AC_LANG_RESTORE. ** Specific Macros - AC_FUNC_CHOWN, AC_FUNC_MALLOC, AC_FUNC_STRERROR_R, AC_FUNC_LSTAT_FOLLOWS_SLASHED_SYMLINK, AC_FUNC_STAT, AC_FUNC_LSTAT, AC_FUNC_ERROR_AT_LINE, AC_FUNC_OBSTACK, AC_FUNC_STRTOD, AC_FUNC_FSEEKO. New. - AC_FUNC_GETGROUPS Sets GETGROUPS_LIBS. - AC_FUNC_GETLOADAVG Defines `HAVE_STRUCT_NLIST_N_UN_N_NAME' instead of `NLIST_NAME_UNION'. - AC_PROG_LEX Now integrates `AC_DECL_YYTEXT' which is obsoleted. - AC_SYS_LARGEFILE Arrange for large-file support. - AC_EXEEXT, AC_OBJEXT You are no longer expected to use them: their computation is performed by default. ** C++ compatibility Every macro has been revisited in order to support at best CC=c++. Major changes in Autoconf 2.14: There was no release of GNU Autoconf 2.14. Major changes in Autoconf 2.13: Released 1999-05-01 by Ben Elliston. * Support for building on 32-bit Windows systems where the only available C or C++ compiler is the Microsoft Visual C++ command line compiler (`cl'). Additional support for building on 32-bit Windows systems which are using the Cygwin or Mingw32 environments. * Support for alternative object file and executable file extensions. On 32-bit Windows, for example, these are .obj and .exe. These are discovered using AC_OBJEXT and AC_EXEEXT, which substitute @OBJEXT@ and @EXEEXT@ in the output, respectively. * New macros: AC_CACHE_LOAD, AC_CACHE_SAVE, AC_FUNC_SELECT_ARGTYPES, AC_VALIDATE_CACHED_SYSTEM_TUPLE, AC_SEARCH_LIBS, AC_TRY_LINK_FUNC, AC_C_STRINGIZE, AC_CHECK_FILE(S), AC_PROG_F77 (and friends). * AC_DEFINE now has an optional third argument for a description to be placed in the config header input file (e.g. config.h.in). * The C++ code fragment compiled for the C++ compiler test had to be improved to include an explicit return type for main(). This was causing failures on systems using recent versions of the EGCS C++ compiler. * Fixed an important bug in AC_CHECK_TYPE that would cause a configure script to report that `sometype_t' was present when only `type_t' was defined. * Merge of the FSF version of config.guess and config.sub to modernize these scripts. Add support for a few new hosts in config.guess. Incorporate latest versions of install-sh, mkinstalldirs and texinfo.tex from the FSF. * autoreconf is capable of running automake if necessary (and applicable). * Support for Fortran 77. See the Texinfo documentation for details. * Bug fixes and workarounds for quirky bugs in vendor utilities. Major changes in Autoconf 2.12: Released 1996-11-26 by David J. MacKenzie * AC_OUTPUT and AC_CONFIG_HEADER can create output files by concatenating multiple input files separated by colons, like so: AC_CONFIG_HEADER(config.h:conf.pre:config.h.in:conf.post) AC_OUTPUT(Makefile:Makefile.in:Makefile.rules) The arguments may be shell variables, to compute the lists on the fly. * AC_LINK_FILES and AC_CONFIG_SUBDIRS may be called multiple times. * New macro AC_OUTPUT_COMMANDS adds more commands to run in config.status. * Bug fixes. Major changes in Autoconf 2.11: Released November 18th, 1996, by David J. MacKenzie * AC_PROG_CC and AC_PROG_CXX check whether the compiler works. They also default CFLAGS/CXXFLAGS to "-g -O2" for gcc, instead of "-g -O". * AC_REPLACE_FUNCS defines HAVE_foo if the system has the function `foo'. * AC_CONFIG_HEADER expands shell variables in its argument. * New macros: AC_FUNC_FNMATCH, AC_FUNC_SETPGRP. * The "checking..." messages and the source code for test programs that fail are saved in config.log. * Another workaround has been added for seds with small command length limits. * config.sub and config.guess recognize more system types. * Bug fixes. Major changes in Autoconf 2.10: Released May 7th, 1996, by Roland McGrath * Bug fixes. * The cache variable names used by `AC_CHECK_LIB(LIB, FUNC, ...)' has changed: now $ac_cv_lib_LIB_FUNC, previously $ac_cv_lib_LIB. Major changes in Autoconf 2.9: Released March 16th, 1996, by Roland McGrath * Bug fixes. Major changes in Autoconf 2.8: Released March 8th, 1996, by Roland McGrath * Bug fixes. Major changes in Autoconf 2.7: Released November 22nd, 1995, by David J. MacKenzie * Bug fixes. Major changes in Autoconf 2.6: Released November 20th, 1995, by David J. MacKenzie * Bug fixes. Major changes in Autoconf 2.5: Released November 17th, 1995, by Roland McGrath * New configure options --bindir, --libdir, --datadir, etc., with corresponding output variables. * New macro: AC_CACHE_CHECK, to make using the cache easier. * config.log contains the command being run as well as any output from it. * AC_CHECK_LIB can check for libraries with "." or "/" or "+" in their name. * AC_PROG_INSTALL doesn't cache a name for install-sh, for sharing caches. * AC_CHECK_PROG, AC_PATH_PROG, AC_CHECK_PROGS, AC_PATH_PROGS, and AC_CHECK_TOOL can search a path other than $PATH. * AC_CHECK_SIZEOF takes an optional size to use when cross-compiling. Major changes in Autoconf 2.4: Released June 14th, 1995, by David J. MacKenzie * Fix a few bugs found by Emacs testers. Major changes in Autoconf 2.3: Released March 27th, 1995, by David J. MacKenzie * Fix the cleanup trap in several ways. * Handle C compilers that are picky about option placement. * ifnames gets the version number from the right directory. Major changes in Autoconf 2.2: Released March 8th, 1995, by David J. MacKenzie * The ifnames utility is much faster but requires a "new awk" interpreter. * AC_CHECK_LIB and AC_HAVE_LIBRARY check and add the new library before existing libs, not after, in case it uses them. * New macros: AC_FUNC_GETPGRP, AC_CHECK_TOOL. * Lots of bug fixes. * Many additions to the TODO file :-) Major changes in Autoconf 2.1: Released November 4th, 1994, by David J. MacKenzie * Fix C++ problems. * More explanations in the manual. * Fix a spurious failure in the testsuite. * Clarify some warning messages. * autoreconf by default only rebuilds configure and config.h.in files that are older than any of their particular input files; there is a --force option to use after installing a new version of Autoconf. Thanks to everybody who's submitted changes and additions to Autoconf! I've incorporated many of them, and am still considering others for future releases -- but I didn't want to postpone this release indefinitely. Caution: don't indiscriminately rebuild configure scripts with Autoconf version 2. Some configure.in files need minor adjustments to work with it; the documentation has a chapter on upgrading. A few configure.in files, including those for GNU Emacs and the GNU C Library, need major changes because they relied on undocumented internals of version 1. Future releases of those packages will have updated configure.in files. It's best to use GNU M4 1.3 (or later) with Autoconf version 2. Autoconf now makes heavy use of M4 diversions, which were implemented inefficiently in GNU M4 releases before 1.3. Major changes in Autoconf 2.0: Released October 26th, 1994, by David J. MacKenzie ** New copyright terms: * There are no restrictions on distribution or use of configure scripts. ** Documentation: * Autoconf manual is reorganized to make information easier to find and has several new indexes. * INSTALL is reorganized and clearer and is now made from Texinfo source. ** New utilities: * autoscan to generate a preliminary configure.in for a package by scanning its source code for commonly used nonportable functions, programs, and header files. * ifnames to list the symbols used in #if and #ifdef directives in a source tree. * autoupdate to update a configure.in to use the version 2 macro names. * autoreconf to recursively remake configure and configuration header files in a source tree. ** Changed utilities: * autoheader can take pieces of acconfig.h to replace config.h.{top,bot}. * autoconf and autoheader can look for package-local definition files in an alternate directory. ** New macros: * AC_CACHE_VAL to share results of tests between configure runs. * AC_DEFUN to define macros, automatically AC_PROVIDE them, and ensure that macros invoked with AC_REQUIRE don't interrupt other macros. * AC_CONFIG_AUX_DIR, AC_CANONICAL_SYSTEM, AC_CANONICAL_HOST, AC_LINK_FILES to support deciding unguessable features based on the host and target types. * AC_CONFIG_SUBDIRS to recursively configure a source tree. * AC_ARG_PROGRAM to use the options --program-prefix, --program-suffix, and --program-transform-name to change the names of programs being installed. * AC_PREFIX_DEFAULT to change the default installation prefix. * AC_TRY_COMPILE to compile a test program without linking it. * AC_CHECK_TYPE to check whether sys/types.h or stdlib.h defines a given type. * AC_CHECK_LIB to check for a particular function and library. * AC_MSG_CHECKING and AC_MSG_RESULT to print test results, on a single line, whether or not the test succeeds. They obsolete AC_CHECKING and AC_VERBOSE. * AC_SUBST_FILE to insert one file into another. * AC_FUNC_MEMCMP to check whether memcmp is 8-bit clean. * AC_FUNC_STRFTIME to find strftime even if it's in -lintl. * AC_FUNC_GETMNTENT to find getmntent even if it's in -lsun or -lseq. * AC_HEADER_SYS_WAIT to check whether sys/wait.h is POSIX.1 compatible. ** Changed macros: * Many macros renamed systematically, but old names are accepted for backward compatibility. * AC_OUTPUT adds the "automatically generated" comment to non-Makefiles where it finds @configure_input@ in an input file, to support files with various comment syntaxes. * AC_OUTPUT does not replace "prefix" and "exec_prefix" in generated files when they are not enclosed in @ signs. * AC_OUTPUT allows the optional environment variable CONFIG_STATUS to override the file name "config.status". * AC_OUTPUT takes an optional argument for passing variables from configure to config.status. * AC_OUTPUT and AC_CONFIG_HEADER allow you to override the input-file names. * AC_OUTPUT automatically substitutes the values of CFLAGS, CXXFLAGS, CPPFLAGS, and LDFLAGS from the environment. * AC_PROG_CC and AC_PROG_CXX now set CFLAGS and CXXFLAGS, respectively. * AC_PROG_INSTALL looks for install-sh or install.sh in the directory specified by AC_CONFIG_AUXDIR, or srcdir or srcdir/.. or srcdir/../.. by default. * AC_DEFINE, AC_DEFINE_UNQUOTED, and AC_SUBST are more robust and smaller. * AC_DEFINE no longer prints anything, because of the new result reporting mechanism (AC_MSG_CHECKING and AC_MSG_RESULT). * AC_VERBOSE pays attention to --quiet/--silent, not --verbose. * AC_ARG_ENABLE and AC_ARG_WITH support whitespace in the arguments to --enable- and --with- options. * AC_CHECK_FUNCS and AC_CHECK_HEADERS take optional shell commands to execute on success or failure. * Checking for C functions in C++ works. ** Removed macros: * AC_REMOTE_TAPE and AC_RSH removed; too specific to tar and cpio, and better maintained with them. * AC_ARG_ARRAY removed because no one was likely using it. * AC_HAVE_POUNDBANG replaced with AC_SYS_INTERPRETER, which doesn't take arguments, for consistency with all of the other specific checks. ** New files: * Comes with config.sub and config.guess, and uses them optionally. * Uses config.cache to cache test results. An alternate cache file can be selected with the --cache-file=FILE option. * Uses optional shell scripts $prefix/share/config.site and $prefix/etc/config.site to perform site or system specific initializations. * configure saves compiler output to ./config.log for debugging. * New files autoconf.m4 and autoheader.m4 load the other Autoconf macros. * acsite.m4 is the new name for the system-wide aclocal.m4. * Has a DejaGnu test suite. Major changes in Autoconf 1.11: * AC_PROG_INSTALL calls install.sh with the -c option. * AC_SET_MAKE cleans up after itself. * AC_OUTPUT sets prefix and exec_prefix if they weren't set already. * AC_OUTPUT prevents shells from looking in PATH for config.status. Plus a few other bug fixes. Major changes in Autoconf 1.10: * autoheader uses config.h.bot if present, analogous to config.h.top. * AC_PROG_INSTALL looks for install.sh in srcdir or srcdir/.. and never uses cp. * AC_PROG_CXX looks for cxx as a C++ compiler. Plus several bugs fixed. Major changes in Autoconf 1.9: * AC_YYTEXT_POINTER replaces AC_DECLARE_YYTEXT. * AC_SIZEOF_TYPE generates the cpp symbol name automatically, and autoheader generates entries for those names automatically. * AC_FIND_X gets the result from xmkmf correctly. * AC_FIND_X assumes no X if --without-x was given. * AC_FIND_XTRA adds libraries to the variable X_EXTRA_LIBS. * AC_PROG_INSTALL finds OSF/1 installbsd. Major changes in Autoconf 1.8: ** New macros: * New macros AC_LANG_C, AC_LANG_CPLUSPLUS, AC_LANG_SAVE, AC_LANG_RESTORE, AC_PROG_CXX, AC_PROG_CXXCPP, AC_REQUIRE_CPP for checking both C++ and C features in one configure script. * New macros AC_CHECKING, AC_VERBOSE, AC_WARN, AC_ERROR for printing messages. * New macros AC_FIND_XTRA, AC_MMAP, AC_SIZEOF_TYPE, AC_PREREQ, AC_SET_MAKE, AC_ENABLE. ** Changed macros: * AC_FIND_X looks for X in more places. * AC_PROG_INSTALL defaults to install.sh instead of cp, if it's in srcdir. install.sh is distributed with Autoconf. * AC_DECLARE_YYTEXT has been removed because it can't work, pending a rewrite of quoting in AC_DEFINE. * AC_OUTPUT adds its comments in C format when substituting in C files. * AC_COMPILE_CHECK protects its ECHO-TEXT argument with double quotes. ** New or changed command line options: * configure accepts --enable-FEATURE[=ARG] and --disable-FEATURE options. * configure accepts --without-PACKAGE, which sets withval=no. * configure accepts --x-includes=DIR and --x-libraries=DIR. * Giving --with-PACKAGE no argument sets withval=yes instead of withval=1. * configure accepts --help, --version, --silent/--quiet, --no-create options. * configure accepts and ignores most other Cygnus configure options, and warns about unknown options. * config.status accepts --help, --version options. ** File names and other changes: * Relative srcdir values are not made absolute. * The values of @prefix@ and @exec_prefix@ and @top_srcdir@ get substituted. * Autoconf library files are installed in ${datadir}/autoconf, not ${datadir}. * autoheader optionally copies config.h.top to the beginning of config.h.in. * The example Makefile dependencies for configure et al. work better. * Namespace cleanup: all shell variables used internally by Autoconf have names beginning with `ac_'. More big improvements are in process for future releases, but have not yet been (variously) finished, integrated, tested, or documented enough to release yet. Major changes in Autoconf 1.7: * New macro AC_OBSOLETE. * Bugs in Makefile.in fixed. * AC_LONG_FILE_NAMES improved. Major changes in Autoconf 1.6: * New macro AC_LONG_64_BITS. * Multiple .h files can be created. * AC_FIND_X looks for X files directly if it doesn't find xmkmf. * AC_ALLOCA defines C_ALLOCA if using alloca.c. * --with-NAME can take a value, e.g., --with-targets=sun4,hp300bsd. * Unused --no-create option to configure removed. * autoheader doesn't change the timestamp of its output file if the file didn't change. * All macros that look for libraries now use AC_HAVE_LIBRARY. * config.status checks three optional environment variables to modify its behavior. * The usual bug fixes. Major changes in Autoconf 1.5: * New macros AC_FIND_X, AC_OFF_T, AC_STAT_MACROS_BROKEN, AC_REVISION. * autoconf and autoheader scripts have GNU standards conforming --version and --help options (they print their message and exit). * Many bug fixes. Major changes in Autoconf 1.4: * New macros AC_HAVE_POUNDBANG, AC_TIME_WITH_SYS_TIME, AC_LONG_DOUBLE, AC_GETGROUPS_T, AC_DEFINE_UNQUOTED. * autoconf and autoheader use the M4 environment variable to determine the name of the M4 program to use. * The --macrodir option to autoconf and autoheader specifies the directory in which acspecific.m4, acgeneral.m4, etc. reside if not the default. * autoconf and autoheader can take `-' as their file names, which means to read stdin as input. * Resulting configure scripts can take a --verbose option which causes them to print the results of their tests. * AC_DEFINE quotes its second argument in such a way that spaces, magic shell characters, etc. will be preserved during various stages of expansion done by the shell. If you don't want this, use AC_DEFINE_UNQUOTED instead. * Much textual processing done with external calls to tr and sed have been internalized with builtin M4 `patsubst' and `translit' calls. * AC_OUTPUT doesn't hardwire the file names it outputs. Instead, you can set the shell variables `gen_files' and `gen_config' to the list of file names to output. * AC_DECLARE_YYTEXT does an AC_SUBST of `LEX_OUTPUT_ROOT', which may be "lex.yy" or "lexyy", depending on the system. * AC_PROGRAMS_CHECK takes an optional third arg. If given, it is used as the default value. * If AC_ALLOCA chooses alloca.c, it also defines STACK_DIRECTION. * AC_CONST works much more reliably on more systems. * Many bug fixes. Major changes in Autoconf 1.3: configure no longer requires awk for packages that use a config.h. Support handling --with-PACKAGE options. New `autoheader' script to create `config.h.in' from `configure.in'. Ignore troublesome -lucb and -lPW when searching for alloca. Rename --exec_prefix to --exec-prefix for GNU standards conformance. Improve detection of STDC library. Add AC_HAVE_LIBRARY to check for non-default libraries. Function checking should work with future GNU libc releases. Major changes in Autoconf 1.2: The --srcdir option is now usually unnecessary. Add a file containing sample comments describing CPP macros. A comment in config.status tells which host it was configured on. Substituted variable values can now contain commas. Fix bugs in various feature checks. Major changes in Autoconf 1.1: Added AC_STRCOLL macro. Made AC_GETLOADAVG check for more things. AC_OUTPUT argument is now optional. Various bug fixes. ----- Copyright (C) 1993-1996, 1998-2012 Free Software Foundation, Inc. Copying and distribution of this file, with or without modification, are permitted in any medium without royalty provided the copyright notice and this notice are preserved. This file is offered as-is, without warranty of any kind. Local Variables: mode: outline End: PK [�!\HxAAt t AUTHORSnu �[��� Authors of GNU Autoconf. Autoconf was originally written by David MacKenzie, with help from François Pinard, Karl Berry, Richard Pixley, Ian Lance Taylor, Roland McGrath, Noah Friedman, david d zuhn, and many others. Ben Elliston next took over the maintenance, facing a huge Autoconf backlog that had been piling up since the departure of David. Other maintainers have included Akim Demaille, Jim Meyering, Alexandre Oliva, and Tom Tromey, with plenty of contributions from Lars J. Aas, Mo DeJong, Steven G. Johnson, Matthew D. Langston, Pavel Roskin. Today, the primary maintainers are Paul Eggert and Eric Blake, with help from Ralf Wildenhues, Stepan Kasal, and Benoit Sigoure. Many other people have contributed, as listed in the THANKS file. The following contributors have warranted legal paper exchanges with the Free Software Foundation for their contributions to GNU Autoconf. This list results from searching for AUTOCONF in the file /gd/gnuorg/copyright.list on the fencepost.gnu.org machine. David J. MacKenzie djm@gnu.org 1991-07-09 James L. Avera ? 1993-10-04 Roland McGrath roland@gnu.org 1994-06-24 Noah Friedman friedman@gnu.org 1994-07-15 Francois Pinard pinard@iro.umontreal.ca 1997-02-02 Thomas E. Dickey dickey@clark.net 1998-01-11 Matthew D. Langston langston@slac.stanford.edu 1998-09-29 Mark Elbrecht snowball3@usa.net 1999-01-11 Akim Demaille akim@gnu.org 1999-02-02 Pavel Roskin pavel_roskin@geocities.com 1999-02-24 Alexandre Oliva oliva@dcc.unicamp.br 1999-03-26 Thomas Tanner tanner@ffii.org 1999-06-23 Gary V. Vaughan gary@gnu.org 2000-01-10 Joseph Samuel Myers jsm28@cam.ac.uk 2000-03-13 Lars J. Aas larsa@sim.no 2000-07-07 Morten Eriksen mortene@sim.no 2000-07-07 Martin Wilck martin@tropos.de 2000-07-12 Paul Eggert eggert@twinsun.com 2000-10-13 Alexandre Duret-Lutz duret_g@epita.fr 2001-02-12 Tim Van Holder tim.van.holder@pandora.be 2001-02-13 Christian Marquardt marq@gfz-potsdam.de 2001-02-19 Derek R. Price dprice@collab.net 2001-03-12 Markus Kuhn Markus.Kuhn@cl.cam.ac.uk 2001-07-07 Erik Lindahl erik@theophys.kth.se 2001-08-22 Hans-Peter Nilsson hp@bitrange.com 2001-10-24 Paul Wagland paul@wagland.net 2001-10-30 Paolo Bonzini bonzini@gnu.org 2001-11-08 Nishio Futoshi fut_nis@d3.dion.ne.jp 2002-01-23 Federico G. Schwindt fgsch@openbsd.org 2002-05-21 Mark D. Roth roth@feep.net 2002-05-28 Greg McGary greg@mcgary.org 2002-06-05 Charles Stephen Wilson cwilson@ece.gatech.edu 2002-07-25 Robert Bernstein rocky@panix.com 2002-08-20 Assar Westerlund assar@kth.se 2002-09-13 Scott Bambrough sbambrough@storm.ca 2002-09-24 Richard Dawe rich@phekda.freeserve.co.uk 2003-01-23 Andreas Buening andreas.buening@nexgo.de 2003-02-18 Raja R. Harinath harinath@acm.org 2003-02-25 Ilya Zakharevich ilya@Math.Berkeley.EDU 2003-03-11 Kaveh Ghazi ghazi@caip.rutgers.edu 2003-03-15 Felix Lee felix.1@canids.net 2003-03-31 Nathanael Nerode neroden@twcny.rr.com 2003-04-04 Gavin Puche user42@zip.com.au 2003-04-10 Steven Glenn Johnson stevenj@alum.mit.edu 2003-07-26 Bernardo Innocenti bernie@codewiz.org 2003-07-31 Albert Marsden Chin-A-Young china@thewrittenword.com 2003-08-02 Ralf Corsepius corsepiu@faw.uni-ulm.de 2003-09-03 Scott Remnant scott@netsplit.com 2003-10-04 Daniel Jacobowitz dan@debian.org 2003-10-17 Kevin Fleming kpfleming@backtobasicsmgmt.com 2003-11-17 John David Anglin dave.anglin@nrc-cnrc.gc.ca 2004-01-21 Eric Sunshine sunshine@sunshineco.com 2004-01-25 Ralf Wildenhues Ralf.Wildenhues@gmx.de 2004-02-12 Noah Jeffrey Misch noah@cs.caltech.edu 2004-07-05 Thorsten Glaser tg@66h.42h.de 2004-10-11 Peter O'Gorman peter@pogma.com 2004-11-14 Toshio Ernie Kuratomi toshio@tiki-lounge.com 2004-11-17 Roger Leigh rleigh@whinlatter.ukfsn.org 2004-12-09 Ian Lance Taylor ian@airs.com 2004-12-22 Daniel Manthey dan_manthey@partech.com 2005-02-14 Gregorio Guidi greg_g@gentoo.org 2005-03-03 Bruno Haible bruno@clisp.org 2005-06-12 Toby Oliver Hilary White tow21@cam.ac.uk 2005-10-18 Eric Benjamin Blake ebb9@byu.net 2006-01-18 Romain Lenglet romain.lenglet@laposte.net 2006-02-10 Markus Duft markus.duft@salomon.at 2006-08-03 Robert Schiele rschiele@gmail.com 2006-09-12 Joel Edward Denny jdenny@clemson.edu 2006-09-15 Helge Deller deller@gmx.de 2007-02-01 Benoit Sigoure tsuna@lrde.epita.fr 2007-04-20 Bob Proulx bob@proulx.com 2007-06-25 Bruce Korb bkorb@gnu.org 2008-05-06 Benjamin Pfaff blp@gnu.org 2008-09-29 Peter Breitenlohner peb@mppmu.mpg.de 2009-08-18 Stefano Lattarini stefano.lattarini@gmail.com 2009-10-01 Reuben Thomas rrt@sc3d.org 2010-03-10 Peter Rosin peda@lysator.liu.se 2010-07-21 John W. Eaton jwe@gnu.org 2010-11-05 Christopher Hulbert cchgroupmail@gmail.com 2010-11-09 Tim Rice tim@multitalents.net 2011-01-24 KO Myun-Hun komh78@gmail.com 2011-04-05 Christian Roessel christian.roessel@gmx.de 2011-08-26 Nicolai Stange nicolai.stange@zmaw.de 2011-10-13 ======================================================================== Local Variables: mode: text coding: utf-8 End: Copyright (C) 1996, 2000-2001, 2005, 2007-2012 Free Software Foundation, Inc. This program is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version. This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. You should have received a copy of the GNU General Public License along with this program. If not, see <http://www.gnu.org/licenses/>. PK [�!\J jQ T T THANKSnu �[��� GNU Autoconf THANKS file GNU Autoconf was originally written by David J. MacKenzie. It would not be what it is today without the invaluable help of these people, who have reported problems, suggested improvements, or submitted actual code. Please help us keep this list complete and free from errors. Also see the AUTHORS file for the list of people with contributions significant enough to warrant copyright assignment. Aaron Crane aaronc@pobox.com Aaron M. Ucko amu@alum.mit.edu Aaron W. LaFramboise aaronenvelope277@aaronwl.com Adam J. Richter adam@yggdrasil.com Adrian Bunk bunk-gnu@fs.tum.de Aharon Robbins arnold@gnu.org Akim Demaille akim@freefriends.org Akinori Musha knu@iDaemons.org Alain Knaff Alain.Knaff@imag.fr Albert Chin-A-Young china@thewrittenword.com Alec Wolman wolman@cs.washington.edu Alex Unleashed unledev@gmail.com Alexander Kurz alexander.kurz@qsc.de Alexander Mai ? Alexander Pletzer pletzer@txcorp.com Alexandre Duret-Lutz duret_g@epita.fr Alexandre Julliard ? Alexandre Oliva oliva@lsd.ic.unicamp.br Alfred G. de Wijn dwijn@iluvatar.eu.org Alfred M. Szmidt ams@gnu.org Allan Caffee allan.caffee@gmail.com Allan Clark allanc@chickenandporn.com Anders Kaseorg andersk@MIT.EDU Andreas Buening andreas.buening@nexgo.de Andreas Jaeger aj@suse.de Andreas Schott schott@rzg.mpg.de Andreas Schwab schwab@issan.informatik.uni-dortmund.de Andreas Waechter andreasw@watson.ibm.com Andrej Borsenkow borsenkow.msk@sni.de Andrew Belov ? Andrew Church achurch@achurch.org Andrey Simonenko simon@comsys.ntu-kpi.kiev.ua Andris Pavenis andris.pavenis@iki.fi Anthony N. Frasso afrasso@yahoo.com Arkadiusz Miskiewicz arekm@maven.pl Art Haas ahaas@neosoft.com Arto C. Nirkko ? Artur Frysiak wiget@pld.org.pl Assar Westerlund assar@sics.se Axel Thimm Axel.Thimm@physik.fu-berlin.de Bart Oldeman bartoldeman@users.sourceforge.net Ben Elliston bje@redhat.com Ben Pfaff pfaffben@debian.org Benoit Sigoure tsunanet@gmail.com Bill Moseley moseley@hank.org Bill Northcott w.northcott@unsw.edu.au Bill Sommerfeld sommerfeld@apollo.hp.com BJ Terry bjterry@gmail.com Bob Friesenhahn bfriesen@simple.dallas.tx.us Bob Proulx bob@proulx.com Bob Rossi bob_rossi@cox.net Bob Wilson bwilson@tensilica.com Brad Walker me@bradmwalker.com Braden McDaniel braden@endoframe.com Bram Moolenaar bram@vim.org Brian Gough bjg@network-theory.co.uk Brian J. Murrell brian@sun.com Bruce Dugan bld0401@gmail.com Bruce Korb bkorb@gnu.org Bruce Lilly ? Bruno Haible haible@ilog.fr Björn Lindqvist bjourne@gmail.com Carl Edman cedman@princeton.edu Carlos Velasco carlosev@newipnet.com Chad R. Larson chad@anasazi.com Charles 'Buck' Krasic krasic@cs.ubc.ca Chikama Masaki masaki.chikama@gmail.com Chris P. Ross cross@uu.net Chris Pickett chris.pickett@mail.mcgill.ca Chris Provenzano proven@cygnus.com Chris Torek torek@bsdi.com Christian Cornelssen ccorn@cs.tu-berlin.de Christian Krackowizer ckrackowiz@std.schuler-ag.com Christian Krone krischan@sql.de Christian Rössel christian.roessel@gmx.de Christophe Jarry christophe.jarry@ouvaton.org Christopher Hulbert cchgroupmail@gmail.com Christopher Lee chrislee@ri.cmu.edu Clinton Roy clinton.roy@gmail.com Colin Watson cjwatson@debian.org Corinna Vinschen corinna-cygwin@cygwin.com Cort Dougan cort@cs.nmt.edu D'Arcy A MacIsaac ? Dalibor Topic robilad@kaffe.org Dan Manthey dan_manthey@partech.com Daniel Carroll dan@mesastate.edu Daniel Jacobowitz drow@mvista.com Daniel Reed ? Daniele Arena daniele@ripe.net Dave Adams adams@hpesdwa.fc.hp.com Dave Erickson retrorandomaccess@hotmail.com Dave Korn dave.korn.cygwin@googlemail.com Dave Love fx@gnu.org David Byron dbyron@hheld.com David Carter david@carter.net David Cournapeau david@ar.media.kyoto-u.ac.jp David Fang fang@csl.cornell.edu David J. MacKenzie djm@uunet.uu.net David M. Lloyd dmlloyd@tds.net David Morgan dmorgan@symark.com Davie Reiss dreiss@facebook.com David Relson relson@osagesoftware.com Dennis J. Linse ? Derek R. Price derek.price@openavenue.com Didier Desseaux didess@infonie.fr Didier Verna didier@xemacs.org Dieter Jurzitza dieter.jurzitza@t-online.de Dietmar P. Schindler schd@mra.man.de Dmitry Grebeniuk gdsfh1@gmail.com Doug Evans dje@canuck.cygnus.com Dries Kimpe ? Dustin J. Mitchell dustin@zmanda.com Edouard Bechetoille ebecheto@ens-lyon.fr Elbert Pol elbert.pol@gmail.com Eli Zaretskii eliz@gnu.org Elias Pipping pipping@macports.org Enrique Robledo Arnuncio enrique.robledo@wanadoo.es Erez Zadok ezk@cs.columbia.edu Eric Backus ericb@lsid.hp.com Eric Blake ebb9@byu.net Eric Lemings lemings@roguewave.com Eric Mumpower nocturne@mit.edu Eric Paire ? Eric Sunshine sunshine@sunshineco.com Ezra Peisach epeisach@zif.mit.edu Fedor Sergeev ? Felix Lee flee@cygnus.com Fernando Carrijo fcarrijo@freedesktop.org Franceseco Romani fromani@gmail.com Frank Denis j@jedi.claranet.fr François Pinard pinard@iro.umontreal.ca Fred Kreek Fred.Kreek@kadaster.nl Frederik Fouvry fouvry@CoLi.Uni-SB.DE Gareth McCaughan gareth.mccaughan@pobox.com Gary V. Vaughan gvaughan@oranda.demon.co.uk Geir Ove Myhr myhr@stud.fim.ntnu.no Gerrit P. Haase gp@familiehaase.de Gideon Go gideon.go@gmail.com Giorgos Keramidas gkeramidas@gmail.com Giuseppe Guerrini guisguerrini@racine.ra.it Glenn P. Davis davis@unidata.ucar.edu Godmar Back gback@cs.utah.edu Gordon Matzigkeit gord@trick.fig.org Graham Jenkins c714553@vus415.telstra.com.au Greg A. Woods woods@weird.com Greg Schafer gschafer@zip.com.au Gregorio Guidi ? Gregory Giannoni sand@narguile.org Giulio Paci giuliopaci@interfree.it Guido Draheim Guido.Draheim@gmx.de Guido Flohr gufl0000@stud.uni-sb.de Guido van Rossum ? Guillermo Gomez gomez@mi.uni-erlangen.de H. Merijn Brand h.m.brand@hccnet.nl H. Peter Anvin ? H.J. Lu hjl@gnu.org Hallvard B Furuseth h.b.furuseth@usit.uio.no Hans Aberg haberg@math.su.se Hans Olsson Hans.Olsson@dna.lth.se Hans Ulrich Niedermann hun@n-dimensional.de Harlan Stenn stenn@whimsy.udel.edu Heiko Schlichting inn-workers@fu-berlin.de Henk Krus h.krus@cyclone.nl Howard Chu hyc@highlandsun.com Ian Lance Taylor ian@cygnus.com Ian Macdonald iamacdo@telkomsa.net Ian Redfern Ian.Redfern@logicacmg.com Ilya Bobir ilya.bobir@gmail.com Ilya Zakharevich ilya@Math.Berkeley.EDU Ineiev ineiev@yahoo.co.uk Iohannes m zmoelnig zmoelnig@iem.at J C Fitzgerald v7022@wave.co.nz Jaap Haitsma jaap@haitsma.org James A. Lupo lupoja@feynman.ml.wpafb.af.mil Jan Madzik jmadzik@gmail.com Jason Molenda jsm@cygnus.com Jeff Garzik jgarzik@pobox.com Jeff Painter ? Jeff Squyres jsquyres@cisco.com Jeffrey A Law law@cygnus.com Jeffrey J. Barteet ? Jennis Pruett ? Jens Petersen petersen@redhat.com Jens Schmidt jens.schmidt35@arcor.de Jeremy Yallop jeremy@yallop.org Jerker Bäck jerker.back@home.se Jim Blandy jimb@wookumz.gnu.ai.mit.edu Jim Meyering meyering@ascend.com Jim Warhol jrw@jwarhol.com Jiro Takabatake jiro@din.or.jp Jochen Friedrich jochen@scram.de Joel E. Denny jdenny@ces.clemson.edu Joel James Adamson joel@chondestes.bio.unc.edu Joey Mingrone joey@mingrone.org Johan Danielsson joda@pdc.kth.se John Calcote john.calcote@gmail.com John David Anglin dave@hiauly1.hia.nrc.ca John Fortin fortinj@attglobal.net John Interrante interran@uluru.stanford.edu John R. Cary cary@txcorp.com John W. Eaton jwe@bevo.che.wisc.edu Jonathan Kamens jik@kamens.brookline.ma.us Josef Tran josef@timetrackertechnology.com Josef Vukovic josefvukovic@googlemail.com Joseph S. Myers jsm28@cam.ac.uk Joshua G. Hale jgh.emc@gmail.com Juan Carlos Hurtado adso.lists@gmail.com Jules Colding colding@42tools.com Julian C. Cummings cummings@cacr.caltech.edu Julian Onions j.onions@nexor.co.uk Julien Danjou acid@debian.org Julien Élie julien@trigofacile.com Julio Garvia ? Justace Clutter ? Jörn Rennecke amylaar@cygnus.co.uk Karl Berry karl@cs.umb.edu Karl Heuer kwzh@gnu.org Karsten Hopp karsten@redhat.com Kate Hedstrom ? Kathryn Hargreaves kathryn@deas.harvard.edu Kaveh R. Ghazi ghazi@caip.rutgers.edu Keith Bostic bostic@abyssinian.sleepycat.com Keith Marshall keith.marshall@total.com Kelly Anderson tgcorp@attglobal.net Ken Pizzini ken@halcyon.com Ken Raeburn raeburn@cygnus.com Kevin Ryde user42@zip.com.au Klee Dienes kdienes@apple.com Koji Arai JCA02266@nifty.ne.jp Kristian Kvilekval kris@cs.ucsb.edu Křištof Želechovski giecrilj@stegny.2a.pl Kurt D. Zeilenga kurt@openldap.org Larry Jones larry.jones@sdrc.com Larry Schmitt larry@mail.haleakalawebdesigns.com Larry Schwimmer rosebud@cyclone.stanford.edu Lars Hecking lhecking@nmrc.ucc.ie Lars J. Aas larsa@sim.no Laurence Darbe ldarby@tuffmail.com Leo Moisio leo.moisio@gmail.com Loulou Pouchet loulou@lrde.epita.fr Luc Maisonobe luc@spaceroots.org Ludovic Courtes ? Luke Dalessandro luked@cs.rochester.edu Magnus Therning therning@gforge.natlab.research.philips.com Manu manubee@wanadoo.fr Marc Espie Marc.Espie@liafa.jussieu.fr Marcus Brinkmann ? Marcus Daniels marcus@sysc.pdx.edu Marcus Thiessel marcus@xemacs.org Mark Cave-Ayland ? Mark D. Baushke ? Mark D. Roth ? Mark Elbrecht snowball3@usa.net Mark Hessling mark@rexx.org Mark Kettenis kettenis@gnu.org Markku Savela msa@msa.tte.vtt.fi Markus Oberhumer markus.oberhumer@jk.uni-linz.ac.at Markus Geimer m.geimer@fz-juelich.de Martin Buchholz martin@xemacs.org Martin Costabel costabel@wanadoo.fr Martin Frydl martin@systinet.com Martin Koeppe mkoeppe@gmx.de Martin Mokrejs mmokrejs@natur.cuni.cz Martin Wilck martin@tropos.de Martyn Johnson Martyn.Johnson@cl.cam.ac.uk Matěj Týč matej.tyc@gmail.com Matt Kraai kraai@ftbfs.org Matteo Frigo ? Matthew D. Langston langston@SLAC.Stanford.EDU Matthew Mueller donut@azstarnet.com Matthew Woehlke mw_triad@users.sourceforge.net Matthias Andree matthias.andree@gmx.de Michal Čihař nijel@debian.org Michael Elizabeth Chastain chastain@cygnus.com Michael Jenning ? Michael Matz matz@kde.org Michael Schoene mrs@mlc.de Michael Wardle ? Mike Frysinger vapier@gentoo.org Mike Hopkirk hops@sco.com Mike Stump mrs@wrs.com Mikulas Patocka ? Miles Bader miles@gnu.ai.mit.edu Mo DeJong mdejong@cygnus.com Momchil Velkov velco@fadata.bg Monty Taylor mordred@inaugust.com Morten Eriksen mortene@sim.no Mostafa mostafa_working_away@yahoo.com Motoyuki Kasahara m-kasahr@sra.co.jp Nathan Schulte reklipz@gmail.com Nathanael Nerode neroden@gcc.gnu.org Nelson H. F. Beebe beebe@math.utah.edu Nicolas Joly njoly@pasteur.fr Nicolás Lichtmaier jnl@synapsis-sa.com.ar Nick Bowler nbowler@elliptictech.com NightStrike nightstrike@gmail.com Nishio Futoshi fut_nis@d3.dion.ne.jp Noah Elliott elliott@hera.llnl.gov Noah Friedman friedman@gnu.ai.mit.edu Noah Misch noah@cs.caltech.edu Norman Gray ? Olaf Lenz olenz@fias.uni-frankfurt.de Ole Holm Nielsen Ole.H.Nielsen@fysik.dtu.dk Oliver Kiddle opk@zsh.org Olly Betts olly@survex.com Ossama Othman ossama@debian.org Pallav Gupta pallavgupta@gmail.com Paolo Bonzini bonzini@gnu.org Patrick Tullmann tullmann@cs.utah.edu Patrick Welche prlw1@newn.cam.ac.uk Paul Berrevoets paul@swi.com Paul D. Smith psmith@gnu.org Paul Eggert eggert@cs.ucla.edu Paul Gampe paulg@apnic.net Paul Jarc prj@po.cwru.edu Paul Martinolich martinol@datasync.com Paul Pogonyshev ? Paul Townsend ? Pavel Roskin pavel_roskin@geocities.com Pádraig Brady P@draigbrady.com Per Øyvind Karlsen peroyvind@mandriva.org Peter Breitenlohner peb@mppmu.mpg.de Peter Eisentraut peter_e@gmx.net Peter Hendrickson pdh@wiredyne.com Peter Johansson trojkan@gmail.com Peter O'Gorman peter@pogma.com Peter Palfrader weasel@debian.org Peter Simons simons@cryp.to Peter Stephenson pws@csr.com Philipp Thomas kthomas@gwdg.de Philippe De Muyter ? Pierre pierre42d@9online.fr Pierre Ynard linkfanel@yahoo.fr Pontus Skoeld pont@soua.net Rainer Orth ro@TechFak.Uni-Bielefeld.DE Raja R Harinath harinath@cs.umn.edu Ralf Corsepius corsepiu@faw.uni-ulm.de Ralf Menzel menzel@ls6.cs.uni-dortmund.de Ralf S. Engelschall rse@engelschall.com Ralf Wildenhues Ralf.Wildenhues@gmx.de Randall Cotton recotton@earthlink.net Reuben Thomas rrt@sc3d.org Richard Dawe rich@phekda.freeserve.co.uk Richard Stallman rms@gnu.org Robert Lipe robertlipe@usa.net Robert S. Maier rsm@math.arizona.edu Roberto Bagnara bagnara@cs.unipr.it Rochan rochan@ices.utexas.edu Roger Leigh rleigh@whinlatter.ukfsn.org Roland McGrath roland@gnu.org Rolf Ebert rolf.ebert.gcc@gmx.de Rolf Vandevaart Rolf.Vandevaart@sun.com Romain Lenglet romain.lenglet@laposte.net Ruediger Kuhlmann info@ruediger-kuhlmann.de Rugxulo rugxulo@gmail.com Ruslan Babayev ruslan@babayev.com Russ Allbery rra@stanford.edu Russ Boylan ross@biostat.ucsf.edu Ryuji Abe raeva@t3.rim.or.jp Sam Sexton Sam.Sexton@reuters.com Sam Sirlin sam@kalessin.jpl.nasa.gov Sam Steingold sds@gnu.org Sam Varshavchik mrsam@courier-mta.com Sander Niemeijer niemeijer@science-and-technology.nl santilín listas@gestiong.org Scott Bambrough scottb@corelcomputer.com Scott McCreary scottmc2@gmail.com Scott Stanton stanton@scriptics.com Sebastian Freundt hroptatyr@gna.org Sergey Poznyakoff ? Simon Josefsson jas@extundo.com Simon Leinen simon@lia.di.epfl.ch Slava Sysoltsev Viatcheslav.Sysoltsev@h-d-gmbh.de Stefan Seefeld stefan@codesourcery.com Stefan `Sec' Zehl ? Stefano Lattarini stefano.lattarini@gmail.com Stepan Kasal kasal@ucw.cz Stéphane Chazelas Stephane_Chazelas@yahoo.fr Stephen Gildea filtered@against.spam Stephen Rasku srasku@mail.tantalus-systems.com Stephen P. Schaefer sschaefer@acm.org Steve Chamberlain sac@cygnus.com Steve Goetze goetze@dovetail.com Steve Huston shuston@riverace.com Steve Robbins steve@nyongwa.montreal.qc.ca Steven G. Johnson stevenj@alum.mit.edu Steven R. Loomis srl@icu-project.org Stu Grossman grossman@cygnus.com Sumit Pandya sumit@elitecore.com Syd Polk spolk@cygnus.com T.E. Dickey dickey@clark.net Ted Bullock tbullock@canada.com Theodore Ts'o tytso@mit.edu Thien-Thi Nguyen ttn@gnu.org Thomas Jahns jahns@dkrz.de Thomas Winder tom@vlsivie.tuwien.ac.at Tim Freeman tim@fungible.com Tim Mooney mooney@dogbert.cc.ndsu.NoDak.edu Tim Rice tim@multitalents.net Tim Van Holder tim.van.holder@pandora.be Tobias Burnus burnus@net-b.de Tom Browder tom.browder@gmail.com Tom Epperly tepperly@llnl.gov Tom Lane tgl@sss.pgh.pa.us Tom Purcell Tom.Purcell@wang.com Tom Tromey tromey@cygnus.com Tom Yu tlyu@mit.edu Tomohiro Suzuki ? Tony Leneis tony@plaza.ds.adp.com Toshio Kuratomi ? Uwe Seimet us@orbacus.com Václav Haisman v.haisman@sh.cvut.cz Vance Shipley vances@motivity.ca Viktor Dukhovni viktor@anaheim.esm.com Ville Karaila karaila@iki.fi Vincent Lefèvre vincent@vinc17.org Vincent Torri vtorri at univ-evry.fr Vladimir Volovich vvv@vsu.ru Volker Borchert bt@teknon.de Wayne Chapeskie waynec@spinnaker.com Werner Lemberg wl@gnu.org Wilfredo Sanchez wsanchez@apple.com William Pursell bill.pursell@gmail.com Wiseman Jun junwiseman@gmail.com Wolfgang Mueller Wolfgang.Mueller@cui.unige.ch Yaakov Selkowitz yselkowitz@users.sourceforge.net Yavor Doganov yavor@gnu.org Yury Puhalsky pooh@cryptopro.ru Zack Weinberg zack@codesourcery.com ? Seanster@Seanster.com Many people are not named here because we lost track of them. We thank them! Please, help us keep this list up to date. ================ Local Variables: mode: text coding: utf-8 End: Copyright (C) 1999-2012 Free Software Foundation, Inc. This program is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version. This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. You should have received a copy of the GNU General Public License along with this program. If not, see <http://www.gnu.org/licenses/>. PK [�!\���� � READMEnu �[��� -*- text -*- Autoconf Autoconf is an extensible package of M4 macros that produce shell scripts to automatically configure software source code packages. These scripts can adapt the packages to many kinds of UNIX-like systems without manual user intervention. Autoconf creates a configuration script for a package from a template file that lists the operating system features that the package can use, in the form of M4 macro calls. Producing configuration scripts using Autoconf requires GNU M4 and Perl. You should install GNU M4 (version 1.4.6 or later is required; 1.4.14 or later is recommended) and Perl (5.006 or later) before configuring Autoconf, so that Autoconf's configure script can find them. The configuration scripts produced by Autoconf are self-contained, so their users do not need to have Autoconf (or GNU M4, Perl, etc.). You can get GNU M4 here: ftp://ftp.gnu.org/gnu/m4/ The file INSTALL should be distributed with packages that use Autoconf-generated configure scripts and Makefiles that conform to the GNU coding standards. The package's README can just give an overview of the package, where to report bugs, and a pointer to INSTALL for instructions on compilation and installation. This removes the need to maintain many similar sets of installation instructions. Be sure to read BUGS and INSTALL. Mail suggestions to autoconf@gnu.org, report bugs to bug-autoconf@gnu.org, and submit patches to autoconf-patches@gnu.org. All changes can be tracked at the read-only autoconf-commit@gnu.org. Always include the Autoconf version number, which you can get by running `autoconf --version'. Archives of bug-autoconf@gnu.org can be found in <http://lists.gnu.org/archive/html/bug-autoconf/>, and similarly for the other mailing lists. Licensing Autoconf is released under the General Public License version 3 (GPLv3+). Additionally, Autoconf includes a licensing exception in some of its source files; see the respective copyright notices for how your project is impacted by including scripts generated by Autoconf, and the COPYING.EXCEPTION file for the exception in terms of the Additional Permissions as described in section 7 of GPLv3. For more licensing information, see <http://www.gnu.org/licenses/gpl-faq.html> and <http://www.gnu.org/licenses/exceptions.html>. For any copyright year range specified as YYYY-ZZZZ in this package note that the range specifies every single year in that closed interval. ----- Copyright (C) 1992-1994, 1998, 2000-2012 Free Software Foundation, Inc. Copying and distribution of this file, with or without modification, are permitted in any medium without royalty provided the copyright notice and this notice are preserved. This file is offered as-is, without warranty of any kind. PK [�!\�:v>T >T ChangeLognu �[��� 2012-04-24 Eric Blake <eblake@redhat.com> Release Version 2.69. * NEWS: Mention the release. 2012-04-24 Eric Blake <eblake@redhat.com> maint: drop bz2 tarball At 2.68b, I asked whether anyone would miss .gz and .bz2 formats. Consensus was overwhelming that .gz still holds a place in people's hearts, in spite of .xz compressing to smaller files, but no one was able to make a convincing argument for .bz2. * configure.ac (AM_INIT_AUTOMAKE): Drop bzip2; xz wins hands down. 2012-04-24 Eric Blake <eblake@redhat.com> maint: resync files from upstream The files in lib/Autom4te/ are intentionally not synced at this point, since this recent Automake patch: https://lists.gnu.org/archive/html/automake-patches/2012-03/msg00111.html was buggy regarding '-' as stdout, and also exposes some latent bugs in autoconf where we use raw 'open' instead of XFile::open. * build-aux/announce-gen: Resync via 'make fetch'. * build-aux/config.sub: Likewise. * build-aux/git-version-gen: Likewise. * build-aux/gnupload: Likewise. * build-aux/move-if-change: Likewise. * build-aux/texinfo.tex: Likewise. * doc/standards.texi: Likewise. * maint.mk: Likewise. 2012-04-24 Eric Blake <eblake@redhat.com> doc: fix bad @xref uses Upstream gnulib maint.mk improvements caught a few issues we should fix, as well as a few issues in files we copy from other sources that we will just ignore here. * doc/autoconf.texi (Generic Programs, Special Shell Variables) (Limitations of Builtins): Use references correctly. * cfg.mk (exclude_file_name_regexp--sc_prohibit_undesirable_word_seq) (exclude_file_name_regexp--sc_useless_cpp_parens): Add exemptions. 2012-04-24 Bruno Haible <bruno@clisp.org> AC_INIT: remove a transitional warning On bi-arch systems (such as x86 / x86_64) it is often necessary to pass the --host option together with an appropriate value for CC. But this triggers a warning: $ ./configure --host=i686-pc-linux-gnu CC="gcc -m32 -march=i586" configure: WARNING: if you wanted to set the --build type, don't use --host. If a cross compiler is detected then cross compile mode will be used .. This warning was introduced on 2000-06-30, in commit <http://git.savannah.gnu.org/gitweb/?p=autoconf.git;a=commitdiff;h=cb2e761b8e1181f97e8e09d85526bd22078433db> with the remark "Re-enable the old behavior of --host and --build." This warning was meant to warn users about a changed semantics of --build and --host. This change is now 12 years in the past; users have had enough time to learn it. I therefore suggest to remove the warning. I've done lots of cross and bi-arch compilations in the last 10 years, all with --host and without --build, and have never observed a problem with it, except for the warning. Simply relying on config.guess is sufficient. * lib/autoconf/general.m4 (_AC_INIT_PARSE_ARGS): Don't warn if --host given without --build. 2012-04-24 Bruno Haible <bruno@clisp.org> doc: fix incorrect and incomplete doc about cross-compilation mode * doc/autoconf.texi (Runtime): Mention the effect of the cross- compilation mode on AC_RUN_IFELSE. (Specifying Target Triplets): Fix description of --host's effects. (Hosts and Cross-Compilation): Remove incorrect statement about --host's effects. 2012-04-23 Paul Eggert <eggert@cs.ucla.edu> doc: document --build and cross-compilation better * doc/autoconf.texi (Specifying Target Triplets): Mention that specifying a build-type that differs from host-type enables cross-compilation. Problem reported by Bruno Haible in: http://lists.gnu.org/archive/html/autoconf-patches/2012-04/msg00009.html 2012-04-11 Jim Meyering <meyering@redhat.com> maint: avoid "make syntax-check" failure * cfg.mk (old_NEWS_hash): Update to reflect typo fix in old news. 2012-03-28 Stefano Lattarini <stefano.lattarini@gmail.com> cosmetics fix imprecise comment in Autom4te::General * lib/Autom4te/General.pm: This file is *not* used by Automake; adjust comments accordingly. 2012-03-07 Paul Eggert <eggert@cs.ucla.edu> tests: fix port of AT_CHECK_ENV to hosts with flaky grep * tests/local.at (AT_CHECK_ENV): Don't copy the buggy grep's diagnostics to stderr, as that causes AT_CHECK to fail. They can be found in the stderr-* files if this is needed for debugging. 2012-03-07 Eric Blake <eblake@redhat.com> docs: document set -n pitfalls * doc/autoconf.texi (Limitations of Builtins) <set>: Document issues with set -n. 2012-03-07 Eric Blake <eblake@redhat.com> build: require perl 5.6 This reduces the implicit requirement from 5.6.2 back to 5.6, while raising the explicit requirement to match the actual code. * configure.ac (PERL): Fail up front if perl is too old. * NEWS: Document this. * README: Likewise. * README-hacking: Likewise. * lib/Autom4te/ChannelDefs.pm: Bump requirement. * lib/Autom4te/General.pm: Relax requirement. 2012-03-07 Eric Blake <eblake@redhat.com> tests: ignore ksh -n warnings Recent ksh is noisy: $ ksh -nc '``'; echo $? ksh: warning: line 1: `...` obsolete, use $(...) 0 * tests/local.at (AT_CHECK_SHELL_SYNTAX): Ignore noisy ksh on. Reported by Martin Zaun. 2012-03-06 Paul Eggert <eggert@cs.ucla.edu> tests: port AT_CHECK_ENV to hosts with flaky grep * tests/local.at (AT_CHECK_ENV): Don't assume that if one grep fails, the other will too. It could be that 'grep' is flaky, and fails somewhat at random. This would explain the problems reported for autoconf-2.68b on FreeBSD and MacOS X, for example: <http://lists.gnu.org/archive/html/bug-autoconf/2012-03/msg00032.html> <http://lists.gnu.org/archive/html/bug-autoconf/2012-03/msg00035.html> <http://lists.gnu.org/archive/html/bug-autoconf/2012-03/msg00036.html> <http://lists.gnu.org/archive/html/bug-autoconf/2012-03/msg00044.html> 2012-03-06 Stefano Lattarini <stefano.lattarini@gmail.com> maint: resync files from upstream Since the perl version required in Automake::Getopt has been recently lowered from 5.6.2 to 5.6.0, this change has the nice effect of making autoconf compatible again with all perls in the 5.6.x release series. * maint.mk: Resync via 'make fetch'. * lib/Autom4te/Channels.pm: Likewise. * lib/Autom4te/Configure_ac.pm: Likewise. * lib/Autom4te/FileUtils.pm: Likewise. * lib/Autom4te/Getopt.pm: Likewise. * lib/Autom4te/XFile.pm: Likewise. 2012-03-05 Stefano Lattarini <stefano.lattarini@gmail.com> maint: drop syncing with Automake::Struct The module Automake::Struct has been removed in automake master branch (with yesterday's commit v1.11-2055-g74a7f49 "maint: drop 'Automake::Struct' module"): since Automake now requires Perl 5.6, that module has become obsolete, being basically just a backport of Perl 5.6's 'Class::Struct' to Perl 5.5. With this change, we follow suite in Autoconf, which syncs some of its internal modules with Automake. * lib/Autom4te/Struct.pm: Delete. * lib/Autom4te/Makefile.am (dist_perllib_DATA): Don't list it anymore. * cfg.mk: Don't sync it with the Automake repository anymore. * lib/Autom4te/Request.pm: Use 'Class::Struct' instead of 'Autom4te::Struct'. 2012-03-04 Paul Eggert <eggert@cs.ucla.edu> doc: mention PATH bug with "ksh foo" * doc/autoconf.texi (Invoking the Shell): Mention ksh PATH bug. 2012-03-04 Stefano Lattarini <stefano.lattarini@gmail.com> tests: fix spurious failure due to Solaris XPG4 sh bug On Solaris 10, the /usr/xpg4/bin/sh shell seems unable to execute a shell script named 'script': $ touch script $ /bin/sh script; echo status: $? # As expected. status: 0 $ /usr/xpg4/bin/sh script; echo status: $? # Weirdness follows. /usr/xpg4/bin/sh: script: cannot execute status: 1 This was causing a spurious testsuite failure for users which have /usr/xpg4/bin in $PATH before /bin and /usr/bin. Fix that. * tests/m4sh.at (Configure re-execs self with CONFIG_SHELL): Rename the m4sh-produced script to 'script2', to avoid the just-described issue. 2012-03-04 Stefano Lattarini <stefano.lattarini@gmail.com> tests: fix spurious failure when CONFIG_SITE is set * tests/m4sh.at (Configure re-execs self with CONFIG_SHELL): Export $CONFIG_SITE to "/dev/null", to avoid spurious diffs in expected stdout/stderr. 2012-03-03 Paul Eggert <eggert@cs.ucla.edu> fortran: clean up core files after AC_FC_CHECK_BOUNDS * lib/autoconf/fortran.m4 (AC_FC_CHECK_BOUNDS): Clean up core files, too. Needed for Sun Fortran 95 8.2 2005/10/13 on Solaris 8. tests: port AS_TR_SH and AS_TR_CPP test to Solaris 8 wc * tests/m4sh.at (AS@&t@_TR_SH and AS@&t@_TR_CPP): Do not assume that "wc -l" outputs only digits; on Solaris 8 it also outputs blanks and POSIX allows this. tests: fix "#/bin/sh" typo * tests/m4sh.at (AS@&t@_EXECUTABLE): "#!/bin/sh", not "#/bin/sh". Typo reported by Tim Rice in: http://lists.gnu.org/archive/html/autoconf-patches/2012-03/msg00009.html tests: port AS_EXECUTABLE_P test to Solaris 8 /bin/sh * tests/m4sh.at (AS@&t@_EXECUTABLE): Treat any nonzero exit status as failure. This is needed for Solaris 8 /bin/sh, where executing a nonexecutable file causes the shell to say the file had exit status 1. 2012-03-03 Stefano Lattarini <stefano.lattarini@gmail.com> configure: don't infloop when re-executing with $CONFIG_SHELL It turns out our guard against infinite recursion wasn't good enough when shells without $LINENO support were involved, since the creation-and-sourcing of configure.lineno broke the guard's expectations. Reports by Tim Rice and Paul Eggert. * lib/m4sugar/m4sh.m4 (_AS_LINENO_PREPARE): Export '_as_can_reexec' to "no" before sourcing the just-created configure.lineno. 2012-03-01 Paul Eggert <eggert@cs.ucla.edu> maint: spelling fixes 2012-03-01 Eric Blake <eblake@redhat.com> maint: post-release administrivia * NEWS: Add header line for next release. * .prev-version: Record previous version. * cfg.mk (old_NEWS_hash): Auto-update. 2012-03-01 Eric Blake <eblake@redhat.com> Release Version 2.68b. It's been more than a year since 2.68; time for a beta release to shake out any last minute bugs, before a release of 2.69 in the near future. * NEWS: Mention the release. * HACKING: Update some instructions. 2012-03-01 Eric Blake <eblake@redhat.com> maint: resync files from upstream * GNUmakefile: Resync via 'make fetch'. * build-aux/config.guess: Likewise. * build-aux/config.sub: Likewise. * build-aux/texinfo.tex: Likewise. * build-aux/update-copyright: Likewise. * doc/standards.texi: Likewise. * lib/Autom4te/Channels.pm: Likewise. * lib/Autom4te/Configure_ac.pm: Likewise. * lib/Autom4te/FileUtils.pm: Likewise. * lib/Autom4te/Getopt.pm: Likewise. * lib/Autom4te/Struct.pm: Likewise. * lib/Autom4te/XFile.pm: Likewise. * maint.mk: Likewise. 2012-02-25 Eric Blake <eblake@redhat.com> tests: add test for AS_EXECUTABLE_P Now that this is public, we should regression test it. * tests/m4sh.at (AS@&t@_EXECUTABLE): New test. 2012-02-24 Eric Blake <eblake@redhat.com> m4sh: make AS_EXECUTABLE_P public In the process of making it public, factor it into a reusable function. This makes constructs like AC_CHECK_PROGRAM smaller, as well as making libtool's naughty use of $as_executable_p safer. * lib/m4sugar/m4sh.m4 (_AS_TEST_PREPARE): Add a shell function. (AS_EXECUTABLE_P): Forward to shell function. * doc/autoconf.texi (Common Shell Constructs): Document it. * NEWS: Mention this. 2012-02-24 Eric Blake <eblake@redhat.com> m4sh: require that 'test -x' works 4.3BSD is no longer a reasonable portability target; and we are pretty sure that these days we can find at least one shell on any platform that supports 'test -x'. Drop a horribly unsafe use of eval as a result. :) Libtool still uses $as_executable_p without so much as calling either AS_TEST_X or AS_EXECUTABLE_P; even though the latter has existed, although undocumented, since at least 2.59; furthermore, libtool uses it in a context where filtering out directories would have been desirable. Shame on them. * lib/m4sugar/m4sh.m4 (_AS_TEST_X_WORKS): New probe. (AS_SHELL_SANITIZE, AS_INIT): Use it in shell searching. (AS_TEST_X, AS_EXECUTABLE_P): Simplify. 2012-02-24 Eric Blake <eblake@redhat.com> doc: mention more pitfalls of file mode tests 4.3BSD is museum-ware now, so we can assume that test -x exists; however, we still can't assume that it always does what we want. * doc/autoconf.texi (Limitations of Builtins) <test (files)>: Treat 'test -x' as mostly portable, but mention problems with root user, ACLs, and TOCTTOU races. 2012-02-16 Eric Blake <eblake@redhat.com> docs: tweak 'rm -f' limitations Based on http://debbugs.gnu.org/10819 and http://austingroupbugs.net/view.php?id=542 * doc/autoconf.texi (Limitations of Usual Tools) <rm>: More details on 'rm -f' without files. 2012-02-10 Paul Eggert <eggert@cs.ucla.edu> maint: replace FSF snail-mail addresses with URLs * tests/erlang.at, tests/go.at, tests/statesave.m4: Replace FSF snail mail addresses with URLs, as per GNU coding standards, and for consistency with other tests. 2012-01-28 Jim Meyering <meyering@redhat.com> maint: avoid "make syntax-check" failure * Makefile.am ($(srcdir)/INSTALL): Remove spurious space-before-TAB. 2012-01-23 Eric Blake <eblake@redhat.com> tests: fix test regression due to additional output This test has been failing since commit 5285ea8c (sadly, since last July; thankfully, unreleased). * tests/m4sugar.at (m4@&t@_require: nested): Fix test. 2012-01-23 Eric Blake <eblake@redhat.com> INSTALL: convert to '' quoting, drop blank line at end This is allowed by recent GNU Coding Standards changes, and mirrors recent gnulib changes: https://lists.gnu.org/archive/html/bug-gnulib/2012-01/msg00267.html https://lists.gnu.org/archive/html/bug-gnulib/2012-01/msg00298.html I've confirmed that after these changes, the INSTALL generated and installed by autoconf matches the INSTALL.ISO in gnulib. * Makefile.am ($(srcdir)/INSTALL): Match gnulib INSTALL.ISO. 2012-01-23 Jim Meyering <meyering@redhat.com> maint: convert .x-sc_* into exclude_file_name_regexp--sc_* exemptions Many of the .x-sc_* exemptions were no long necessary. Remove those files and instead, provide exemptions via variable definitions in cfg.mk to address the few remaining exceptions. * .x-sc_prohibit_atoi_atof: Remove file. * .x-sc_space_tab: Likewise. * .x-sc_sun_os_names: Likewise. * .x-sc_trailing_blank: Likewise. * .x-sc_two_space_separator_in_usage: Likewise. * .x-sc_useless_cpp_parens: Likewise. * cfg.mk: Add minimal exemptions. * cfg.mk: Add minimal exemptions. * doc/standards.texi (Standard C): Address the sole useless-cpp-parens violation in this file: -#if defined (__STDC__) || defined (WINDOWSNT) +#if defined __STDC__ || defined WINDOWSNT With that, the only remaining offender is config.guess, whose name is now listed in cfg.mk. Suggested by Eric Blake. 2012-01-23 Paul Eggert <eggert@cs.ucla.edu> doc: work around mingw-w64 alloca problem with example * doc/autoconf.texi (Particular Functions): In example code for alloca, do not re-#define alloca. This works around a mingw-w64 problem reported by Vincent Torri in <http://lists.gnu.org/archive/html/autoconf/2012-01/msg00018.html>. 2012-01-21 Jim Meyering <meyering@redhat.com> maint: fix or disable failing syntax-check rules * cfg.mk (local-checks-to-skip): List failing tests, so we skip them, for now. (old_NEWS_hash): Update. * doc/autoconf.texi: Per suggestion from Eric Blake, obfuscate the first word of "Filesystem Hierarchy Standard" as File@/system so it continues to render as one word, yet doesn't trigger the syntax-check prohibition. maint: also sync maint.mk and useless-if-before-free from gnulib * cfg.mk (gnulib-update): Add them to the list. * maint.mk: Update from gnulib. * build-aux/gitlog-to-changelog: Likewise. * build-aux/useless-if-before-free: New file, from gnulib. * doc/gnu-oids.texi: Update. maint.mk: update from gnulib * maint.mk: Update. maint: placate syntax-check rules: exempt some false positives * cfg.mk: Exempt maint.mk from the "undesirable word seq" check. Exempt maint.mk and autoconf.texi from the test_minus_ao check. maint: tweak to avoid triggering space-tab-prohibiting syntax-check * tests/m4sh.at (nargs): Use TAB-SP, not SP-TAB in abusive file name, to avoid triggering the space-tab-prohibiting syntax-check. maint: remove empty lines at EOF * man/autoconf.x: Remove empty line at EOF. * man/autoheader.x: Likewise. * man/autoscan.x: Likewise. * man/autoupdate.x: Likewise. * man/ifnames.x: Likewise. * tests/compile.at: Likewise. * doc/fdl.texi: Likewise. doc: fix grammar/doubled-word errors * doc/autoconf.texi: Remove/fix doubled-word errors. Also, s/can not/cannot/. * lib/m4sugar/m4sh.m4: Reword "if IF" comment to avoid triggering the doubled-word warning. 2012-01-21 Stefano Lattarini <stefano.lattarini@gmail.com> maint: sync files from gnulib * GNUmakefile: Sync from gnulib. * build-aux/announce-gen: Likewise. * build-aux/config.guess: Likewise. * build-aux/config.sub: Likewise. * build-aux/git-version-gen: Likewise. * build-aux/gnupload: Likewise. * build-aux/move-if-change: Likewise. * build-aux/texinfo.tex: Likewise. * build-aux/update-copyright: Likewise. * build-aux/vc-list-files: Likewise. * doc/gendocs_template: Likewise. * doc/standards.texi: Likewise. * m4/autobuild.m4: Likewise. 2012-01-21 Stefano Lattarini <stefano.lattarini@gmail.com> maint: make position of gnulib checkout configurable Some gnulib-related tools (most prominently, the gnulib-provided 'bootstrap' script) allow the user to define the position of his gnulib's repository checkout through the use of the 'GNULIB_SRCDIR' environment variable. We should do the same, for consistency and to easily support slightly unusual layouts in developers' source trees. * cfg.mk (gnulib_dir): Define to "$GNULIB_SRCDIR" if that's set, and to default value of "'$(abs_srcdir)'/../gnulib" otherwise. Update comments. 2012-01-20 Stefano Lattarini <stefano.lattarini@gmail.com> getopt: sync from Automake repository * lib/Autom4te/Getopt.am: The master copy of this file has been moved to the Automake repository (see Automake commit 'v1.11-662-g52246cc' 2012-01-18, "cmdline parsing: move into a dedicated perl module"). So we now we sync it from there, by listing it ... * cfg.mk (autom4te_files): ... in this variable. 2012-01-20 Stefano Lattarini <stefano.lattarini@gmail.com> build: fix automake error due to missing ChangeLog Apparently, Automake does not accept the '$(srcdir)/ChangeLog' target in Makefile.am as a declaration that ChangeLog is automatically generated (and thus does not need to exist at automake time). One has to use a *literal* 'ChangeLog' target. Problem introduced in commit v2.68-118-g6ed5195 of 2012-01-17, "maint: generate ChangeLog from git log". * Makefile.ma ($(srcdir)/ChangeLog): Renamed ... (ChangeLog): ... to this. 2012-01-17 Stefano Lattarini <stefano.lattarini@gmail.com> getopt: new Autom4te::Getopt module * lib/Autom4te/General.pm (getopt): Move the guts of its implementation ... * lib/Autom4te/Getopt.pm (parse_options): .. into this function in the new Autom4te::Getopt module. This will make it simpler for the implementation to be shared with other projects (right now, Automake). * lib/Automake/Makefile.am (dist_perllib_DATA): Add the new module. 2012-01-17 Jim Meyering <meyering@redhat.com> tests: avoid spurious failure for each gnu-fortran-using test The tests compare pre- and post-run lists of envvars, which must be the same, modulo a list of known, filtered-out exceptions. However, when running fortran-checking tests with GNU fortran, each would fail due to the post-run addition of the GFC symbol added in v2.68-97-gbd962ac. * tests/local.at (AT_CHECK_ENV): Add GFC to the list of symbols that we ignore in pre-/post-run environment diffs. 2012-01-17 Stefano Lattarini <stefano.lattarini@gmail.com> maint: generate ChangeLog from git log Following the practice set by various other GNU projects, we start to automatically generate the ChangeLog file from the git commit messages. This will avoid duplication (as the ChangeLog entries were always inserted both in the git commit message and in the version-controlled ChangeLog file), and potential problems with spurious merge conflicts (which, although greatly mitigated by Bruno Haible's `git-merge-changelog' helper program, have never been completely solved). * ChangeLog: Moved ... * ChangeLog.3: ... to this. * build-aux/gitlog-to-changelog: New script, synced from gnulib. * cfg.mk (gnulib-update): Also sync gitlog-to-changelog. * Makefile.am (gen-ChangeLog): New .PHONY rule, generate the ChangeLog for distribution. (dist-hook): Depend on it. ($(srcdir)/ChangeLog): New dummy rule, to pacify automake "gnu" strictness. Creates a dummy ChangeLog, that will be overridden by the proper one at distribution time. (gen_start_date): New variable, the date starting from which the git log entries are to be copied in the generated ChangeLog. (EXTRA_DIST): Add ChangeLog.3 and gitlog-to-changelog. * configure.ac (AC_CONFIG_SRCDIR): Use 'lib/autoconf/autoconf.m4' instead of 'ChangeLog' as the sentinel file. * .gitignore: Add ChangeLog. 2012-01-15 Stefano Lattarini <stefano.lattarini@gmail.com> cosmetics: fix some typos in ChangeLog PK [�!\�B�\ \ TODOnu �[��� PK [�!\B�j �> �> F\ NEWSnu �[��� PK [�!\HxAAt t ]� AUTHORSnu �[��� PK [�!\J jQ T T � THANKSnu �[��� PK [�!\���� � I READMEnu �[��� PK [�!\�:v>T >T J ChangeLognu �[��� PK � �n
| ver. 1.6 |
Github
|
.
| PHP 8.2.30 | ??????????? ?????????: 0.03 |
proxy
|
phpinfo
|
???????????