Gnu Autoconf

• Thread Index

• Compile-Run Cycle
  • From: Anarchean <anarchean@xxxxxxxxxxxxxxxxx>
• Re: [PATCH] autoheader: check templates of all config headers
  • From: Daniel Elstner <daniel.kitta@xxxxxxxxx>
• Re: [PATCH] autoheader: check templates of all config headers
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: [PATCH] autoheader: check templates of all config headers
  • From: Daniel Elstner <daniel.kitta@xxxxxxxxx>
• Re: Timeline for 2.70 (hit issue fixed in e17a30e9)
  • From: Mike Frysinger <vapier@xxxxxxxxxx>
• Re: Timeline for 2.70 (hit issue fixed in e17a30e9)
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Timeline for 2.70 (hit issue fixed in e17a30e9)
  • From: Andrei Borzenkov <arvidjaar@xxxxxxxxx>
• Trying to run autogen
  • From: Erik Moe <e.moe@xxxxxxx>
• Re: How to check for linker argument support?
  • From: Mike Frysinger <vapier@xxxxxxxxxx>
• Re: How to check for linker argument support?
  • From: Bent Bisballe Nyeng <deva@xxxxxxxxxxx>
• How to check for linker argument support?
  • From: Bent Bisballe Nyeng <deva@xxxxxxxxxxx>
• Autoconf tutorial updated
  • From: Edward Rosten <ed@xxxxxxxxxxxxxxxx>
• Re: Autoconf and a bare-metal host with no C library
  • From: Ineiev <ineiev@xxxxxxx>
• Re: Autoconf and a bare-metal host with no C library
  • From: Luca Saiu <positron@xxxxxxx>
• Re: Autoconf and a bare-metal host with no C library
  • From: Robert Woodworth <robertjwoodworth@xxxxxxxxx>
• Re: Autoconf and a bare-metal host with no C library
  • From: Keith Marshall <keith.d.marshall@xxxxxxxxxxxx>
• Re: Autoconf and a bare-metal host with no C library
  • From: Zack Weinberg <zackw@xxxxxxxxx>
• Re: Autoconf and a bare-metal host with no C library
  • From: Russell Shaw <rjshaw@xxxxxxxxxxxxxxx>
• Autoconf and a bare-metal host with no C library
  • From: Luca Saiu <positron@xxxxxxx>
• Symbian support
  • From: fedor_qd@xxxxxxx
• Re: Check perl module
  • From: Thomas Jahns <jahns@xxxxxxx>
• Re: Check perl module
  • From: Rudra Banerjee <bnrj.rudra@xxxxxxxx>
• Re: Check perl module
  • From: Gavin Smith <gavinsmith0123@xxxxxxxxx>
• Check perl module
  • From: Rudra Banerjee <bnrj.rudra@xxxxxxxx>
• [PATCH 1/2] mountlist: include sysmacros.h for glibc
  • From: Eric Blake <eblake@xxxxxxxxxx>
• [PATCH 2/2] sys_types: avoid glibc 2.25 warnings about major()
  • From: Eric Blake <eblake@xxxxxxxxxx>
• [gnulib PATCH 0/2] Work around glibc 2.25 deprecation warnings
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: m4_divert_text
  • From: Eric Blake <eblake@xxxxxxxxxx>
• m4_divert_text
  • From: Russell Shaw <rjshaw@xxxxxxxxxxxxxxx>
• Re: AC_HEADER_MAJOR vs. glibc 2.25(-to-be)
  • From: Zack Weinberg <zackw@xxxxxxxxx>
• Re: AC_HEADER_MAJOR vs. glibc 2.25(-to-be)
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: AC_HEADER_MAJOR vs. glibc 2.25(-to-be)
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: AC_HEADER_MAJOR vs. glibc 2.25(-to-be)
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: AC_HEADER_MAJOR vs. glibc 2.25(-to-be)
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: Control of .deps folder generation location.
  • From: "Andrew W. Nosenko" <andrew.w.nosenko@xxxxxxxxx>
• Re: Control of .deps folder generation location.
  • From: Bent Bisballe Nyeng <deva@xxxxxxxxxxx>
• Re: Control of .deps folder generation location.
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Control of .deps folder generation location.
  • From: Bent Bisballe Nyeng <deva@xxxxxxxxxxx>
• Re: Question on configure summary with subpackages
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Question on configure summary with subpackages
  • From: Juergen Reuter <juergen.reuter@xxxxxxx>
• Re: AC_HEADER_MAJOR vs. glibc 2.25(-to-be)
  • From: Zack Weinberg <zackw@xxxxxxxxx>
• Re: AC_HEADER_MAJOR vs. glibc 2.25(-to-be)
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: AC_HEADER_MAJOR vs. glibc 2.25(-to-be)
  • From: Zack Weinberg <zackw@xxxxxxxxx>
• Re: AC_HEADER_MAJOR vs. glibc 2.25(-to-be)
  • From: Zack Weinberg <zackw@xxxxxxxxx>
• Re: AC_HEADER_MAJOR vs. glibc 2.25(-to-be)
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: AC_HEADER_MAJOR vs. glibc 2.25(-to-be)
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: AC_HEADER_MAJOR vs. glibc 2.25(-to-be)
  • From: Nick Bowler <nbowler@xxxxxxxxxx>
• Re: AC_HEADER_MAJOR vs. glibc 2.25(-to-be)
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• AC_HEADER_MAJOR vs. glibc 2.25(-to-be)
  • From: Zack Weinberg <zackw@xxxxxxxxx>
• Re: ax_lib_hdf5 bug with library ordering, static libraries
  • From: Thomas Jahns <jahns@xxxxxxx>
• ax_lib_hdf5 bug with library ordering, static libraries
  • From: Harald Anlauf <anlauf@xxxxxx>
• Re: Using autoconf for a shared library
  • From: Marco Maggi <marco.maggi-ipsu@xxxxxxxx>
• Re: Using autoconf for a shared library
  • From: Thomas Nyberg <thomas@xxxxxxxxxxxxxxx>
• Re: Using autoconf for a shared library
  • From: Peter Johansson <trojkan@xxxxxxxxx>
• Re: Using autoconf for a shared library
  • From: Basin Ilya <basinilya@xxxxxxxxx>
• Using autoconf for a shared library
  • From: Thomas Nyberg <thomas@xxxxxxxxxxxxxxx>
• Using autoconf for a shared library
  • From: Thomas Nyberg <thomas@xxxxxxxxxxxxxxx>
• Using autoconf for a shared library
  • From: Thomas Nyberg <thomas@xxxxxxxxxxxxxxx>
• Re: Release Autoconf 2.70
  • From: Mike Frysinger <vapier@xxxxxxxxxx>
• Re: How to update config.guess?
  • From: Wookey <wookey@xxxxxxxxxxxx>
• Re: How to update config.guess?
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Re: How to update config.guess?
  • From: Václav Haisman <vhaisman@xxxxxxxxx>
• How to update config.guess?
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Need help with autoconf generating Makefile.in for a simple X Windows program embedded within an Emacs Lisp program
  • From: Robert Weiner <rsw@xxxxxxx>
• Re: Conditionally including macros that require a newer autoconf version
  • From: Rainer Gerhards <rgerhards@xxxxxxxxx>
• Re: Conditionally including macros that require a newer autoconf version
  • From: Nick Bowler <nbowler@xxxxxxxxxx>
• Conditionally including macros that require a newer autoconf version
  • From: Rainer Gerhards <rgerhards@xxxxxxxxx>
• Re: Release Autoconf 2.70
  • From: Gavin Smith <gavinsmith0123@xxxxxxxxx>
• Re: Release Autoconf 2.70
  • From: Julien ÉLIE <julien@xxxxxxxxxxxxxxx>
• Re: Autoconf Digest, Vol 147, Issue 4
  • From: Keith Bostic <keith.bostic@xxxxxxxxxxx>
• Re: Release Autoconf 2.70
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: Release Autoconf 2.70
  • From: Marko Lindqvist <cazfi74@xxxxxxxxx>
• Re: Release Autoconf 2.70
  • From: Zack Weinberg <zackw@xxxxxxxxx>
• Re: Release Autoconf 2.70
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Release Autoconf 2.70
  • From: Craig Andrews <candrews@xxxxxxxxxxxxxxxx>
• Re: Detect Autoconf run in preprocessor?
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: Detect Autoconf run in preprocessor?
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Re: Detect Autoconf run in preprocessor?
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Re: Detect Autoconf run in preprocessor?
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: Detect Autoconf run in preprocessor?
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• Re: Detect Autoconf run in preprocessor?
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Detect Autoconf run in preprocessor?
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Convey C++ STL library for Android?
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Re: running autoconf in chrooted environments
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: running autoconf in chrooted environments
  • From: Eric Blake <eblake@xxxxxxxxxx>
• running autoconf in chrooted environments
  • From: Peter Crady <pcrady@xxxxxxxx>
• non-recursive autoconf w/ recursive automake/make?
  • From: Jay K <jay.krell@xxxxxxxxxxx>
• suggest AC_SYS_LARGEFILE should #define _LARGEFILE, at least for VMS
  • From: Jay K <jay.krell@xxxxxxxxxxx>
• Re: Background processes in GNU Autotest
  • From: Olaf Mandel <olaf@xxxxxxxxxxx>
• Re: OPENMP_FLAGS in autoconf not working
  • From: Rudra Banerjee <bnrj.rudra@xxxxxxxxx>
• Re: OPENMP_FLAGS in autoconf not working
  • From: Rudra Banerjee <bnrj.rudra@xxxxxxxxx>
• Re: OPENMP_FLAGS in autoconf not working
  • From: Zack Weinberg <zackw@xxxxxxxxx>
• Re: OPENMP_FLAGS in autoconf not working
  • From: Rudra Banerjee <bnrj.rudra@xxxxxxxxx>
• Re: OPENMP_FLAGS in autoconf not working
  • From: Rudra Banerjee <bnrj.rudra@xxxxxxxxx>
• Re: OPENMP_FLAGS in autoconf not working
  • From: Nick Bowler <nbowler@xxxxxxxxxx>
• OPENMP_FLAGS in autoconf not working
  • From: Rudra Banerjee <bnrj.rudra@xxxxxxxxx>
• Re: Background processes in GNU Autotest
  • From: Mike Frysinger <vapier@xxxxxxxxxx>
• Re: Background processes in GNU Autotest
  • From: Olaf Mandel <olaf@xxxxxxxxxxx>
• Re: Background processes in GNU Autotest
  • From: Mike Frysinger <vapier@xxxxxxxxxx>
• Background processes in GNU Autotest
  • From: Olaf Mandel <olaf@xxxxxxxxxxx>
• Re: $sysconfdir substitution
  • From: Kip Warner <kip@xxxxxxxxxxxxxx>
• Re: $sysconfdir substitution
  • From: Kip Warner <kip@xxxxxxxxxxxxxx>
• Re: $sysconfdir substitution
  • From: Kip Warner <kip@xxxxxxxxxxxxxx>
• Re: $sysconfdir substitution
  • From: Nick Bowler <nbowler@xxxxxxxxxx>
• Re: $sysconfdir substitution
  • From: Gavin Smith <gavinsmith0123@xxxxxxxxx>
• Re: $sysconfdir substitution
  • From: Kip Warner <kip@xxxxxxxxxxxxxx>
• Re: $sysconfdir substitution
  • From: Gavin Smith <gavinsmith0123@xxxxxxxxx>
• Re: $sysconfdir substitution
  • From: Peter Johansson <trojkan@xxxxxxxxx>
• $sysconfdir substitution
  • From: Kip Warner <kip@xxxxxxxxxxxxxx>
• Re: Using "m4_bpatsubst/patsubst" to remove a string from a variable
  • From: Zack Weinberg <zackw@xxxxxxxxx>
• Re: Using "m4_bpatsubst/patsubst" to remove a string from a variable
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: Using "m4_bpatsubst/patsubst" to remove a string from a variable
  • From: Manuel Bachmann <manuel.bachmann@xxxxxxx>
• Re: Using "m4_bpatsubst/patsubst" to remove a string from a variable
  • From: Zack Weinberg <zackw@xxxxxxxxx>
• Using "m4_bpatsubst/patsubst" to remove a string from a variable
  • From: Manuel Bachmann <manuel.bachmann@xxxxxxx>
• Re: Output additional header file
  • From: Keith Marshall <keithmarshall@xxxxxxxxxxxxxxxxxxxxx>
• Re: Output additional header file
  • From: "A.P. Horst" <ariehorst@xxxxxxxxx>
• Re: Output additional header file
  • From: Gavin Smith <gavinsmith0123@xxxxxxxxx>
• Re: Output additional header file
  • From: "A.P. Horst" <ariehorst@xxxxxxxxx>
• Re: Output additional header file
  • From: Keith Marshall <keithmarshall@xxxxxxxxxxxxxxxxxxxxx>
• Re: Output additional header file
  • From: "A.P. Horst" <ariehorst@xxxxxxxxx>
• Re: Output additional header file
  • From: Gavin Smith <gavinsmith0123@xxxxxxxxx>
• Output additional header file
  • From: "A.P. Horst" <ariehorst@xxxxxxxxx>
• Cache variable name for AC_CHECK_LIBS
  • From: Bert Wesarg <bert.wesarg@xxxxxxxxxxxxxx>
• Re: Call the AC_CHECK_HEADER macro on a condition
  • From: Julien ÉLIE <julien@xxxxxxxxxxxxxxx>
• Re: Call the AC_CHECK_HEADER macro on a condition
  • From: Thomas Petazzoni <thomas.petazzoni@xxxxxxxxxxxxxxxxxx>
• Re: Call the AC_CHECK_HEADER macro on a condition
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: OS400
  • From: Earnie <earnie@xxxxxxxxxxxxxxxxxxxxx>
• Re: Call the AC_CHECK_HEADER macro on a condition
  • From: Earnie <earnie@xxxxxxxxxxxxxxxxxxxxx>
• Re: Call the AC_CHECK_HEADER macro on a condition
  • From: YuGiOhJCJ Mailing-List <yugiohjcj-mailinglist@xxxxxxxxxxx>
• Re: Call the AC_CHECK_HEADER macro on a condition
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: Call the AC_CHECK_HEADER macro on a condition
  • From: Nick Bowler <nbowler@xxxxxxxxxx>
• Call the AC_CHECK_HEADER macro on a condition
  • From: YuGiOhJCJ Mailing-List <yugiohjcj-mailinglist@xxxxxxxxxxx>
• OS400
  • From: Iglesias, Gérard (FircoSoft) <Gerard.Iglesias@xxxxxxxxxxxxx>
• Re: Definition of AC_CHECK_FUNCS
  • From: Nikita Karetnikov <nikita@xxxxxxxxxxxxxx>
• Re: Definition of AC_CHECK_FUNCS
  • From: Mathieu Lirzin <mthl@xxxxxxx>
• Definition of AC_CHECK_FUNCS
  • From: Nikita Karetnikov <nikita@xxxxxxxxxxxxxx>
• Re: --site option
  • From: Ben Elliston <bje@xxxxxxxxxx>
• Re: --site option
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• --site option
  • From: Ben Elliston <bje@xxxxxxxxxx>
• Re: Add clang++ to AC_PROG_CXX
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: Add clang++ to AC_PROG_CXX
  • From: Richard Stallman <rms@xxxxxxx>
• Re: autoconf check for building shared library
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• autoconf check for building shared library
  • From: Will Parsons <varro@xxxxxxxxxxxxxxxxxxxx>
• Re: Add clang++ to AC_PROG_CXX
  • From: Russ Allbery <eagle@xxxxxxxxx>
• Re: Dropping support for all non-free tools (was: Add clang++ to AC_PROG_CXX)
  • From: Dustin Laurence <dllaurence@xxxxxxxxxxxxxx>
• Dropping support for all non-free tools (was: Add clang++ to AC_PROG_CXX)
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Re: Add clang++ to AC_PROG_CXX
  • From: Ruben Safir <ruben@xxxxxxxxxxxx>
• Re: Add clang++ to AC_PROG_CXX
  • From: Václav Haisman <vhaisman@xxxxxxxxx>
• Re: Add clang++ to AC_PROG_CXX
  • From: Ruben Safir <ruben@xxxxxxxxxxxx>
• Re: Add clang++ to AC_PROG_CXX
  • From: Ruben Safir <ruben@xxxxxxxxxxxx>
• Re: Add clang++ to AC_PROG_CXX
  • From: Ruben Safir <ruben@xxxxxxxxxxxx>
• Re: Add clang++ to AC_PROG_CXX
  • From: Ruben Safir <ruben@xxxxxxxxxxxx>
• Re: Add clang++ to AC_PROG_CXX
  • From: Ruben Safir <ruben@xxxxxxxxxxxx>
• Re: Add clang++ to AC_PROG_CXX
  • From: Ruben Safir <ruben@xxxxxxxxxxxx>
• Re: Add clang++ to AC_PROG_CXX
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Re: Add clang++ to AC_PROG_CXX
  • From: Václav Haisman <vhaisman@xxxxxxxxx>
• Re: Add clang++ to AC_PROG_CXX
  • From: Ruben Safir <ruben@xxxxxxxxxxxx>
• Re: Using LLVM with Autotools
  • From: Mike Miller <mtmiller@xxxxxxxxxx>
• Re: Clean rebuild
  • From: Gavin Smith <gavinsmith0123@xxxxxxxxx>
• Clean rebuild
  • From: Russell Wallace <russell.wallace@xxxxxxxxx>
• Re: Transferring variables from configure.ac to Makefile.am
  • From: Nick Bowler <nbowler@xxxxxxxxxx>
• Transferring variables from configure.ac to Makefile.am
  • From: Russell Wallace <russell.wallace@xxxxxxxxx>
• Re: Using LLVM with Autotools
  • From: Russell Wallace <russell.wallace@xxxxxxxxx>
• Re: Using LLVM with Autotools
  • From: Gavin Smith <gavinsmith0123@xxxxxxxxx>
• Re: Using LLVM with Autotools
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Re: Using LLVM with Autotools
  • From: Russell Wallace <russell.wallace@xxxxxxxxx>
• Re: Using LLVM with Autotools
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Using LLVM with Autotools
  • From: Russell Wallace <russell.wallace@xxxxxxxxx>
• Re: m4_set_contains cannot find key
  • From: Eric Blake <eblake@xxxxxxxxxx>
• m4_set_contains cannot find key
  • From: Petre Pircalabu <petre.pircalabu@xxxxxxxxx>
• Re: m4_set_contains cannot find key
  • From: Petre Pircalabu <petre.pircalabu@xxxxxxxxx>
• Re: Add clang++ to AC_PROG_CXX
  • From: Václav Haisman <vhaisman@xxxxxxxxx>
• Re: Add clang++ to AC_PROG_CXX
  • From: Earnie <earnie@xxxxxxxxxxxxxxxxxxxxx>
• Re: Add clang++ to AC_PROG_CXX
  • From: Václav Haisman <vhaisman@xxxxxxxxx>
• Re: C11 and C++11 support detection fails with clang
  • From: Mike Miller <mtmiller@xxxxxxxxxx>
• Re: Add clang++ to AC_PROG_CXX
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: C11 and C++11 support detection fails with clang
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Modification of CXX and re-evaluation of dependent variables
  • From: Enrico Maria Crisostomo <enrico.m.crisostomo@xxxxxxxxx>
• Re: Compiling for newer Intel CPUs with an older Intel build system?
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• Re: Compiling for newer Intel CPUs with an older Intel build system?
  • From: Sean Byland <seanb@xxxxxxxx>
• Re: Compiling for newer Intel CPUs with an older Intel build system?
  • From: Sean Byland <seanb@xxxxxxxx>
• Re: Compiling for newer Intel CPUs with an older Intel build system?
  • From: Mike Frysinger <vapier@xxxxxxxxxx>
• Re: Compiling for newer Intel CPUs with an older Intel build system?
  • From: Nick Bowler <nbowler@xxxxxxxxxx>
• Re: Compiling for newer Intel CPUs with an older Intel build system?
  • From: Mike Frysinger <vapier@xxxxxxxxxx>
• Re: Compiling for newer Intel CPUs with an older Intel build system?
  • From: Nick Bowler <nbowler@xxxxxxxxxx>
• Compiling for newer Intel CPUs with an older Intel build system?
  • From: Sean Byland <seanb@xxxxxxxx>
• Re: C11 and C++11 support detection fails with clang
  • From: Nick Bowler <nbowler@xxxxxxxxxx>
• Re: C11 and C++11 support detection fails with clang
  • From: Mike Miller <mtmiller@xxxxxxxxxx>
• C11 and C++11 support detection fails with clang
  • From: Mike Miller <mtmiller@xxxxxxxxxx>
• Re: Automatic autoheader invocations for AC_DEFINE changes in m4-files
  • From: Luke Mewburn <lukem@xxxxxxxxxx>
• Re: Automatic autoheader invocations for AC_DEFINE changes in m4-files
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Automatic autoheader invocations for AC_DEFINE changes in m4-files
  • From: Marko Lindqvist <cazfi74@xxxxxxxxx>
• Re: OpenLDAP Configure failed
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• OpenLDAP Configure failed
  • From: Kartikeswar K <kartikeswar@xxxxxxxxx>
• Re: Using autotest with Emacs’ compilation mode
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: Using autotest with Emacs’ compilation mode
  • From: Nikolai Weibull <now@xxxxxxx>
• Re: Using autotest with Emacs’ compilation mode
  • From: Nikolai Weibull <now@xxxxxxx>
• Using autotest with Emacs’ compilation mode
  • From: Nikolai Weibull <now@xxxxxxx>
• Re: Hierarchical autoconf project with cross-compiled subproject
  • From: panic <lists@xxxxxxxxx>
• Re: Autoconf can't find X11 libraries
  • From: Earnie <earnie@xxxxxxxxxxxxxxxxxxxxx>
• Re: Hierarchical autoconf project with cross-compiled subproject
  • From: Wookey <wookey@xxxxxxxxxxxx>
• Hierarchical autoconf project with cross-compiled subproject
  • From: panic <lists@xxxxxxxxx>
• Re: Autoconf can't find X11 libraries
  • From: anatoly techtonik <techtonik@xxxxxxxxx>
• Re: Autoconf can't find X11 libraries
  • From: Thomas Dickey <dickey@xxxxxxx>
• Conflict between standard headers and winsock(2).h
  • From: Marko Lindqvist <cazfi74@xxxxxxxxx>
• Re: Autoconf can't find X11 libraries
  • From: anatoly techtonik <techtonik@xxxxxxxxx>
• Re: Autoconf can't find X11 libraries
  • From: Thomas Dickey <dickey@xxxxxxx>
• Re: AC_PROG_CC_C99 should prefer "c99" as name of compiler
  • From: Earnie <earnie@xxxxxxxxxxxxxxxxxxxxx>
• Re: AC_PROG_CC_C99 should prefer "c99" as name of compiler
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• AC_PROG_CC_C99 should prefer "c99" as name of compiler
  • From: Gavin Smith <gavinsmith0123@xxxxxxxxx>
• Autoconf can't find X11 libraries
  • From: anatoly techtonik <techtonik@xxxxxxxxx>
• Re: [PATCH] autoheader: check templates of all config headers
  • From: Warren Young <wyml@xxxxxxxxxxx>
• Re: [PATCH] autoheader: check templates of all config headers
  • From: Daniel Elstner <daniel.kitta@xxxxxxxxx>
• Re: [Qemu-devel] [Bug 1525682] Re: configure: fix POSIX compatibility issue
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: Struggling to build autoconf 2.69
  • From: SF Markus Elfring <elfring@xxxxxxxxxxxxxxxxxxxxx>
• Struggling to build autoconf 2.69
  • From: Kevin Connor Arpe <kevinarpe@xxxxxxxxx>
• Re: AC_CONFIG_SUBDIRS but immediately
  • From: Gavin Smith <gavinsmith0123@xxxxxxxxx>
• AC_CONFIG_SUBDIRS but immediately
  • From: Gavin Smith <gavinsmith0123@xxxxxxxxx>
• Re: Cross-compiling with Autoconf
  • From: Dustin Laurence <dllaurence@xxxxxxxxxxxxxx>
• Re: Cross-compiling with Autoconf
  • From: Dustin Laurence <dllaurence@xxxxxxxxxxxxxx>
• Re: Cross-compiling with Autoconf
  • From: Dustin Laurence <dllaurence@xxxxxxxxxxxxxx>
• Re: Cross-compiling with Autoconf
  • From: Dustin Laurence <dllaurence@xxxxxxxxxxxxxx>
• Re: Cross-compiling with Autoconf
  • From: Dustin Laurence <dllaurence@xxxxxxxxxxxxxx>
• Re: Cross-compiling with Autoconf
  • From: Nick Bowler <nbowler@xxxxxxxxxx>
• Re: Cross-compiling with Autoconf
  • From: Gavin Smith <gavinsmith0123@xxxxxxxxx>
• Re: Cross-compiling with Autoconf
  • From: Gavin Smith <gavinsmith0123@xxxxxxxxx>
• Cross-compiling with Autoconf
  • From: Dustin Laurence <dllaurence@xxxxxxxxxxxxxx>
• Re: How to programmatically detect awk flavor (e.g. gawk vs mawk vs nawk vs awk)
  • From: Nick Bowler <nbowler@xxxxxxxxxx>
• Re: How to programmatically detect awk flavor (e.g. gawk vs mawk vs nawk vs awk)
  • From: Eric Blake <eblake@xxxxxxxxxx>
• How to programmatically detect awk flavor (e.g. gawk vs mawk vs nawk vs awk)
  • From: Itamar Gal <itamarggal@xxxxxxxxx>
• Re: [PATCH] autoheader: check templates of all config headers
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• [PATCH] autoheader: check templates of all config headers
  • From: Daniel Elstner <daniel.kitta@xxxxxxxxx>
• Re: Autoconf Digest, Vol 138, Issue 2
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: Autoconf Digest, Vol 138, Issue 2
  • From: Keith Bostic <keith.bostic@xxxxxxxxxxx>
• Re: Patch for AC_FC_MODULE_OUTPUT_FLAG
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Patch for AC_FC_MODULE_OUTPUT_FLAG
  • From: Thomas Jahns <jahns@xxxxxxx>
• Re: extract value of ${datadir}
  • From: Peter Johansson <trojkan@xxxxxxxxx>
• Re: extract value of ${datadir}
  • From: Peter Johansson <trojkan@xxxxxxxxx>
• Re: extract value of ${datadir}
  • From: Mike Frysinger <vapier@xxxxxxxxxx>
• Re: extract value of ${datadir}
  • From: Gavin Smith <gavinsmith0123@xxxxxxxxx>
• extract value of ${datadir}
  • From: Peter Johansson <trojkan@xxxxxxxxx>
• Re: Handling of sub-packages by autoconf interfaces
  • From: SF Markus Elfring <elfring@xxxxxxxxxxxxxxxxxxxxx>
• Re: autocon and sub-packages
  • From: Warren Young <wyml@xxxxxxxxxxx>
• Re: autocon and sub-packages
  • From: Warren Young <wyml@xxxxxxxxxxx>
• Re: Handling of sub-packages by autoconf interfaces
  • From: SF Markus Elfring <elfring@xxxxxxxxxxxxxxxxxxxxx>
• Re: autocon and sub-packages
  • From: Sébastien Hinderer <Sebastien.Hinderer@xxxxxxxx>
• Re: autocon and sub-packages
  • From: Wookey <wookey@xxxxxxxxxxxx>
• Re: autocon and sub-packages
  • From: Warren Young <wyml@xxxxxxxxxxx>
• Re: autocon and sub-packages
  • From: Sébastien Hinderer <Sebastien.Hinderer@xxxxxxxx>
• Re: autocon and sub-packages
  • From: Ralf Corsepius <rc040203@xxxxxxxxxx>
• Re: Handling of sub-packages by autoconf interfaces
  • From: SF Markus Elfring <elfring@xxxxxxxxxxxxxxxxxxxxx>
• Re: autocon and sub-packages
  • From: Earnie <earnie@xxxxxxxxxxxxxxxxxxxxx>
• Re: autocon and sub-packages
  • From: Sébastien Hinderer <Sebastien.Hinderer@xxxxxxxx>
• Re: autocon and sub-packages
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: Handling of sub-packages by autoconf interfaces
  • From: SF Markus Elfring <elfring@xxxxxxxxxxxxxxxxxxxxx>
• autocon and sub-packages
  • From: Sébastien Hinderer <Sebastien.Hinderer@xxxxxxxx>
• Re: How can I always cross compile even when host and build are the same?
  • From: Nick Bowler <nbowler@xxxxxxxxxxxxxxxx>
• How can I always cross compile even when host and build are the same?
  • From: Steven Stewart-Gallus <sstewartgallus00@xxxxxxxxxxxxxxx>
• Instructions to compile and install autoconf
  • From: Vishnu Vardhan Makkapati <vishnu.makkapati@xxxxxxxxxx>
• Re: Instructions to compile and install autoconf
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: Trouble submitting patch
  • From: Daniel Elstner <daniel.kitta@xxxxxxxxx>
• Re: Trouble submitting patch
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Trouble submitting patch
  • From: Daniel Elstner <daniel.kitta@xxxxxxxxx>
• [PATCH] config.status: Allow dos style line endings in config.in.
  • From: Andrew Burgess <andrew.burgess@xxxxxxxxxxxx>
• Re: 'pkglibexecdir' is not a legitimate directory
  • From: Gavin Smith <gavinsmith0123@xxxxxxxxx>
• 'pkglibexecdir' is not a legitimate directory
  • From: Itamar Gal <itamarggal@xxxxxxxxx>
• More support for configuration header files?
  • From: SF Markus Elfring <elfring@xxxxxxxxxxxxxxxxxxxxx>
• AC_COMPILE_IFELSE equivalent for CCAS
  • From: "D'Alessandro, Luke K" <ldalessa@xxxxxxxxxxx>
• Fixing "autoheader: warning: missing template: HAVE_…"?
  • From: SF Markus Elfring <elfring@xxxxxxxxxxxxxxxxxxxxx>
• Re: Fwd: installation of automake, autoconf, m4 error
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• Fwd: installation of automake, autoconf, m4 error
  • From: Krishnan Rajiyah <krajiyah@xxxxxxxxx>
• Re: autoconf not passing all the flags needed to g++
  • From: Gavin Smith <gavinsmith0123@xxxxxxxxx>
• autoconf not passing all the flags needed to g++
  • From: Robert Stolarz <robert.stolarz@xxxxxxxxxx>
• Re: obscure failures when RAM is low
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• Re: obscure failures when RAM is low
  • From: Daniel Pocock <daniel@xxxxxxxxxx>
• Re: obscure failures when RAM is low
  • From: Zack Weinberg <zackw@xxxxxxxxx>
• Re: obscure failures when RAM is low
  • From: Daniel Pocock <daniel@xxxxxxxxxx>
• Re: obscure failures when RAM is low
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• obscure failures when RAM is low
  • From: Daniel Pocock <daniel@xxxxxxxxxx>
• RE: autoconf execution needs root permission
  • From: Marslo Jiao <Marslo_Jiao@xxxxxxxxxxxx>
• Re: autoconf execution needs root permission
  • From: Eric Blake <eblake@xxxxxxxxxx>
• autoconf execution needs root permission
  • From: Marslo Jiao <Marslo_Jiao@xxxxxxxxxxxx>
• Re: macro which returns found compiler for given language?
  • From: Diab Jerius <djerius@xxxxxxxxxxxxxxx>
• Re: macro which returns found compiler for given language?
  • From: Nick Bowler <nbowler@xxxxxxxxxxxxxxxx>
• Re: macro which returns found compiler for given language?
  • From: Diab Jerius <djerius@xxxxxxxxxxxxxxx>
• Re: macro which returns found compiler for given language?
  • From: Diab Jerius <djerius@xxxxxxxxxxxxxxx>
• RE: macro which returns found compiler for given language?
  • From: "Daily, Jeff A" <jeff.daily@xxxxxxxx>
• macro which returns found compiler for given language?
  • From: Diab Jerius <djerius@xxxxxxxxxxxxxxx>
• Swapping ac_link after LT_INIT
  • From: Thomas Jahns <jahns@xxxxxxx>
• Re: Compiling 32 bit lib on 64 bit OS
  • From: Zack Weinberg <zackw@xxxxxxxxx>
• Compiling 32 bit lib on 64 bit OS
  • From: Scott Fererro <Scott.Fererro@xxxxxxxx>
• Re: Want to add support for D (via GDC) to Autoconf - how do I start?
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Want to add support for D (via GDC) to Autoconf - how do I start?
  • From: Koz Ross <koz.ross@xxxxxxxxxx>
• Re: source directory already configured
  • From: Bert Wesarg <bert.wesarg@xxxxxxxxxxxxxx>
• source directory already configured
  • From: t.martitz@xxxxxx
• RE: sysconfdir
  • From: John Calcote <john.calcote@xxxxxxxxx>
• Re: sysconfdir
  • From: Eric Blake <eblake@xxxxxxxxxx>
• sysconfdir
  • From: Roman Neuhauser <neuhauser@xxxxxxxxxx>
• Re: m4_pattern_forbid
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: m4_pattern_forbid
  • From: Matěj Týč <matej.tyc@xxxxxxxxx>
• Re: named diversions
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: named diversions
  • From: Matěj Týč <matej.tyc@xxxxxxxxx>
• Re: named diversions
  • From: Eric Blake <eblake@xxxxxxxxxx>
• named diversions
  • From: Matěj Týč <matej.tyc@xxxxxxxxx>
• Re: m4_pattern_forbid
  • From: Matěj Týč <matej.tyc@xxxxxxxxx>
• Re: m4_pattern_forbid
  • From: Eric Blake <eblake@xxxxxxxxxx>
• m4_pattern_forbid
  • From: Matěj Týč <matej.tyc@xxxxxxxxx>
• Re: Having trouble using AC_CHECK_LIB
  • From: Peter Johansson <trojkan@xxxxxxxxx>
• Re: Having trouble using AC_CHECK_LIB
  • From: Julian Marchant <onpon4@xxxxxxxxxx>
• Re: Having trouble using AC_CHECK_LIB
  • From: Zack Weinberg <zackw@xxxxxxxxx>
• Re: Having trouble using AC_CHECK_LIB
  • From: Julian Marchant <onpon4@xxxxxxxxxx>
• Re: Having trouble using AC_CHECK_LIB
  • From: Mike Frysinger <vapier@xxxxxxxxxx>
• Re: Having trouble using AC_CHECK_LIB
  • From: Julian Marchant <onpon4@xxxxxxxxxx>
• Re: Having trouble using AC_CHECK_LIB
  • From: Julian Marchant <onpon4@xxxxxxxxxx>
• Re: Having trouble using AC_CHECK_LIB
  • From: Gavin Smith <gavinsmith0123@xxxxxxxxx>
• Re: Having trouble using AC_CHECK_LIB
  • From: Harlan Stenn <stenn@xxxxxxx>
• Having trouble using AC_CHECK_LIB
  • From: Julian Marchant <onpon4@xxxxxxxxxx>
• Re: config summary output?
  • From: Harlan Stenn <stenn@xxxxxxx>
• Re: config summary output?
  • From: Bert Wesarg <bert.wesarg@xxxxxxxxxxxxxx>
• config summary output?
  • From: Harlan Stenn <stenn@xxxxxxx>
• AC_CONFIG_SUBDIRS
  • From: Evrim Ulu <evrimulu@xxxxxxxxx>
• Re: What is the best/recommended technique for referencing development libraries?
  • From: Patrick Doyle <wpdster@xxxxxxxxx>
• Re: emacs autoconf mode
  • From: Zack Weinberg <zackw@xxxxxxxxx>
• Re: emacs autoconf mode
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: What is the best/recommended technique for referencing development libraries?
  • From: Thomas Jahns <jahns@xxxxxxx>
• Re: How To Configure for Android? (Redux for x86_64)
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Re: What is the best/recommended technique for referencing development libraries?
  • From: Mike Frysinger <vapier@xxxxxxxxxx>
• Re: How To Configure for Android? (Redux for x86_64)
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: How To Configure for Android? (Redux for x86_64)
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Bug#776559: autoupdate: add option that reports needed updates to configure.ac
  • From: Ben Pfaff <blp@xxxxxxxxxxxxxxx>
• Re: How To Configure for Android? (Redux for x86_64)
  • From: Mike Frysinger <vapier@xxxxxxxxxx>
• Re: emacs autoconf mode
  • From: Harlan Stenn <stenn@xxxxxxx>
• Re: emacs autoconf mode
  • From: Eric Blake <eblake@xxxxxxxxxx>
• emacs autoconf mode
  • From: Harlan Stenn <stenn@xxxxxxx>
• Shouldn't I be able to set unrecognised target triples?
  • From: Steven Stewart-Gallus <sstewartgallus00@xxxxxxxxxxxxxxx>
• Documentation issues regarding AC_CONFIG_LINKS
  • From: Nikolai Weibull <now@xxxxxxx>
• Re: [PATCH] testsuite: fix race conditions in ltdl dryrun
  • From: "Gary V. Vaughan" <gary@xxxxxxx>
• How To Configure for Android? (Redux for x86_64)
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• RE: Using 'make dist' with a 32 UID
  • From: "Finucane, Stephen" <stephen.finucane@xxxxxxxxx>
• Re: Mangled argument vector choking on spaces?
  • From: Kip Warner <kip@xxxxxxxxxxxxxx>
• Re: Mangled argument vector choking on spaces?
  • From: "David A. Wheeler" <dwheeler@xxxxxxxxxxxx>
• Re: Using 'make dist' with a 32 UID
  • From: Eric Blake <eblake@xxxxxxxxxx>
• RE: Using 'make dist' with a 32 UID
  • From: "Finucane, Stephen" <stephen.finucane@xxxxxxxxx>
• Re: Using 'make dist' with a 32 UID
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Using 'make dist' with a 32 UID
  • From: "Finucane, Stephen" <stephen.finucane@xxxxxxxxx>
• Re: Mangled argument vector choking on spaces?
  • From: Fotis Georgatos <fotis@xxxxxxxxxxxx>
• Re: Mangled argument vector choking on spaces?
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: Mangled argument vector choking on spaces?
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• Re: Mangled argument vector choking on spaces?
  • From: "David A. Wheeler" <dwheeler@xxxxxxxxxxxx>
• Re: Mangled argument vector choking on spaces?
  • From: "David A. Wheeler" <dwheeler@xxxxxxxxxxxx>
• Re: Mangled argument vector choking on spaces?
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• Re: Mangled argument vector choking on spaces?
  • From: Kip Warner <kip@xxxxxxxxxxxxxx>
• Re: Mangled argument vector choking on spaces?
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: Mangled argument vector choking on spaces?
  • From: Kip Warner <kip@xxxxxxxxxxxxxx>
• Re: Mangled argument vector choking on spaces?
  • From: "David A. Wheeler" <dwheeler@xxxxxxxxxxxx>
• Re: The results of your email commands
  • From: "David A. Wheeler" <dwheeler@xxxxxxxxxxxx>
• Re: Autoconf Digest, Vol 129, Issue 1
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• Re: Autoconf Digest, Vol 129, Issue 1
  • From: "David A. Wheeler" <dwheeler@xxxxxxxxxxxx>
• Re: Mangled argument vector choking on spaces?
  • From: "David A. Wheeler" <dwheeler@xxxxxxxxxxxx>
• Re: Mangled argument vector choking on spaces?
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: Mangled argument vector choking on spaces?
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• Re: Mangled argument vector choking on spaces?
  • From: "David A. Wheeler" <dwheeler@xxxxxxxxxxxx>
• Re: Mangled argument vector choking on spaces?
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: Mangled argument vector choking on spaces?
  • From: Fotis Georgatos <fotis@xxxxxxxxxxxx>
• Re: Autoconf Digest, Vol 128, Issue 6
  • From: "David A. Wheeler" <dwheeler@xxxxxxxxxxxx>
• Re: Mangled argument vector choking on spaces?
  • From: "David A. Wheeler" <dwheeler@xxxxxxxxxxxx>
• Re: Mangled argument vector choking on spaces?
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: Mangled argument vector choking on spaces?
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• Re: Mangled argument vector choking on spaces?
  • From: "David A. Wheeler" <dwheeler@xxxxxxxxxxxx>
• Re: Mangled argument vector choking on spaces?
  • From: Kip Warner <kip@xxxxxxxxxxxxxx>
• Re: Mangled argument vector choking on spaces?
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• Re: Mangled argument vector choking on spaces?
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• Re: Mangled argument vector choking on spaces?
  • From: Kip Warner <kip@xxxxxxxxxxxxxx>
• Mangled argument vector choking on spaces?
  • From: Kip Warner <kip@xxxxxxxxxxxxxx>
• Removing '../' from $abs_top_srcdir when distcheck is run
  • From: James Gallagher <jgallagher@xxxxxxxxxxx>
• Re: bug#16623: PACKAGE vs PACKAGE_TARNAME
  • From: Stefano Lattarini <stefano.lattarini@xxxxxxxxx>
• [PATCH] testsuite: fix race conditions in ltdl dryrun
  • From: Pavel Raiskup <praiskup@xxxxxxxxxx>
• What is the best/recommended technique for referencing development libraries?
  • From: Patrick Doyle <wpdster@xxxxxxxxx>
• Re: handling application data question
  • From: Peter Johansson <trojkan@xxxxxxxxx>
• handling application data question
  • From: Joey Runyans <joey.runyans@xxxxxxxxx>
• Re: Clarification request: AC_PREFIX_DEFAULT([.]) and AC_CONFIG_SUBDIRS collide.
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: Clarification request: AC_PREFIX_DEFAULT([.]) and AC_CONFIG_SUBDIRS collide.
  • From: Václav Zeman <vhaisman@xxxxxxxxx>
• Clarification request: AC_PREFIX_DEFAULT([.]) and AC_CONFIG_SUBDIRS collide.
  • From: Thomas Jahns <jahns@xxxxxxx>
• Re: Check whether AC_PROG_X has failed
  • From: Aggelos Kolaitis <neoaggelos@xxxxxxxxx>
• Re: Check whether AC_PROG_X has failed
  • From: Shahbaz Youssefi <shabbyx@xxxxxxxxx>
• Re: Check whether AC_PROG_X has failed
  • From: Nick Bowler <nbowler@xxxxxxxxxxxxxxxx>
• Check whether AC_PROG_X has failed
  • From: Shahbaz Youssefi <shabbyx@xxxxxxxxx>
• Re: Why is this "quadrigraph" necessary?
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: Why is this "quadrigraph" necessary?
  • From: Bruce Korb <bruce.korb@xxxxxxxxx>
• Re: Why is this "quadrigraph" necessary?
  • From: Bert Wesarg <bert.wesarg@xxxxxxxxxxxxxx>
• Why is this "quadrigraph" necessary?
  • From: Bruce Korb <bruce.korb@xxxxxxxxx>
• Re: new/custom installation directory
  • From: Harlan Stenn <stenn@xxxxxxx>
• Re: new/custom installation directory
  • From: Gavin Smith <gavinsmith0123@xxxxxxxxx>
• Re: new/custom installation directory
  • From: Harlan Stenn <stenn@xxxxxxx>
• Re: new/custom installation directory
  • From: Eric Blake <eblake@xxxxxxxxxx>
• new/custom installation directory
  • From: Harlan Stenn <stenn@xxxxxxx>
• Re: How to add directory to CFLAGS (or CXXFLAGS) search path?
  • From: Patrick Doyle <wpdster@xxxxxxxxx>
• Re: How to add directory to CFLAGS (or CXXFLAGS) search path?
  • From: Mike Frysinger <vapier@xxxxxxxxxx>
• How to add directory to CFLAGS (or CXXFLAGS) search path?
  • From: Patrick Doyle <wpdster@xxxxxxxxx>
• Re: Macro to select c++ as default compiler for c files
  • From: Zack Weinberg <zackw@xxxxxxxxx>
• Macro to select c++ as default compiler for c files
  • From: Lakshmi M <lakshmim@xxxxxxxxxxxxxxx>
• Re: Auto-Generating ChangeLog and AUTHORS for projects in a version tracking system?
  • From: "Arne Babenhauserheide (IMK)" <arne.babenhauserheide@xxxxxxx>
• Re: Auto-Generating ChangeLog and AUTHORS for projects in a version tracking system?
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: Auto-Generating ChangeLog and AUTHORS for projects in a version tracking system?
  • From: "Arne Babenhauserheide (IMK)" <arne.babenhauserheide@xxxxxxx>
• Re: Auto-Generating ChangeLog and AUTHORS for projects in a version tracking system?
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Auto-Generating ChangeLog and AUTHORS for projects in a version tracking system?
  • From: "Arne Babenhauserheide (IMK)" <arne.babenhauserheide@xxxxxxx>
• Re: Bash security issue
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: [PATCH] docs: mention that not all values can be exported
  • From: Nick Bowler <nbowler@xxxxxxxxxxxxxxxx>
• Re: Bash security issue
  • From: Nick Bowler <nbowler@xxxxxxxxxxxxxxxx>
• Re: Bash security issue
  • From: Henrique de Moraes Holschuh <hmh@xxxxxxxxxx>
• Re: Bash security issue
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: Bash security issue
  • From: Ralf Corsepius <rc040203@xxxxxxxxxx>
• Re: Bash security issue
  • From: Eric Blake <eblake@xxxxxxxxxx>
• sniffing for shellshock [was: Autoconf Digest, Vol 125, Issue 22]
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: Bash security issue
  • From: Ralf Corsepius <rc040203@xxxxxxxxxx>
• Re: Autoconf Digest, Vol 125, Issue 22
  • From: "David A. Wheeler" <dwheeler@xxxxxxxxxxxx>
• [PATCH] docs: mention that not all values can be exported
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: Bash security issue
  • From: Steve Simmons <scs@xxxxxxxxx>
• Re: Bash security issue
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: Bash security issue
  • From: Chet Ramey <chet.ramey@xxxxxxxx>
• Re: Bash security issue
  • From: Linda Walsh <bash@xxxxxxxxx>
• Re: Bash security issue
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: Bash security issue
  • From: Linda Walsh <bash@xxxxxxxxx>
• Re: Bash security issue
  • From: Zack Weinberg <zackw@xxxxxxxxx>
• Re: Bash security issue
  • From: Paul Smith <psmith@xxxxxxx>
• Re: Bash security issue
  • From: Nick Bowler <nbowler@xxxxxxxxxxxxxxxx>
• Re: Bash security issue
  • From: Nick Bowler <nbowler@xxxxxxxxxxxxxxxx>
• Re: Bash security issue
  • From: Nick Bowler <nbowler@xxxxxxxxxxxxxxxx>
• Re: Bash security issue
  • From: Steve Simmons <scs@xxxxxxxxx>
• Re: Bash security issue
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: Bash security issue
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: Bash security issue
  • From: Zack Weinberg <zackw@xxxxxxxxx>
• Re: Bash security issue
  • From: lolilolicon <lolilolicon@xxxxxxxxx>
• Re: Bash security issue
  • From: Andreas Schwab <schwab@xxxxxxxxxxxxxx>
• Re: Bash security issue
  • From: Linda Walsh <bash@xxxxxxxxx>
• Re: Bash security issue
  • From: Shawn H Corey <shawnhcorey@xxxxxxxxx>
• Re: Bash security issue
  • From: Linda Walsh <bash@xxxxxxxxx>
• Re: Bash security issue
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: Bash security issue
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: Bash security issue
  • From: Nick Bowler <nbowler@xxxxxxxxxxxxxxxx>
• Re: Bash security issue
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• Re: Bash security issue
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: Bash security issue
  • From: Shawn H Corey <shawnhcorey@xxxxxxxxx>
• Re: Bash security issue
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: Bash security issue
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Bash security issue
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• Re: Possible bug: AC_USE_SYSTEM_EXTENSIONS ignores "AS_IF" conditionals
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: Possible bug: AC_USE_SYSTEM_EXTENSIONS ignores "AS_IF" conditionals
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: Possible bug: AC_USE_SYSTEM_EXTENSIONS ignores "AS_IF" conditionals
  • From: "David A. Wheeler" <dwheeler@xxxxxxxxxxxx>
• Re: Possible bug: AC_USE_SYSTEM_EXTENSIONS ignores "AS_IF" conditionals
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: Possible bug: AC_USE_SYSTEM_EXTENSIONS ignores "AS_IF" conditionals
  • From: Gavin Smith <gavinsmith0123@xxxxxxxxx>
• Possible bug: AC_USE_SYSTEM_EXTENSIONS ignores "AS_IF" conditionals
  • From: "David A. Wheeler" <dwheeler@xxxxxxxxxxxx>
• Re: A Closer Look at GNU AutoTools
  • From: Gavin Smith <gavinsmith0123@xxxxxxxxx>
• Re: A Closer Look at GNU AutoTools
  • From: Shawn H Corey <shawnhcorey@xxxxxxxxx>
• RE: A Closer Look at GNU AutoTools
  • From: "John Calcote" <john.calcote@xxxxxxxxx>
• Re: A Closer Look at GNU AutoTools
  • From: Shawn H Corey <shawnhcorey@xxxxxxxxx>
• RE: A Closer Look at GNU AutoTools
  • From: "John Calcote" <john.calcote@xxxxxxxxx>
• RE: A Closer Look at GNU AutoTools
  • From: "David A. Wheeler" <dwheeler@xxxxxxxxxxxx>
• Re: A Closer Look at GNU AutoTools
  • From: Zé <jose.passes@xxxxxxx>
• Re: A Closer Look at GNU AutoTools
  • From: Ineiev <ineiev@xxxxxxxxx>
• Re: A Closer Look at GNU AutoTools
  • From: Gavin Smith <gavinsmith0123@xxxxxxxxx>
• Re: A Closer Look at GNU AutoTools
  • From: Shawn H Corey <shawnhcorey@xxxxxxxxx>
• RE: A Closer Look at GNU AutoTools
  • From: "John Calcote" <john.calcote@xxxxxxxxx>
• Re: A Closer Look at GNU AutoTools
  • From: Zé <jose.passes@xxxxxxx>
• Re: A Closer Look at GNU AutoTools
  • From: Zé <jose.passes@xxxxxxx>
• Re: A Closer Look at GNU AutoTools
  • From: Zé <jose.passes@xxxxxxx>
• Re: AC_PROG_CC wrongly setting $GCC=yes while clang is used
  • From: Thomas Jahns <jahns@xxxxxxx>
• Re: AC_PROG_CC wrongly setting $GCC=yes while clang is used
  • From: Bastien Chevreux <bach@xxxxxxxxxxxx>
• Re: AC_PROG_CC wrongly setting $GCC=yes while clang is used
  • From: Russ Allbery <eagle@xxxxxxxxx>
• Re: AC_PROG_CC wrongly setting $GCC=yes while clang is used
  • From: Peter Johansson <trojkan@xxxxxxxxx>
• Re: AC_PROG_CC wrongly setting $GCC=yes while clang is used
  • From: Russ Allbery <eagle@xxxxxxxxx>
• Re: AC_PROG_CC wrongly setting $GCC=yes while clang is used
  • From: "David A. Wheeler" <dwheeler@xxxxxxxxxxxx>
• Re: AC_PROG_CC wrongly setting $GCC=yes while clang is used
  • From: Bastien Chevreux <bach@xxxxxxxxxxxx>
• Re: AC_PROG_CC wrongly setting $GCC=yes while clang is used
  • From: Marko Lindqvist <cazfi74@xxxxxxxxx>
• Re: AC_PROG_CC wrongly setting $GCC=yes while clang is used
  • From: Bastien Chevreux <bach@xxxxxxxxxxxx>
• Re: AC_PROG_CC wrongly setting $GCC=yes while clang is used
  • From: Marko Lindqvist <cazfi74@xxxxxxxxx>
• Re: AC_PROG_CC wrongly setting $GCC=yes while clang is used
  • From: Bastien Chevreux <bach@xxxxxxxxxxxx>
• Re: AC_PROG_CC wrongly setting $GCC=yes while clang is used
  • From: Marko Lindqvist <cazfi74@xxxxxxxxx>
• Re: AC_PROG_CC wrongly setting $GCC=yes while clang is used
  • From: "David A. Wheeler" <dwheeler@xxxxxxxxxxxx>
• Re: AC_PROG_CC wrongly setting $GCC=yes while clang is used
  • From: Bastien Chevreux <bach@xxxxxxxxxxxx>
• Re: Initializing a Project with GNU Autotools
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: AC_PROG_CC wrongly setting $GCC=yes while clang is used
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: AC_PROG_CC wrongly setting $GCC=yes while clang is used
  • From: Bastien Chevreux <bach@xxxxxxxxxxxx>
• Re: Initializing a Project with GNU Autotools
  • From: Shawn H Corey <shawnhcorey@xxxxxxxxx>
• Re: Initializing a Project with GNU Autotools
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: AC_PROG_CC wrongly setting $GCC=yes while clang is used
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: AC_PROG_CC wrongly setting $GCC=yes while clang is used
  • From: Marko Lindqvist <cazfi74@xxxxxxxxx>
• Re: AC_PROG_CC wrongly setting $GCC=yes while clang is used
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: AC_PROG_CC wrongly setting $GCC=yes while clang is used
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: AC_PROG_CC wrongly setting $GCC=yes while clang is used
  • From: Thomas Jahns <jahns@xxxxxxx>
• Re: AC_PROG_CC wrongly setting $GCC=yes while clang is used
  • From: Paul Smith <psmith@xxxxxxx>
• AC_PROG_CC wrongly setting $GCC=yes while clang is used
  • From: Bastien Chevreux <bach@xxxxxxxxxxxx>
• Initializing a Project with GNU Autotools
  • From: Shawn H Corey <shawnhcorey@xxxxxxxxx>
• Re: A Closer Look at GNU AutoTools
  • From: Gavin Smith <gavinsmith0123@xxxxxxxxx>
• Re: A Closer Look at GNU AutoTools
  • From: Nick Bowler <nbowler@xxxxxxxxxxxxxxxx>
• Re: A Closer Look at GNU AutoTools
  • From: "Gary V. Vaughan" <gary@xxxxxxx>
• Re: A Closer Look at GNU AutoTools
  • From: Shawn H Corey <shawnhcorey@xxxxxxxxx>
• Tutorial
  • From: "David A. Wheeler" <dwheeler@xxxxxxxxxxxx>
• Re: A Closer Look at GNU AutoTools
  • From: Grégory Pakosz <gpakosz@xxxxxxxx>
• Re: A Closer Look at GNU AutoTools
  • From: Henrique de Moraes Holschuh <hmh@xxxxxxxxxx>
• Re: A Closer Look at GNU AutoTools
  • From: Johan Persson <johanp@xxxxxxxxx>
• Re: A Closer Look at GNU AutoTools
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: A Closer Look at GNU AutoTools
  • From: Shawn H Corey <shawnhcorey@xxxxxxxxx>
• Re: A Closer Look at GNU AutoTools
  • From: Shawn H Corey <shawnhcorey@xxxxxxxxx>
• Re: A Closer Look at GNU AutoTools
  • From: Shawn H Corey <shawnhcorey@xxxxxxxxx>
• Re: A Closer Look at GNU AutoTools
  • From: Hartmut Holzgraefe <hartmut.holzgraefe@xxxxxxxxx>
• RE: A Closer Look at GNU AutoTools
  • From: "John Calcote" <john.calcote@xxxxxxxxx>
• Re: A Closer Look at GNU AutoTools
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: A Closer Look at GNU AutoTools
  • From: Shawn H Corey <shawnhcorey@xxxxxxxxx>
• Re: A Closer Look at GNU AutoTools
  • From: Nick Bowler <nbowler@xxxxxxxxxxxxxxxx>
• Re: A Closer Look at GNU AutoTools
  • From: Shawn H Corey <shawnhcorey@xxxxxxxxx>
• Re: A Closer Look at GNU AutoTools
  • From: Nick Bowler <nbowler@xxxxxxxxxxxxxxxx>
• Re: A Closer Look at GNU AutoTools
  • From: John Spencer <maillist-autoconf@xxxxxxxxxxx>
• A Closer Look at GNU AutoTools
  • From: Shawn H Corey <shawnhcorey@xxxxxxxxx>
• Re: Strategy to specify major, minor, and patch versions
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• Re: Strategy to specify major, minor, and patch versions
  • From: Frank Lahm <franklahm@xxxxxxxxx>
• Re: Strategy to specify major, minor, and patch versions
  • From: Zack Weinberg <zackw@xxxxxxxxx>
• Re: Strategy to specify major, minor, and patch versions
  • From: Shawn H Corey <shawnhcorey@xxxxxxxxx>
• Re: Strategy to specify major, minor, and patch versions
  • From: Zé <jose.passes@xxxxxxx>
• Re: Strategy to specify major, minor, and patch versions
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• Re: Strategy to specify major, minor, and patch versions
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: Strategy to specify major, minor, and patch versions
  • From: Shawn H Corey <shawnhcorey@xxxxxxxxx>
• Re: Strategy to specify major, minor, and patch versions
  • From: Zé <jose.passes@xxxxxxx>
• Re: Strategy to specify major, minor, and patch versions
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: Strategy to specify major, minor, and patch versions
  • From: Zé <jose.passes@xxxxxxx>
• Re: Strategy to specify major, minor, and patch versions
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: Strategy to specify major, minor, and patch versions
  • From: Zé <jose.passes@xxxxxxx>
• Re: Strategy to specify major, minor, and patch versions
  • From: Peter Johansson <trojkan@xxxxxxxxx>
• Re: Strategy to specify major, minor, and patch versions
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Strategy to specify major, minor, and patch versions
  • From: Zé <jose.passes@xxxxxxx>
• Re: POSIX ruling on up-to-date vs. identical timestamps
  • From: Eli Zaretskii <eliz@xxxxxxx>
• Re: POSIX ruling on up-to-date vs. identical timestamps
  • From: Keith Marshall <keithmarshall@xxxxxxxxxxxxxxxxxxxxx>
• Re: POSIX ruling on up-to-date vs. identical timestamps
  • From: Eli Zaretskii <eliz@xxxxxxx>
• Re: POSIX ruling on up-to-date vs. identical timestamps
  • From: Eli Zaretskii <eliz@xxxxxxx>
• Re: POSIX ruling on up-to-date vs. identical timestamps
  • From: Keith Marshall <keithmarshall@xxxxxxxxxxxxxxxxxxxxx>
• Re: POSIX ruling on up-to-date vs. identical timestamps
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: POSIX ruling on up-to-date vs. identical timestamps
  • From: Paul Smith <psmith@xxxxxxx>
• Re: POSIX ruling on up-to-date vs. identical timestamps
  • From: Eli Zaretskii <eliz@xxxxxxx>
• Re: POSIX ruling on up-to-date vs. identical timestamps
  • From: Paul Smith <psmith@xxxxxxx>
• Change the linker of AC_PROG_CC
  • From: Barnabé Chauvin <barnabe.chauvin@xxxxxxxxx>
• Re: POSIX ruling on up-to-date vs. identical timestamps
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: POSIX ruling on up-to-date vs. identical timestamps
  • From: David Boyce <david.s.boyce@xxxxxxxxx>
• Re: POSIX ruling on up-to-date vs. identical timestamps
  • From: Paul Smith <psmith@xxxxxxx>
• Re: POSIX ruling on up-to-date vs. identical timestamps
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: POSIX ruling on up-to-date vs. identical timestamps
  • From: David Boyce <david.s.boyce@xxxxxxxxx>
• Re: POSIX ruling on up-to-date vs. identical timestamps
  • From: Ray Donnelly <mingw.android@xxxxxxxxx>
• Re: POSIX ruling on up-to-date vs. identical timestamps
  • From: David Boyce <david.s.boyce@xxxxxxxxx>
• Re: POSIX ruling on up-to-date vs. identical timestamps
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: POSIX ruling on up-to-date vs. identical timestamps
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• Re: POSIX ruling on up-to-date vs. identical timestamps
  • From: Ray Donnelly <mingw.android@xxxxxxxxx>
• Re: POSIX ruling on up-to-date vs. identical timestamps
  • From: Ray Donnelly <mingw.android@xxxxxxxxx>
• Re: POSIX ruling on up-to-date vs. identical timestamps
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• POSIX ruling on up-to-date vs. identical timestamps
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: config.guess problem with pgcc
  • From: Ben Elliston <bje@xxxxxxxxxx>
• Re: config.guess problem with pgcc
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: config.guess problem with pgcc
  • From: Thomas Jahns <jahns@xxxxxxx>
• Re: config.guess problem with pgcc
  • From: Eric Blake <eblake@xxxxxxxxxx>
• config.guess problem with pgcc
  • From: Thomas Jahns <jahns@xxxxxxx>
• Re: cross-compilation and proprietary pkg-config replacements (pcre-config, pcap-config, etc)
  • From: Mike Frysinger <vapier@xxxxxxxxxx>
• Re: cross-compilation and proprietary pkg-config replacements (pcre-config, pcap-config, etc)
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• Re: cross-compilation and proprietary pkg-config replacements (pcre-config, pcap-config, etc)
  • From: Mike Frysinger <vapier@xxxxxxxxxx>
• Re: cross-compilation and proprietary pkg-config replacements (pcre-config, pcap-config, etc)
  • From: Werner LEMBERG <wl@xxxxxxx>
• Re: cross-compilation and proprietary pkg-config replacements (pcre-config, pcap-config, etc)
  • From: Wookey <wookey@xxxxxxxxxxxx>
• cross-compilation and proprietary pkg-config replacements (pcre-config, pcap-config, etc)
  • From: John Spencer <maillist-autoconf@xxxxxxxxxxx>
• Re: ./configure: Choose data file
  • From: fr33domlover <fr33domlover@xxxxxxxxxx>
• Re: ./configure: Choose data file
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: ./configure: Choose data file
  • From: fr33domlover <fr33domlover@xxxxxxxxxx>
• Re: ./configure: Choose data file
  • From: Eric Blake <eblake@xxxxxxxxxx>
• ./configure: Choose data file
  • From: fr33domlover <fr33domlover@xxxxxxxxxx>
• Re: AC_PROG_INSTALL and AC_PROG_MKDIR_P fallbacks
  • From: Thomas Jahns <jahns@xxxxxxx>
• Re: How can I override CXXFLAGS?
  • From: Nick Bowler <nbowler@xxxxxxxxxxxxxxxx>
• Re: How can I override CXXFLAGS?
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• How can I override CXXFLAGS?
  • From: bholland <benedict.m.holland@xxxxxxxxx>
• Re: AC_PROG_INSTALL and AC_PROG_MKDIR_P fallbacks
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: AC_PROG_INSTALL and AC_PROG_MKDIR_P fallbacks
  • From: Thomas Jahns <jahns@xxxxxxx>
• Re: AC_PROG_INSTALL and AC_PROG_MKDIR_P fallbacks
  • From: Peter Johansson <trojkan@xxxxxxxxx>
• AC_PROG_INSTALL and AC_PROG_MKDIR_P fallbacks
  • From: Thomas Jahns <jahns@xxxxxxx>
• RE: [NOT SOLVED] Null characters in config.status
  • From: "Norman, Ben" <bnorman@xxxxxxxx>
• RE: [SOLVED] Null characters in config.status
  • From: "Norman, Ben" <bnorman@xxxxxxxx>
• Re: Null characters in config.status
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Null characters in config.status
  • From: "Norman, Ben" <bnorman@xxxxxxxx>
• Re: how to detect gcc version in configure.ac
  • From: Mike Frysinger <vapier@xxxxxxxxxx>
• Re: Autoconf and NCurses in C++
  • From: Mike Frysinger <vapier@xxxxxxxxxx>
• Autoconf and NCurses in C++
  • From: Adam Jiang <jiang.adam@xxxxxxxxx>
• Re: m4/autoconf quoting difference in include()
  • From: Roman Neuhauser <neuhauser@xxxxxxxxxx>
• Re: m4/autoconf quoting difference in include()
  • From: Roman Neuhauser <neuhauser@xxxxxxxxxx>
• Re: m4/autoconf quoting difference in include()
  • From: Nick Bowler <nbowler@xxxxxxxxxxxxxxxx>
• Re: m4/autoconf quoting difference in include()
  • From: Eric Blake <eblake@xxxxxxxxxx>
• m4/autoconf quoting difference in include()
  • From: Roman Neuhauser <neuhauser@xxxxxxxxxx>
• sadf
  • From: Roman Neuhauser <neuhauser@xxxxxxxxxx>
• Talk & demo of the autotools
  • From: ludovic.courtes@xxxxxxxx (Ludovic Courtès)
• Re: how to detect gcc version in configure.ac
  • From: "David A. Wheeler" <dwheeler@xxxxxxxxxxxx>
• Re: howto make "make check" verbose in 2.69
  • From: Rainer Gerhards <rgerhards@xxxxxxxxxxxxxx>
• Re: howto make "make check" verbose in 2.69
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: how to detect gcc version in configure.ac
  • From: Eric Blake <eblake@xxxxxxxxxx>
• how to detect gcc version in configure.ac
  • From: Minxuan Zhuang <z82507200@xxxxxxxxx>
• howto make "make check" verbose in 2.69
  • From: Rainer Gerhards <rgerhards@xxxxxxxxxxxxxx>
• Re: [GNU Autoconf 2.69] OSX autotools: `aclocal.m4' not being output by `autom4te'
  • From: "Gary V. Vaughan" <gary@xxxxxxx>
• Re: [GNU Autoconf 2.69] OSX autotools: `aclocal.m4' not being output by `autom4te'
  • From: Jeffrey Sheen <jeff@xxxxxxxxxxxxxxxxxxx>
• Re: [GNU Autoconf 2.69] OSX autotools: `aclocal.m4' not being output by `autom4te'
  • From: Werner LEMBERG <wl@xxxxxxx>