Gnu Autoconf

• Thread Index

• Re: bool and C23
  • From: Bruno Haible <bruno@xxxxxxxxx>
• Re: bool and C23
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: bool and C23
  • From: Bruno Haible <bruno@xxxxxxxxx>
• Re: bool and C23
  • From: Bruno Haible <bruno@xxxxxxxxx>
• Re: bool and C23
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: bool and C23
  • From: Bruno Haible <bruno@xxxxxxxxx>
• Re: bool and C23
  • From: Bruno Haible <bruno@xxxxxxxxx>
• Re: bool and C23
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: bool and C23
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: bool and C23
  • From: Bruno Haible <bruno@xxxxxxxxx>
• install autoconf as 'relocatable'
  • From: Mike Fulton <mikefultonpersonal@xxxxxxxxx>
• savannah page outdated
  • From: Detlef Riekenberg <wine.dev@xxxxxx>
• Re: autoheader an AC_DEFINE
  • From: aotto <aotto1968@xxxxxxxxxxx>
• Re: autoheader an AC_DEFINE
  • From: "Zack Weinberg" <zack@xxxxxxxxxxxx>
• autoheader an AC_DEFINE
  • From: aotto <aotto1968@xxxxxxxxxxx>
• Re: bool and C23
  • From: Bruno Haible <bruno@xxxxxxxxx>
• Re: bool and C23
  • From: Bruno Haible <bruno@xxxxxxxxx>
• Re: bool and C23
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: bool and C23
  • From: "Zack Weinberg" <zack@xxxxxxxxxxxx>
• Re: bool and C23
  • From: Tim Rice <tim@xxxxxxxxxxxxxxxx>
• Re: bool and C23
  • From: Bruno Haible <bruno@xxxxxxxxx>
• Re: bool and C23
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: bool and C23
  • From: "Zack Weinberg" <zack@xxxxxxxxxxxx>
• Re: bool and C23
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: bool and C23
  • From: "Zack Weinberg" <zack@xxxxxxxxxxxx>
• Re: bool and C23
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: bool and C23
  • From: Bruno Haible <bruno@xxxxxxxxx>
• bool and C23
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: gtk configure fails to detect XInput2.h
  • From: Sam James <sam@xxxxxxxxxx>
• Re: AC_PROG_LEX issue when compiling with -Werror
  • From: "Zack Weinberg" <zack@xxxxxxxxxxxx>
• Re: AC_PROG_LEX issue when compiling with -Werror
  • From: Tobias Brunner <tobias@xxxxxxxxxxxxxx>
• Re: AC_PROG_LEX issue when compiling with -Werror
  • From: Tobias Brunner <tobias@xxxxxxxxxxxxxx>
• Re: AC_PROG_LEX issue when compiling with -Werror
  • From: "Todd C. Miller" <Todd.Miller@xxxxxxx>
• Re: AC_PROG_LEX issue when compiling with -Werror
  • From: "Todd C. Miller" <Todd.Miller@xxxxxxx>
• Re: AC_PROG_LEX issue when compiling with -Werror
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• AC_PROG_LEX issue when compiling with -Werror
  • From: Tobias Brunner <tobias@xxxxxxxxxxxxxx>
• Re: How to set up autoconf on Ubuntu 20.04
  • From: dave@xxxxxxxxxxxxxxxxxx
• Re: How to set up autoconf on Ubuntu 20.04
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• How to set up autoconf on Ubuntu 20.04
  • From: dave@xxxxxxxxxxxxxxxxxx
• Re: Parallelization of shell scripts for 'configure' etc.
  • From: Alex Ameen <alex.ameen.tx@xxxxxxxxx>
• Re: Parallelization of shell scripts for 'configure' etc.
  • From: Simon Josefsson via Discussion list for the autoconf build system <autoconf@xxxxxxx>
• Re: docs linked https://www.gnu.org/savannah-checkouts/gnu/autoconf/ goes to 2.70
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: Parallelization of shell scripts for 'configure' etc.
  • From: Alexandre Oliva <oliva@xxxxxxx>
• Re: Parallelization of shell scripts for 'configure' etc.
  • From: Chet Ramey <chet.ramey@xxxxxxxx>
• Re: Parallelization of shell scripts for 'configure' etc.
  • From: Tim Rühsen <tim.ruehsen@xxxxxx>
• Re: How to prevent warning "The macro `AC_PROG_CC_C99' is obsolete"
  • From: "R. Diez" <rdiezmail-temp2@xxxxxxxx>
• Re: How to prevent warning "The macro `AC_PROG_CC_C99' is obsolete"
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• How to prevent warning "The macro `AC_PROG_CC_C99' is obsolete"
  • From: "R. Diez" <rdiezmail-temp2@xxxxxxxx>
• Re: Parallelization of shell scripts for 'configure' etc.
  • From: L A Walsh <coreutils@xxxxxxxxx>
• Re: Parallelization of shell scripts for 'configure' etc.
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• Re: Parallelization of shell scripts for 'configure' etc.
  • From: Alex Ameen <alex.ameen.tx@xxxxxxxxx>
• Re: Parallelization of shell scripts for 'configure' etc.
  • From: Demi Marie Obenour <demiobenour@xxxxxxxxx>
• Re: Parallelization of shell scripts for 'configure' etc.
  • From: madmurphy <madmurphy333@xxxxxxxxx>
• Re: Generating configuration files conditionnally?
  • From: Sébastien Hinderer <Sebastien.Hinderer@xxxxxxxx>
• Re: Generating configuration files conditionnally?
  • From: Nick Bowler <nbowler@xxxxxxxxxx>
• Generating configuration files conditionnally?
  • From: Sébastien Hinderer <Sebastien.Hinderer@xxxxxxxx>
• Re: Parallelization of shell scripts for 'configure' etc.
  • From: "Zack Weinberg" <zack@xxxxxxxxxxxx>
• Re: Parallelization of shell scripts for 'configure' etc.
  • From: Warren Young <warren@xxxxxxxxxxx>
• Re: Parallelization of shell scripts for 'configure' etc.
  • From: Bruno Haible <bruno@xxxxxxxxx>
• Re: Parallelization of shell scripts for 'configure' etc.
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Re: Parallelization of shell scripts for 'configure' etc.
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: Parallelization of shell scripts for 'configure' etc.
  • From: Ángel <angel@xxxxxxxxxx>
• Re: Parallelization of shell scripts for 'configure' etc.
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: Parallelization of shell scripts for 'configure' etc.
  • From: Richard Purdie <richard.purdie@xxxxxxxxxxxxxxxxxxx>
• Re: Parallelization of shell scripts for 'configure' etc.
  • From: Nick Bowler <nbowler@xxxxxxxxxx>
• Re: Parallelization of shell scripts for 'configure' etc.
  • From: Nick Bowler <nbowler@xxxxxxxxxx>
• Re: Parallelization of shell scripts for 'configure' etc.
  • From: Steffen Nurpmeso <steffen@xxxxxxxxxx>
• Re: Parallelization of shell scripts for 'configure' etc.
  • From: Chet Ramey <chet.ramey@xxxxxxxx>
• Re: Parallelization of shell scripts for 'configure' etc.
  • From: Michael Orlitzky <michael@xxxxxxxxxxxx>
• Re: Parallelization of shell scripts for 'configure' etc.
  • From: madmurphy <madmurphy333@xxxxxxxxx>
• Re: Parallelization of shell scripts for 'configure' etc.
  • From: Alex Ameen <alex.ameen.tx@xxxxxxxxx>
• Re: Parallelization of shell scripts for 'configure' etc.
  • From: "Dale R. Worley" <worley@xxxxxxxxxxxx>
• Re: Parallelization of shell scripts for 'configure' etc.
  • From: Alex Ameen <alex.ameen.tx@xxxxxxxxx>
• Re: Parallelization of shell scripts for 'configure' etc.
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Parallelization of shell scripts for 'configure' etc.
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: make check to test a few tests, not all
  • From: Nick Bowler <nbowler@xxxxxxxxxx>
• make check to test a few tests, not all
  • From: Mike Fulton <mikefultonpersonal@xxxxxxxxx>
• Re: Extensions to M4sh
  • From: Alex Ameen <alex.ameen.tx@xxxxxxxxx>
• Re: Extensions to M4sh
  • From: madmurphy <madmurphy333@xxxxxxxxx>
• Re: Extensions to M4sh
  • From: Michael Orlitzky <michael@xxxxxxxxxxxx>
• Re: Extensions to M4sh
  • From: Per Bothner <per@xxxxxxxxxxx>
• Re: Extensions to M4sh
  • From: Nate Bargmann <n0nb@xxxxxxx>
• Re: Extensions to M4sh
  • From: "Carlos O'Donell" <carlos@xxxxxxxxxx>
• Re: Extensions to M4sh
  • From: "Carlos O'Donell" <carlos@xxxxxxxxxx>
• Re: Extensions to M4sh
  • From: Michael Orlitzky <michael@xxxxxxxxxxxx>
• Re: Extensions to M4sh
  • From: Demi Marie Obenour <demiobenour@xxxxxxxxx>
• Re: Extensions to M4sh
  • From: "Zack Weinberg" <zack@xxxxxxxxxxxx>
• Re: Detecting gated functions w/ AC_CHECK_FUNCS()
  • From: Philip Prindeville <philipp_subx@xxxxxxxxxxxxxxxxxxxxx>
• Re: Detecting gated functions w/ AC_CHECK_FUNCS()
  • From: Nick Bowler <nbowler@xxxxxxxxxx>
• Re: Detecting gated functions w/ AC_CHECK_FUNCS()
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• Detecting gated functions w/ AC_CHECK_FUNCS()
  • From: Philip Prindeville <philipp_subx@xxxxxxxxxxxxxxxxxxxxx>
• Re: Extensions to M4sh
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Extensions to M4sh
  • From: Alex Ameen <alex.ameen.tx@xxxxxxxxx>
• Re: Accelerate the 'configure' script
  • From: Markus Elfring <Markus.Elfring@xxxxxx>
• Re: Accelerate the 'configure' script
  • From: Demi Marie Obenour <demiobenour@xxxxxxxxx>
• Re: Accelerate the 'configure' script
  • From: Alex Ameen <alex.ameen.tx@xxxxxxxxx>
• Accelerate the 'configure' script
  • From: "R. Diez" <rdiezmail-temp2@xxxxxxxx>
• Re: Wrong order of preprocessor and compiler flags
  • From: Evgeny Grin <k2k@xxxxxxxxx>
• Re: Wrong order of preprocessor and compiler flags
  • From: Peter Johansson <trojkan@xxxxxxxxx>
• Re: libtool-2.4.7 released [stable]
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• Re: Wrong order of preprocessor and compiler flags
  • From: Evgeny Grin <k2k@xxxxxxxx>
• Re: Wrong order of preprocessor and compiler flags
  • From: Alex Ameen <alex.ameen.tx@xxxxxxxxx>
• Re: Wrong order of preprocessor and compiler flags
  • From: Evgeny Grin <k2k@xxxxxxxx>
• Re: Wrong order of preprocessor and compiler flags
  • From: Evgeny Grin <k2k@xxxxxxxx>
• Re: Wrong order of preprocessor and compiler flags
  • From: Evgeny Grin <k2k@xxxxxxxx>
• Re: Wrong order of preprocessor and compiler flags
  • From: "Carlos O'Donell" <carlos@xxxxxxxxxx>
• Re: Wrong order of preprocessor and compiler flags
  • From: "David A. Wheeler" <dr.david.a.wheeler@xxxxxxxxx>
• Re: Wrong order of preprocessor and compiler flags
  • From: Sam James <sam@xxxxxxxxxx>
• Re: Wrong order of preprocessor and compiler flags
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• Wrong order of preprocessor and compiler flags
  • From: Evgeny Grin <k2k@xxxxxxxx>
• Re: Checking whether program foo supports option --bar
  • From: Sébastien Hinderer <Sebastien.Hinderer@xxxxxxxx>
• Re: Checking whether program foo supports option --bar
  • From: Peter Johansson <trojkan@xxxxxxxxx>
• Re: Checking whether program foo supports option --bar
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Checking whether program foo supports option --bar
  • From: Sébastien Hinderer <Sebastien.Hinderer@xxxxxxxx>
• Re: portability of xargs
  • From: Jacob Bachmeyer <jcb62281@xxxxxxxxx>
• Re: portability of xargs
  • From: Dan Kegel <dank@xxxxxxxxx>
• Re: portability of xargs
  • From: Mike Frysinger <vapier@xxxxxxxxxx>
• Re: portability of xargs
  • From: Mike Frysinger <vapier@xxxxxxxxxx>
• Re: portability of xargs
  • From: NightStrike <nightstrike@xxxxxxxxx>
• Re: portability of xargs
  • From: Paul Smith <psmith@xxxxxxx>
• Re: portability of xargs
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• Re: portability of xargs
  • From: Paul Smith <psmith@xxxxxxx>
• Re: portability of xargs
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• Re: portability of xargs
  • From: Nick Bowler <nbowler@xxxxxxxxxx>
• Re: portability of xargs
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• Re: portability of xargs
  • From: Daniel Herring <dherring@xxxxxxxxxxxx>
• Re: portability of xargs
  • From: Roman Neuhauser <neuhauser@xxxxxxxxxx>
• Re: portability of xargs
  • From: Jan Engelhardt <jengelh@xxxxxxx>
• Re: portability of xargs
  • From: Dan Kegel <dank@xxxxxxxxx>
• Re: portability of xargs
  • From: Daniel Herring <dherring@xxxxxxxxxxxx>
• Re: portability of xargs
  • From: Alex Ameen <alex.ameen.tx@xxxxxxxxx>
• Re: portability of xargs
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: portability of xargs
  • From: Mike Frysinger <vapier@xxxxxxxxxx>
• Re: portability of xargs
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• portability of xargs
  • From: Mike Frysinger <vapier@xxxxxxxxxx>
• Re: bug#19539: [1.15] AC_CONFIG_AUX_DIR should be called early
  • From: "Zack Weinberg" <zack@xxxxxxxxxxxx>
• Re: support for build-time programs
  • From: Mike Frysinger <vapier@xxxxxxxxxx>
• Re: support for build-time programs
  • From: Alex Ameen <alex.ameen.tx@xxxxxxxxx>
• Re: support for build-time programs
  • From: "Zack Weinberg" <zack@xxxxxxxxxxxx>
• support for build-time programs
  • From: Mike Frysinger <vapier@xxxxxxxxxx>
• docs linked https://www.gnu.org/savannah-checkouts/gnu/autoconf/ goes to 2.70
  • From: Peter Johansson <trojkan@xxxxxxxxx>
• Re: abs_top_srcdir broken?
  • From: Sébastien Hinderer <Sebastien.Hinderer@xxxxxxxx>
• Re: New libtool maintainer: request for feedback
  • From: Alex Ameen <alex.ameen.tx@xxxxxxxxx>
• Re: New libtool maintainer: request for feedback
  • From: Marko Lindqvist <cazfi74@xxxxxxxxx>
• Re: New libtool maintainer: request for feedback
  • From: Alex Ameen <alex.ameen.tx@xxxxxxxxx>
• Re: New libtool maintainer: request for feedback
  • From: Werner LEMBERG <wl@xxxxxxx>
• Re: New libtool maintainer: request for feedback
  • From: Alex Ameen <alex.ameen.tx@xxxxxxxxx>
• Re: New libtool maintainer: request for feedback
  • From: "Zack Weinberg" <zack@xxxxxxxxxxxx>
• New libtool maintainer: request for feedback
  • From: Alex Ameen <alex.ameen.tx@xxxxxxxxx>
• Re: abs_top_srcdir broken?
  • From: Sébastien Hinderer <Sebastien.Hinderer@xxxxxxxx>
• Re: abs_top_srcdir broken?
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• Re: abs_top_srcdir broken?
  • From: Nick Bowler <nbowler@xxxxxxxxxx>
• abs_top_srcdir broken?
  • From: Sébastien Hinderer <Sebastien.Hinderer@xxxxxxxx>
• Re: Checking failing dlopen when building 32bit software
  • From: alexandre schenberg <ale.schenberg@xxxxxxxxxx>
• Re: Making a path absolute portably
  • From: Sébastien Hinderer <Sebastien.Hinderer@xxxxxxxx>
• Re: Checking failing dlopen when building 32bit software
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• Checking failing dlopen when building 32bit software
  • From: alexandre schenberg <ale.schenberg@xxxxxxxxxx>
• Re: automake-1.16.5 released [stable]
  • From: Kip Warner <kip@xxxxxxxxxxxxxx>
• Re: bug#50469: [bison-3.8] bug or side effect to flex & automake
  • From: "Zack Weinberg" <zack@xxxxxxxxxxxx>
• Re: m4 macro expansion problem
  • From: Sébastien Hinderer <Sebastien.Hinderer@xxxxxxxx>
• Re: m4 macro expansion problem
  • From: Sébastien Hinderer <Sebastien.Hinderer@xxxxxxxx>
• Re: Description not expanded in a call to AC_DEFINE
  • From: Sébastien Hinderer <Sebastien.Hinderer@xxxxxxxx>
• Re: Description not expanded in a call to AC_DEFINE
  • From: Nick Bowler <nbowler@xxxxxxxxxx>
• Re: Description not expanded in a call to AC_DEFINE
  • From: Sébastien Hinderer <Sebastien.Hinderer@xxxxxxxx>
• Re: Description not expanded in a call to AC_DEFINE
  • From: Nick Bowler <nbowler@xxxxxxxxxx>
• Description not expanded in a call to AC_DEFINE
  • From: Sébastien Hinderer <Sebastien.Hinderer@xxxxxxxx>
• Re: m4 macro expansion problem
  • From: Peter Johansson <trojkan@xxxxxxxxx>
• Re: m4 macro expansion problem
  • From: "Zack Weinberg" <zack@xxxxxxxxxxxx>
• Re: m4 macro expansion problem
  • From: Sébastien Hinderer <Sebastien.Hinderer@xxxxxxxx>
• Re: m4 macro expansion problem
  • From: "Zack Weinberg" <zack@xxxxxxxxxxxx>
• Re: m4 macro expansion problem
  • From: Sébastien Hinderer <Sebastien.Hinderer@xxxxxxxx>
• Re: m4 macro expansion problem
  • From: Sébastien Hinderer <Sebastien.Hinderer@xxxxxxxx>
• Re: m4 macro expansion problem
  • From: Sébastien Hinderer <Sebastien.Hinderer@xxxxxxxx>
• Re: m4 macro expansion problem
  • From: Peter Johansson <trojkan@xxxxxxxxx>
• Re: m4 macro expansion problem
  • From: Nick Bowler <nbowler@xxxxxxxxxx>
• Re: m4 macro expansion problem
  • From: Nick Bowler <nbowler@xxxxxxxxxx>
• m4 macro expansion problem
  • From: Sébastien Hinderer <Sebastien.Hinderer@xxxxxxxx>
• Possible regression in AC_FC_WRAPPERS
  • From: Sam James <sam@xxxxxxxxxx>
• Possible regression in AC_FC_WRAPPERS
  • From: Michael Orlitzky <michael@xxxxxxxxxxxx>
• Re: Running autoconf and autoreconf without autotools in the path
  • From: Nick Bowler <nbowler@xxxxxxxxxx>
• Re: Running autoconf and autoreconf without autotools in the path
  • From: Christopher O Cowan <Christopher.O.Cowan@xxxxxxx>
• Running autoconf and autoreconf without autotools in the path
  • From: Christopher O Cowan <Christopher.O.Cowan@xxxxxxx>
• Re: AC_CHECK_FUNC vs. function renaming? (curl on tru64/osf1, threads)
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: AC_CHECK_FUNC vs. function renaming? (curl on tru64/osf1, threads)
  • From: Jay K <jayk123@xxxxxxxxxxx>
• Re: AC_CHECK_FUNC vs. function renaming? (curl on tru64/osf1, threads)
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: AC_CHECK_FUNC vs. function renaming? (curl on tru64/osf1, threads)
  • From: Jay K <jayk123@xxxxxxxxxxx>
• Re: Autoconf online tutorial
  • From: Anthony Scemama <scemama@xxxxxxxxxxxxxxxxxx>
• Re: Autoconf online tutorial
  • From: "David A. Wheeler" <dwheeler@xxxxxxxxxxxx>
• Re: AC_CHECK_FUNC vs. function renaming? (curl on tru64/osf1, threads)
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Autoconf online tutorial
  • From: Anthony Scemama <scemama@xxxxxxxxxxxxxxxxxx>
• AC_CHECK_FUNC vs. function renaming? (curl on tru64/osf1, threads)
  • From: Jay K <jayk123@xxxxxxxxxxx>
• Re: Latest M4 fails M4 checks
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: Latest M4 fails M4 checks
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Re: about variable ac_link and gcc
  • From: Thomas Jahns <jahns@xxxxxxx>
• Re: about variable ac_link and gcc
  • From: Changqing Li <changqing.li@xxxxxxxxxxxxx>
• about variable ac_link and gcc
  • From: Changqing Li <changqing.li@xxxxxxxxxxxxx>
• about variable ac_link and gcc
  • From: Changqing Li <changqing.li@xxxxxxxxxxxxx>
• Re: Force 32 bit build
  • From: Ismael Luceno <ismael@xxxxxxxxxxx>
• Re: automake problem with multiple "-rpath"
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• Re: automake problem with multiple "-rpath"
  • From: aotto <aotto1968@xxxxxxxxxxx>
• Re: automake problem with multiple "-rpath"
  • From: Thomas Jahns <jahns@xxxxxxx>
• Re: automake problem with multiple "-rpath"
  • From: aotto <aotto1968@xxxxxxxxxxx>
• Re: automake problem with multiple "-rpath"
  • From: Thomas Jahns <jahns@xxxxxxx>
• Re: automake problem with multiple "-rpath"
  • From: aotto <aotto1968@xxxxxxxxxxx>
• automake problem with multiple "-rpath"
  • From: aotto <aotto1968@xxxxxxxxxxx>
• Re: autoconf-2.71 released [stable]
  • From: Eric Blake <eblake@xxxxxxxxxx>
• RE: Force 32 bit build
  • From: "Jannick" <thirdedition@xxxxxxx>
• Re: Force 32 bit build
  • From: aotto <aotto1968@xxxxxxxxxxx>
• Re: How to autoconf figure out what library need to be linked to?
  • From: Michael Orlitzky <michael@xxxxxxxxxxxx>
• Re: Force 32 bit build
  • From: Thomas Jahns <jahns@xxxxxxx>
• Re: Force 32 bit build
  • From: Nick Bowler <nbowler@xxxxxxxxxx>
• Force 32 bit build
  • From: aotto <aotto1968@xxxxxxxxxxx>
• Re: Latest M4 fails M4 checks
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: Latest M4 fails M4 checks
  • From: Nick Bowler <nbowler@xxxxxxxxxx>
• Re: Latest M4 fails M4 checks
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Latest M4 fails M4 checks
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• How to autoconf figure out what library need to be linked to?
  • From: Peng Yu <pengyu.ut@xxxxxxxxx>
• Re: [Knut Petersen] [PATCH] fix broken building of guile branch "branch_release-1-8"
  • From: Thien-Thi Nguyen <ttn@xxxxxxxxxxx>
• Re: How to "bake in" configure args
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• Re: How to "bake in" configure args
  • From: "Dan Mahoney (Gushi)" <danm@xxxxxxxxxxxxxxx>
• Re: How to "bake in" configure args
  • From: Richard Purdie <richard.purdie@xxxxxxxxxxxxxxxxxxx>
• Re: How to "bake in" configure args
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• Re: libtool wrapper
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• Re: How to "bake in" configure args
  • From: Dan Mahoney <danm@xxxxxxxxxxxxxxx>
• libtool wrapper
  • From: "Dan Mahoney (Gushi)" <danm@xxxxxxxxxxxxxxx>
• Re: How to "bake in" configure args
  • From: Gavin Smith <gavinsmith0123@xxxxxxxxx>
• How to "bake in" configure args
  • From: "Dan Mahoney (Gushi)" <danm@xxxxxxxxxxxxxxx>
• [Knut Petersen] [PATCH] fix broken building of guile branch "branch_release-1-8"
  • From: Thien-Thi Nguyen <ttn@xxxxxxxxxxx>
• Re: How to check for a #DEFINE?
  • From: Václav Haisman <vhaisman@xxxxxxxxx>
• How to check for a #DEFINE?
  • From: Dan Mahoney <danm@xxxxxxxxxxxxxxx>
• Re: How to properly check for -lresolv and resolv.h
  • From: Dan Mahoney <danm@xxxxxxxxxxxxxxx>
• Re: How to properly check for -lresolv and resolv.h
  • From: Zack Weinberg <zackw@xxxxxxxxx>
• How to properly check for -lresolv and resolv.h
  • From: "Dan Mahoney (Gushi)" <danm@xxxxxxxxxxxxxxx>
• Issue with AC 2.69 (FreeBSD) and recent changes to make us more compatible with 2.70
  • From: "Dan Mahoney (Gushi)" <danm@xxxxxxxxxxxxxxx>
• Re: config.sub/config.guess using nonportable $(...) substitutions
  • From: Karl Berry <karl@xxxxxxxxxxxxxxx>
• Re: config.sub/config.guess using nonportable $(...) substitutions
  • From: "David A. Wheeler" <dwheeler@xxxxxxxxxxxx>
• Re: config.sub/config.guess using nonportable $(...) substitutions
  • From: Russ Allbery <eagle@xxxxxxxxx>
• Re: config.sub/config.guess using nonportable $(...) substitutions
  • From: Warren Young <warren@xxxxxxxxxxx>
• Re: config.sub/config.guess using nonportable $(...) substitutions
  • From: Zack Weinberg <zackw@xxxxxxxxx>
• Re: config.sub/config.guess using nonportable $(...) substitutions
  • From: Nick Bowler <nbowler@xxxxxxxxxx>
• Re: config.sub/config.guess using nonportable $(...) substitutions
  • From: Tim Rice <tim@xxxxxxxxxxxxxxxx>
• Re: config.sub/config.guess using nonportable $(...) substitutions
  • From: Michael Orlitzky <michael@xxxxxxxxxxxx>
• Re: config.sub/config.guess using nonportable $(...) substitutions
  • From: "Todd C. Miller" <Todd.Miller@xxxxxxx>
• Re: config.sub/config.guess using nonportable $(...) substitutions
  • From: Warren Young <warren@xxxxxxxxxxx>
• Re: config.sub/config.guess using nonportable $(...) substitutions
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: config.sub/config.guess using nonportable $(...) substitutions
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: config.sub/config.guess using nonportable $(...) substitutions
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: config.sub/config.guess using nonportable $(...) substitutions
  • From: Karl Berry <karl@xxxxxxxxxxxxxxx>
• Re: config.sub/config.guess using nonportable $(...) substitutions
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• Re: config.sub/config.guess using nonportable $(...) substitutions
  • From: Nick Bowler <nbowler@xxxxxxxxxx>
• Re: config.sub/config.guess using nonportable $(...) substitutions
  • From: Tim Rice <tim@xxxxxxxxxxxxxxxx>
• Re: config.sub/config.guess using nonportable $(...) substitutions
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: config.sub/config.guess using nonportable $(...) substitutions
  • From: Karl Berry <karl@xxxxxxxxxxxxxxx>
• Re: config.sub/config.guess using nonportable $(...) substitutions
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• Re: config.sub/config.guess using nonportable $(...) substitutions
  • From: "Dmitry V. Levin" <ldv@xxxxxxxxxxxx>
• config.sub/config.guess using nonportable $(...) substitutions
  • From: Nick Bowler <nbowler@xxxxxxxxxx>
• Re: sys/time.h and time.h
  • From: Thien-Thi Nguyen <ttn@xxxxxxxxxxx>
• Re: sys/time.h and time.h
  • From: Zack Weinberg <zackw@xxxxxxxxx>
• sys/time.h and time.h
  • From: Thien-Thi Nguyen <ttn@xxxxxxxxxxx>
• Version 2.72a fails with libarchive git version
  • From: Werner LEMBERG <wl@xxxxxxx>
• Re: RFC: Bump minimum Perl to 5.18.0 for next major release of both Autoconf and Automake
  • From: Nick Bowler <nbowler@xxxxxxxxxx>
• Re: RFC: Bump minimum Perl to 5.18.0 for next major release of both Autoconf and Automake
  • From: Karl Berry <karl@xxxxxxxxxxxxxxx>
• Re: RFC: Bump minimum Perl to 5.18.0 for next major release of both Autoconf and Automake
  • From: alexandre schenberg <ale.schenberg@xxxxxxxxxx>
• Re: RFC: Bump minimum Perl to 5.18.0 for next major release of both Autoconf and Automake
  • From: Nick Bowler <nbowler@xxxxxxxxxx>
• Re: RFC: Bump minimum Perl to 5.18.0 for next major release of both Autoconf and Automake
  • From: Zack Weinberg <zackw@xxxxxxxxx>
• Re: RFC: Bump minimum Perl to 5.18.0 for next major release of both Autoconf and Automake
  • From: Zack Weinberg <zackw@xxxxxxxxx>
• Re: AC_PROG_CC: how to distinguish clnag from gcc?
  • From: Sébastien Hinderer <Sebastien.Hinderer@xxxxxxxx>
• Re: AC_PROG_CC: how to distinguish clnag from gcc?
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: AC_PROG_CC: how to distinguish clnag from gcc?
  • From: Russ Allbery <eagle@xxxxxxxxx>
• Re: AC_PROG_CC: how to distinguish clnag from gcc?
  • From: Sébastien Hinderer <Sebastien.Hinderer@xxxxxxxx>
• Re: AC_PROG_CC: how to distinguish clang from gcc?
  • From: Sébastien Hinderer <Sebastien.Hinderer@xxxxxxxx>
• Re: AC_PROG_CC: how to distinguish clang from gcc?
  • From: Russ Allbery <eagle@xxxxxxxxx>
• Re: AC_PROG_CC: how to distinguish clnag from gcc?
  • From: Russ Allbery <eagle@xxxxxxxxx>
• Re: AC_PROG_CC: how to distinguish clang from gcc?
  • From: "David A. Wheeler" <dwheeler@xxxxxxxxxxxx>
• Re: AC_PROG_CC: how to distinguish clnag from gcc?
  • From: "David A. Wheeler" <dwheeler@xxxxxxxxxxxx>
• Re: AC_PROG_CC: how to distinguish clnag from gcc?
  • From: Sébastien Hinderer <Sebastien.Hinderer@xxxxxxxx>
• Re: AC_PROG_CC: how to distinguish clnag from gcc?
  • From: "Todd C. Miller" <Todd.Miller@xxxxxxx>
• AC_PROG_CC: how to distinguish clnag from gcc?
  • From: Sébastien Hinderer <Sebastien.Hinderer@xxxxxxxx>
• Re: Weird behaviour about system types
  • From: Sébastien Hinderer <Sebastien.Hinderer@xxxxxxxx>
• Re: Weird behaviour about system types
  • From: Nick Bowler <nbowler@xxxxxxxxxx>
• Re: Weird behaviour about system types
  • From: Sébastien Hinderer <Sebastien.Hinderer@xxxxxxxx>
• Re: Weird behaviour about system types
  • From: Nick Bowler <nbowler@xxxxxxxxxx>
• Re: Weird behaviour about system types
  • From: Zack Weinberg <zackw@xxxxxxxxx>
• Re: Weird behaviour about system types
  • From: Sébastien Hinderer <Sebastien.Hinderer@xxxxxxxx>
• Re: Weird behaviour about system types
  • From: Zack Weinberg <zackw@xxxxxxxxx>
• Weird behaviour about system types
  • From: Sébastien Hinderer <Sebastien.Hinderer@xxxxxxxx>
• Re: Automake's file locking
  • From: Nick Bowler <nbowler@xxxxxxxxxx>
• Re: Automake's file locking
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• RE: M4 stock macros
  • From: DUDZIAK Krzysztof <krzysztof.dudziak@xxxxxxxxxxxxxxx>
• Re: couple notes about post-2.71 branch management
  • From: Zack Weinberg <zackw@xxxxxxxxx>
• Re: Automake's file locking
  • From: Zack Weinberg <zackw@xxxxxxxxx>
• Re: couple notes about post-2.71 branch management
  • From: Nick Bowler <nbowler@xxxxxxxxxx>
• Re: Procedure for adding new target
  • From: connor horman <chorman64@xxxxxxxxx>
• Re: Procedure for adding new target
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Procedure for adding new target
  • From: connor horman <chorman64@xxxxxxxxx>
• Re: Future plans for Autotools
  • From: Gavin Smith <gavinsmith0123@xxxxxxxxx>
• Re: Future plans for Autotools
  • From: Gavin Smith <gavinsmith0123@xxxxxxxxx>
• Re: version string comparison
  • From: Thien-Thi Nguyen <ttn@xxxxxxxxxxx>
• Re: version string comparison
  • From: Nick Bowler <nbowler@xxxxxxxxxx>
• version string comparison
  • From: Thien-Thi Nguyen <ttn@xxxxxxxxxxx>
• Re: RFC: Bump minimum Perl to 5.18.0 for next major release of both Autoconf and Automake
  • From: Karl Berry <karl@xxxxxxxxxxxxxxx>
• Re: RFC: Bump minimum Perl to 5.18.0 for next major release of both Autoconf and Automake
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• RFC: Bump minimum Perl to 5.18.0 for next major release of both Autoconf and Automake
  • From: Zack Weinberg <zackw@xxxxxxxxx>
• couple notes about post-2.71 branch management
  • From: Zack Weinberg <zackw@xxxxxxxxx>
• Re: Future plans for Autotools
  • From: Richard Purdie <richard.purdie@xxxxxxxxxxxxxxxxxxx>
• NFS file locking (was: Re: Automake's file locking (was Re: Autoconf/Automake is not using version from AC_INIT))
  • From: pluto--- via Discussion list for the autoconf build system <autoconf@xxxxxxx>
• Re: Autoconf version number after 2.70
  • From: John Calcote <john.calcote@xxxxxxxxx>
• Re: Automake's file locking
  • From: Bruno Haible <bruno@xxxxxxxxx>
• Re: Autoconf version number after 2.70
  • From: Zack Weinberg <zackw@xxxxxxxxx>
• autoconf-2.71 released [stable]
  • From: zackw@xxxxxxxxx (Zack Weinberg)
• Re: Parallel configure
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: Automake's file locking (was Re: Autoconf/Automake is not using version from AC_INIT)
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: Automake's file locking (was Re: Autoconf/Automake is not using version from AC_INIT)
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• Re: Automake's file locking (was Re: Autoconf/Automake is not using version from AC_INIT)
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• Re: Automake's file locking (was Re: Autoconf/Automake is not using version from AC_INIT)
  • From: Nick Bowler <nbowler@xxxxxxxxxx>
• Re: Parallel configure
  • From: Gavin Smith <gavinsmith0123@xxxxxxxxx>
• Re: Automake's file locking (was Re: Autoconf/Automake is not using version from AC_INIT)
  • From: Zack Weinberg <zackw@xxxxxxxxx>
• Re: M4 stock macros
  • From: Zack Weinberg <zackw@xxxxxxxxx>
• Re: Automake's file locking (was Re: Autoconf/Automake is not using version from AC_INIT)
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• Re: Automake's file locking (was Re: Autoconf/Automake is not using version from AC_INIT)
  • From: Zack Weinberg <zackw@xxxxxxxxx>
• M4 stock macros
  • From: DUDZIAK Krzysztof <krzysztof.dudziak@xxxxxxxxxxxxxxx>
• Re: Parallel configure
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• Re: Parallel configure
  • From: Gavin Smith <gavinsmith0123@xxxxxxxxx>
• Parallel configure
  • From: Zack Weinberg <zackw@xxxxxxxxx>
• Re: Future plans for Autotools
  • From: Karl Berry <karl@xxxxxxxxxxxxxxx>
• Re: Future plans for Autotools
  • From: Joseph Myers <joseph@xxxxxxxxxxxxxxxx>
• Re: Future plans for Autotools
  • From: Richard Purdie <richard.purdie@xxxxxxxxxxxxxxxxxxx>
• Re: Future plans for Autotools
  • From: Joseph Myers <joseph@xxxxxxxxxxxxxxxx>
• Re: Future plans for Autotools
  • From: Richard Purdie <richard.purdie@xxxxxxxxxxxxxxxxxxx>
• Re: Future plans for Autotools
  • From: Paul Smith <psmith@xxxxxxx>
• Re: Future plans for Autotools
  • From: Paul Smith <psmith@xxxxxxx>
• Re: Future plans for Autotools
  • From: Andy Tai <atai@xxxxxxxx>
• Re: Future plans for Autotools
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: Future plans for Autotools
  • From: Gavin Smith <gavinsmith0123@xxxxxxxxx>
• Re: Future plans for Autotools
  • From: Gavin Smith <gavinsmith0123@xxxxxxxxx>
• Re: Future plans for Autotools
  • From: Nick Bowler <nbowler@xxxxxxxxxx>
• Re: Future plans for Autotools
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• Re: Future plans for Autotools
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: Future plans for Autotools
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• Re: Future plans for Autotools
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• Re: Future plans for Autotools
  • From: Paul Smith <psmith@xxxxxxx>
• Re: Future plans for Autotools
  • From: John Calcote <john.calcote@xxxxxxxxx>
• Re: Future plans for Autotools
  • From: Nick Bowler <nbowler@xxxxxxxxxx>
• Re: Automake's file locking (was Re: Autoconf/Automake is not using version from AC_INIT)
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• Re: Confusing behavior with autoreconf and gettext in the openzfs project
  • From: Eli Schwartz <eschwartz@xxxxxxxxxxxxx>
• Re: Future plans for Autotools
  • From: "David A. Wheeler" <dwheeler@xxxxxxxxxxxx>
• Re: Confusing behavior with autoreconf and gettext in the openzfs project
  • From: Zack Weinberg <zackw@xxxxxxxxx>
• Re: Confusing behavior with autoreconf and gettext in the openzfs project
  • From: Eli Schwartz <eschwartz@xxxxxxxxxxxxx>
• Re: Future plans for Autotools
  • From: Paul Smith <psmith@xxxxxxx>
• Automake's file locking (was Re: Autoconf/Automake is not using version from AC_INIT)
  • From: Zack Weinberg <zackw@xxxxxxxxx>
• Re: Future plans for Autotools
  • From: Zack Weinberg <zackw@xxxxxxxxx>
• Re: Autoconf/Automake is not using version from AC_INIT
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• Re: Autoconf/Automake is not using version from AC_INIT
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• Re: Future plans for Autotools
  • From: Paul Smith <psmith@xxxxxxx>
• Re: Autoconf/Automake is not using version from AC_INIT
  • From: Nick Bowler <nbowler@xxxxxxxxxx>
• Re: Autoconf/Automake is not using version from AC_INIT
  • From: Peter Johansson <trojkan@xxxxxxxxx>
• Re: Autoconf/Automake is not using version from AC_INIT
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: Autoconf/Automake is not using version from AC_INIT
  • From: Zack Weinberg <zackw@xxxxxxxxx>
• Re: Autoconf/Automake is not using version from AC_INIT
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• Re: Autoconf/Automake is not using version from AC_INIT
  • From: Peter Johansson <trojkan@xxxxxxxxx>
• Re: Autoconf/Automake is not using version from AC_INIT
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• Re: Autoconf/Automake is not using version from AC_INIT
  • From: Zack Weinberg <zackw@xxxxxxxxx>
• Re: Autoconf/Automake is not using version from AC_INIT
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• Re: Future plans for Autotools
  • From: Kip Warner <kip@xxxxxxxxxxxxxx>
• Re: Future plans for Autotools
  • From: Eli Schwartz <eschwartz@xxxxxxxxxxxxx>
• Re: Future plans for Autotools
  • From: Nick Bowler <nbowler@xxxxxxxxxx>
• Re: Future plans for Autotools
  • From: John Calcote <john.calcote@xxxxxxxxx>
• Re: Future plans for Autotools
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: Future plans for Autotools
  • From: Andy Tai <atai@xxxxxxxx>
• Re: Future plans for Autotools
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• Re: Future plans for Autotools
  • From: pluto--- via Discussion list for the autoconf build system <autoconf@xxxxxxx>
• Re: Future plans for Autotools
  • From: John Calcote <john.calcote@xxxxxxxxx>
• Re: Future plans for Autotools
  • From: Gavin Smith <gavinsmith0123@xxxxxxxxx>
• Re: Future plans for Autotools
  • From: Zack Weinberg <zackw@xxxxxxxxx>
• Re: Building a cross-compiler
  • From: Sébastien Hinderer <Sebastien.Hinderer@xxxxxxxx>
• Re: Building a cross-compiler
  • From: Zack Weinberg <zackw@xxxxxxxxx>
• Re: Building a cross-compiler
  • From: Sébastien Hinderer <Sebastien.Hinderer@xxxxxxxx>
• Re: Future plans for Autotools
  • From: Nate Bargmann <n0nb@xxxxxxx>
• Re: Future plans for Autotools
  • From: Kip Warner <kip@xxxxxxxxxxxxxx>
• Re: Future plans for Autotools
  • From: Nate Bargmann <n0nb@xxxxxxx>
• Re: Future plans for Autotools
  • From: Dan Kegel <dank@xxxxxxxxx>
• Re: Future plans for Autotools
  • From: Andy Tai <atai@xxxxxxxx>
• Re: Future plans for Autotools
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• Re: Future plans for Autotools
  • From: Gavin Smith <gavinsmith0123@xxxxxxxxx>
• Re: Future plans for Autotools
  • From: Dan Kegel <dank@xxxxxxxxx>
• Future plans for Autotools
  • From: Zack Weinberg <zackw@xxxxxxxxx>
• Re: Building a cross-compiler
  • From: Nick Bowler <nbowler@xxxxxxxxxx>
• Building a cross-compiler
  • From: Sébastien Hinderer <Sebastien.Hinderer@xxxxxxxx>
• Re: Expansion of @libexecdir@ in .desktop.in file includes ${exec_prefix}
  • From: Stefan Koch <stefan.koch10@xxxxxxxxx>
• Re: Expansion of @libexecdir@ in .desktop.in file includes ${exec_prefix}
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: Expansion of @libexecdir@ in .desktop.in file includes ${exec_prefix}
  • From: Nick Bowler <nbowler@xxxxxxxxxx>
• Re: Expansion of @libexecdir@ in .desktop.in file includes ${exec_prefix}
  • From: Eli Schwartz <eschwartz@xxxxxxxxxxxxx>
• Re: Expansion of @libexecdir@ in .desktop.in file includes ${exec_prefix}
  • From: Nick Bowler <nbowler@xxxxxxxxxx>
• Expansion of @libexecdir@ in .desktop.in file includes ${exec_prefix}
  • From: Stefan Koch <stefan.koch10@xxxxxxxxx>
• Re: LIBS or LDLIBS ?
  • From: "Kaz Kylheku (gmake)" <729-670-0061@xxxxxxxxxxx>
• Re: LIBS or LDLIBS ?
  • From: Sébastien Hinderer <Sebastien.Hinderer@xxxxxxxx>
• Re: Autoconf/Automake is not using version from AC_INIT
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• Re: LIBS or LDLIBS ?
  • From: Paul Smith <psmith@xxxxxxx>
• Re: LIBS or LDLIBS ?
  • From: Sébastien Hinderer <Sebastien.Hinderer@xxxxxxxx>
• LIBS or LDLIBS ?
  • From: Sébastien Hinderer <Sebastien.Hinderer@xxxxxxxx>
• Re: Autoconf/Automake is not using version from AC_INIT
  • From: Peter Johansson <trojkan@xxxxxxxxx>
• Re: Autoconf/Automake is not using version from AC_INIT
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• Re: Autoconf/Automake is not using version from AC_INIT
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• Re: Autoconf/Automake is not using version from AC_INIT
  • From: Peter Johansson <trojkan@xxxxxxxxx>
• Re: Autoconf/Automake is not using version from AC_INIT
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• Re: Autoconf/Automake is not using version from AC_INIT
  • From: Peter Johansson <trojkan@xxxxxxxxx>
• Autoconf/Automake is not using version from AC_INIT
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• Re: shell or M4sugar?
  • From: Julien ÉLIE <julien@xxxxxxxxxxxxxxx>
• Re: shell or M4sugar?
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: shell or M4sugar?
  • From: Zack Weinberg <zackw@xxxxxxxxx>
• Re: shell or M4sugar?
  • From: Zack Weinberg <zackw@xxxxxxxxx>
• shell or M4sugar?
  • From: Julien ÉLIE <julien@xxxxxxxxxxxxxxx>
• Re: Autoconf version number after 2.70
  • From: John Calcote <john.calcote@xxxxxxxxx>
• Re: Autoconf version number after 2.70
  • From: Eli Schwartz <eschwartz@xxxxxxxxxxxxx>
• Re: Autoconf version number after 2.70
  • From: Karl Berry <karl@xxxxxxxxxxxxxxx>
• Re: AC_INIT produces unexpected "PACKAGE" and "VERSION" strings in config.h
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• AC_INIT produces unexpected "PACKAGE" and "VERSION" strings in config.h
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• Re: Getting srcdir in script executed using m4_esyscmd in AC_INIT
  • From: Nick Bowler <nbowler@xxxxxxxxxx>
• Re: Getting srcdir in script executed using m4_esyscmd in AC_INIT
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• Re: Autoconf version number after 2.70
  • From: Zack Weinberg <zackw@xxxxxxxxx>
• Re: Getting srcdir in script executed using m4_esyscmd in AC_INIT
  • From: Zack Weinberg <zackw@xxxxxxxxx>
• Re: Getting srcdir in script executed using m4_esyscmd in AC_INIT
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• Re: Getting srcdir in script executed using m4_esyscmd in AC_INIT
  • From: Zack Weinberg <zackw@xxxxxxxxx>
• Re: Getting srcdir in script executed using m4_esyscmd in AC_INIT
  • From: Tim Rice <tim@xxxxxxxxxxxxxxxx>
• Re: Getting srcdir in script executed using m4_esyscmd in AC_INIT
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• Re: Confusing behavior with autoreconf and gettext in the openzfs project
  • From: Zack Weinberg <zackw@xxxxxxxxx>
• Re: Confusing behavior with autoreconf and gettext in the openzfs project
  • From: Eli Schwartz <eschwartz@xxxxxxxxxxxxx>
• Re: Autoconf version number after 2.70
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: Confusing behavior with autoreconf and gettext in the openzfs project
  • From: Zack Weinberg <zackw@xxxxxxxxx>
• Re: Disable the generation of back up ~ files
  • From: Zack Weinberg <zackw@xxxxxxxxx>
• Re: Autoconf version number after 2.70
  • From: Zack Weinberg <zackw@xxxxxxxxx>
• Re: Request to revert the C version change
  • From: Ross Burton <ross@xxxxxxxxxxxxx>
• Re: Getting srcdir in script executed using m4_esyscmd in AC_INIT
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• Re: Getting srcdir in script executed using m4_esyscmd in AC_INIT
  • From: Zack Weinberg <zackw@xxxxxxxxx>
• Getting srcdir in script executed using m4_esyscmd in AC_INIT
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• Re: Autoconf version number after 2.70
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• Disable the generation of back up ~ files
  • From: nu quaquaraqua <nuquaquaraqua@xxxxxxxxx>
• Re: Autoconf version number after 2.70
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: Autoconf version number after 2.70
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: Autoconf version number after 2.70
  • From: Marko Lindqvist <cazfi74@xxxxxxxxx>
• Re: Autoconf version number after 2.70
  • From: "David A. Wheeler" <dwheeler@xxxxxxxxxxxx>
• Re: Autoconf version number after 2.70
  • From: Zack Weinberg <zackw@xxxxxxxxx>
• Confusing behavior with autoreconf and gettext in the openzfs project
  • From: Eli Schwartz <eschwartz@xxxxxxxxxxxxx>
• Re: Autoconf version number after 2.70
  • From: Julien ÉLIE <julien@xxxxxxxxxxxxxxx>
• Autoconf version number after 2.70
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: gnulib / autoconf sync
  • From: Bruno Haible <bruno@xxxxxxxxx>
• Re: gnulib / autoconf sync
  • From: Bruno Haible <bruno@xxxxxxxxx>
• Re: Request to revert the C version change
  • From: Zack Weinberg <zackw@xxxxxxxxx>
• Re: Configure.in can't detect Xft libraries.
  • From: alexandre schenberg <ale.schenberg@xxxxxxxxxx>
• Re: Configure.in can't detect Xft libraries.
  • From: Zack Weinberg <zackw@xxxxxxxxx>
• Configure.in can't detect Xft libraries.
  • From: alexandre schenberg <ale.schenberg@xxxxxxxxxx>
• Re: Reautoconfing
  • From: Wookey <wookey@xxxxxxxxxxxx>
• Re: Reautoconfing
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: Reautoconfing
  • From: Wookey <wookey@xxxxxxxxxxxx>
• Re: Request to revert the C version change
  • From: Zack Weinberg <zackw@xxxxxxxxx>
• Re: Request to revert the C version change
  • From: Zack Weinberg <zackw@xxxxxxxxx>
• Re: Request to revert the C version change
  • From: Zack Weinberg <zackw@xxxxxxxxx>
• Re: Request to revert the C version change
  • From: Ross Burton <ross@xxxxxxxxxxxxx>
• Re: Request to revert the C version change
  • From: Bruno Haible <bruno@xxxxxxxxx>
• Re: Request to revert the C version change
  • From: Zack Weinberg <zackw@xxxxxxxxx>
• Re: Request to revert the C version change
  • From: Zack Weinberg <zackw@xxxxxxxxx>
• Re: Request to revert the C version change
  • From: "Todd C. Miller" <Todd.Miller@xxxxxxx>
• Re: Request to revert the C version change
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• Re: Request to revert the C version change
  • From: "Todd C. Miller" <Todd.Miller@xxxxxxx>
• Re: Request to revert the C version change
  • From: Zack Weinberg <zackw@xxxxxxxxx>
• Re: Request to revert the C version change
  • From: Ross Burton <ross@xxxxxxxxxxxxx>
• Re: Request to revert the C version change
  • From: Zack Weinberg <zackw@xxxxxxxxx>
• Request to revert the C version change
  • From: Ross Burton <ross@xxxxxxxxxxxxx>
• Re: 2.70 release branch created; trunk open for development
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: autoconf-2.70 released [stable]
  • From: Gavin Smith <gavinsmith0123@xxxxxxxxx>
• Re: 2.70 release branch created; trunk open for development
  • From: Zack Weinberg <zackw@xxxxxxxxx>
• Re: 2.70 release branch created; trunk open for development
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: Hidden files in autoconf 2.70 distribution?
  • From: "Dmitry V. Levin" <ldv@xxxxxxxxxxxx>
• Re: Hidden files in autoconf 2.70 distribution?
  • From: Jim Meyering <jim@xxxxxxxxxxxx>
• Re: Hidden files in autoconf 2.70 distribution?
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: Hidden files in autoconf 2.70 distribution?
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• Re: Hidden files in autoconf 2.70 distribution?
  • From: Bruno Haible <bruno@xxxxxxxxx>
• Re: Hidden files in autoconf 2.70 distribution?
  • From: Zack Weinberg <zackw@xxxxxxxxx>
• Re: Hidden files in autoconf 2.70 distribution?
  • From: Bruce Korb <bkorb@xxxxxxx>
• Re: Hidden files in autoconf 2.70 distribution?
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• 2.70 release branch created; trunk open for development
  • From: Zack Weinberg <zackw@xxxxxxxxx>
• Re: Hidden files in autoconf 2.70 distribution?
  • From: Zack Weinberg <zackw@xxxxxxxxx>
• Hidden files in autoconf 2.70 distribution?
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• Re: autoconf-2.70 released [stable]
  • From: John Calcote <john.calcote@xxxxxxxxx>
• autoconf-2.70 released [stable]
  • From: zackw@xxxxxxxxx (Zack Weinberg)
• Re: autoconf-2.69e released [2.70 RELEASE CANDIDATE]
  • From: John Calcote <john.calcote@xxxxxxxxx>
• autoconf-2.69e released [2.70 RELEASE CANDIDATE]
  • From: zackw@xxxxxxxxx
• Autoconf release status update for 2020-11-16; call for help
  • From: Zack Weinberg <zackw@xxxxxxxxx>
• Change in gettext behaviour
  • From: Ross Burton <ross@xxxxxxxxxxxxx>
• Re: Weird failure with autoconf 2.69c in gmp
  • From: Zack Weinberg <zackw@xxxxxxxxx>
• Re: Weird failure with autoconf 2.69c in gmp
  • From: Ross Burton <ross@xxxxxxxxxxxxx>
• Autoconf release status update for 2020-11-09
  • From: Zack Weinberg <zackw@xxxxxxxxx>
• Re: Apply fix for AM_GNU_GETTEXT_REQUIRE_VERSION
  • From: Zack Weinberg <zackw@xxxxxxxxx>
• Apply fix for AM_GNU_GETTEXT_REQUIRE_VERSION
  • From: Nicholas Guriev <nicholas@xxxxxxxxx>
• Fallout from _AC_UNDECLARED_WARNING in autoconf 2.70beta
  • From: Stephan Bergmann <sbergman@xxxxxxxxxx>
• autoconf-2.69d released [beta]
  • From: Zack Weinberg <zackw@xxxxxxxxxxxxx>
• Re: Autoconf 2.70 release status update as of 2020-11-02
  • From: Lars Wendler <polynomial-c@xxxxxxxxxx>
• Re: Autoconf 2.70 release status update as of 2020-11-02
  • From: Michael Orlitzky <michael@xxxxxxxxxxxx>
• Autoconf 2.70 release status update as of 2020-11-02
  • From: Zack Weinberg <zackw@xxxxxxxxx>
• Re: [PATCH] similar treatment for CYGWIN and MSYS2
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• Re: [autoconf 2.69c] test 36: autoupdating AC_OBSOLETE fails when configure reads config.site
  • From: Zack Weinberg <zackw@xxxxxxxxx>
• RE: [autoconf 2.69c] test 36: autoupdating AC_OBSOLETE fails when configure reads config.site
  • From: "Jannick" <thirdedition@xxxxxxx>
• RE: [PATCH] similar treatment for CYGWIN and MSYS2
  • From: "Jannick" <thirdedition@xxxxxxx>
• Re: [PATCH] similar treatment for CYGWIN and MSYS2
  • From: Zack Weinberg <zackw@xxxxxxxxx>
• [autoconf 2.69c] test 36: autoupdating AC_OBSOLETE fails when configure reads config.site
  • From: "Jannick" <thirdedition@xxxxxxx>
• Re: determine base type of a typedef
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: determine base type of a typedef
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• [PATCH] similar treatment for CYGWIN and MSYS2
  • From: "Jannick" <thirdedition@xxxxxxx>
• RE: Debian archive rebuild with Autoconf 2.69c
  • From: "Jannick" <thirdedition@xxxxxxx>
• Re: determine base type of a typedef
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: determine base type of a typedef
  • From: Anatoli <me@xxxxxxxxxx>
• Re: determine base type of a typedef
  • From: Anatoli <me@xxxxxxxxxx>
• Re: Debian archive rebuild with Autoconf 2.69c
  • From: wferi@xxxxxxxxxx
• Re: determine base type of a typedef
  • From: Nick Bowler <nbowler@xxxxxxxxxx>
• Re: determine base type of a typedef
  • From: Nick Bowler <nbowler@xxxxxxxxxx>
• Re: determine base type of a typedef
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: determine base type of a typedef
  • From: Peter Johansson <trojkan@xxxxxxxxx>
• Re: determine base type of a typedef
  • From: Anatoli <me@xxxxxxxxxx>
• Re: determine base type of a typedef
  • From: Anatoli <me@xxxxxxxxxx>
• Re: determine base type of a typedef
  • From: Russell Shaw <rjshaw@xxxxxxxxxxxxxxx>
• Re: determine base type of a typedef
  • From: Russell Shaw <rjshaw@xxxxxxxxxxxxxxx>
• Re: determine base type of a typedef
  • From: Anatoli <me@xxxxxxxxxx>
• Re: determine base type of a typedef
  • From: Russell Shaw <rjshaw@xxxxxxxxxxxxxxx>
• Re: determine base type of a typedef
  • From: Vivien Kraus <vivien@xxxxxxxxxxxxxxxx>
• Re: determine base type of a typedef
  • From: Anatoli <me@xxxxxxxxxx>
• Re: determine base type of a typedef
  • From: Russell Shaw <rjshaw@xxxxxxxxxxxxxxx>
• determine base type of a typedef
  • From: Anatoli <me@xxxxxxxxxx>
• Re: Weird failure with autoconf 2.69c in gmp
  • From: Zack Weinberg <zackw@xxxxxxxxx>
• Re: autoconf-2.69c Gentoo tinderbox run
  • From: Zack Weinberg <zackw@xxxxxxxxx>
• autoconf-2.69c Gentoo tinderbox run
  • From: Michael Orlitzky <michael@xxxxxxxxxxxx>
• Re: AC_PATH_X and friends explicitly look into /usr/lib
  • From: Ross Burton <ross@xxxxxxxxxxxxx>
• Re: AC_PATH_X and friends explicitly look into /usr/lib
  • From: Zack Weinberg <zackw@xxxxxxxxx>
• AC_PATH_X and friends explicitly look into /usr/lib
  • From: Ross Burton <ross@xxxxxxxxxxxxx>
• Re: Weird failure with autoconf 2.69c in gmp
  • From: Ross Burton <ross@xxxxxxxxxxxxx>
• Re: Exactly when does autoconf enter cross-compilation mode? (documentation)
  • From: Zack Weinberg <zackw@xxxxxxxxx>
• Re: Weird failure with autoconf 2.69c in gmp
  • From: Zack Weinberg <zackw@xxxxxxxxx>
• Re: Weird failure with autoconf 2.69c in gmp
  • From: Zack Weinberg <zackw@xxxxxxxxx>
• Re: Weird failure with autoconf 2.69c in gmp
  • From: Nick Bowler <nbowler@xxxxxxxxxx>
• Re: Weird failure with autoconf 2.69c in gmp
  • From: Ross Burton <ross@xxxxxxxxxxxxx>
• Re: Weird failure with autoconf 2.69c in gmp
  • From: Ross Burton <ross@xxxxxxxxxxxxx>
• Re: Weird failure with autoconf 2.69c in gmp
  • From: Ross Burton <ross@xxxxxxxxxxxxx>
• Re: Weird failure with autoconf 2.69c in gmp
  • From: Nick Bowler <nbowler@xxxxxxxxxx>
• Re: Weird failure with autoconf 2.69c in gmp
  • From: Zack Weinberg <zackw@xxxxxxxxx>
• Weird failure with autoconf 2.69c in gmp
  • From: Ross Burton <ross@xxxxxxxxxxxxx>
• Re: Licensing of Autoconf
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Licensing of Autoconf
  • From: Jack Pearson <jackrpearson@xxxxxxxxxxxxxx>
• Re: Exactly when does autoconf enter cross-compilation mode? (documentation)
  • From: wferi@xxxxxxx
• Re: Debian archive rebuild with Autoconf 2.69c
  • From: Zack Weinberg <zackw@xxxxxxxxx>
• Re: Debian archive rebuild with Autoconf 2.69c
  • From: Ben Pfaff <blp@xxxxxxxxxxxxxxx>
• Re: verifying autoconf-2.69c.tar.xz.sig
  • From: Zack Weinberg <zackw@xxxxxxxxx>
• Re: verifying autoconf-2.69c.tar.xz.sig
  • From: Thien-Thi Nguyen <ttn@xxxxxxxxxxx>
• Re: verifying autoconf-2.69c.tar.xz.sig
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: verifying autoconf-2.69c.tar.xz.sig
  • From: Zack Weinberg <zackw@xxxxxxxxx>
• Re: verifying autoconf-2.69c.tar.xz.sig
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• Re: verifying autoconf-2.69c.tar.xz.sig
  • From: Andreas Kusalananda Kähäri <andreas.kahari@xxxxxx>
• Re: verifying autoconf-2.69c.tar.xz.sig
  • From: Thien-Thi Nguyen <ttn@xxxxxxxxxxx>
• verifying autoconf-2.69c.tar.xz.sig
  • From: Thien-Thi Nguyen <ttn@xxxxxxxxxxx>
• Re: autoconf-2.69c released [beta]
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• Re: autoconf-2.69c released [beta]
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: autoconf-2.69c released [beta]
  • From: Zack Weinberg <zackw@xxxxxxxxx>
• Re: autoconf-2.69c released [beta]
  • From: Zack Weinberg <zackw@xxxxxxxxx>
• Re: autoconf-2.69c released [beta]
  • From: Zack Weinberg <zackw@xxxxxxxxx>
• Re: autoconf-2.69c released [beta]
  • From: Russ Allbery <eagle@xxxxxxxxx>
• Re: autoconf-2.69c released [beta]
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• Re: autoconf-2.69c released [beta]
  • From: Bruno Haible <bruno@xxxxxxxxx>
• Re: Results from running autoupdate on gnulib m4 files
  • From: Bruno Haible <bruno@xxxxxxxxx>
• Re: autoconf-2.69c released [beta]
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: autoconf-2.69c released [beta]
  • From: Bruno Haible <bruno@xxxxxxxxx>
• Re: autoconf-2.69c released [beta]
  • From: Gavin Smith <gavinsmith0123@xxxxxxxxx>
• Re: autoconf-2.69c released [beta]
  • From: Gavin Smith <gavinsmith0123@xxxxxxxxx>
• Re: autoconf-2.69c released [beta]
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• Re: autoconf-2.69c released [beta]
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• Re: autoconf-2.69c released [beta]
  • From: Gavin Smith <gavinsmith0123@xxxxxxxxx>
• Re: autoconf-2.69c released [beta]
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: autoconf-2.69c released [beta]
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• Re: autoconf-2.69c released [beta]
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• Re: Results from running autoupdate on gnulib m4 files
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: Debian archive rebuild with Autoconf 2.69c
  • From: Lucas Nussbaum <lucas@xxxxxxxxxx>
• RE: autoconf's -I flag in simple configure.ac cases
  • From: "Jannick" <thirdedition@xxxxxxx>
• Re: autoconf's -I flag in simple configure.ac cases
  • From: Zack Weinberg <zackw@xxxxxxxxx>
• autoconf's -I flag in simple configure.ac cases
  • From: "Jannick" <thirdedition@xxxxxxx>
• Re: Results from running autoupdate on gnulib m4 files
  • From: Zack Weinberg <zackw@xxxxxxxxx>
• Re: autoconf-2.69c released [beta]
  • From: Bruno Haible <bruno@xxxxxxxxx>
• Results from running autoupdate on gnulib m4 files
  • From: Gavin Smith <gavinsmith0123@xxxxxxxxx>
• Re: autoconf-2.69c released [beta]
  • From: Gavin Smith <gavinsmith0123@xxxxxxxxx>
• Re: autoconf-2.69c released [beta]
  • From: Gavin Smith <gavinsmith0123@xxxxxxxxx>
• Re: autoconf-2.69c released [beta]
  • From: Gavin Smith <gavinsmith0123@xxxxxxxxx>
• Re: autoconf-2.69c released [beta]
  • From: Bruno Haible <bruno@xxxxxxxxx>
• Re: autoconf-2.69c released [beta]
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: autoconf-2.69c released [beta]
  • From: Zack Weinberg <zackw@xxxxxxxxx>
• Re: Debian archive rebuild with Autoconf 2.69c
  • From: Zack Weinberg <zackw@xxxxxxxxx>
• Re: Debian archive rebuild with Autoconf 2.69c
  • From: Zack Weinberg <zackw@xxxxxxxxx>
• Re: autoconf-2.69c released [beta]
  • From: Gavin Smith <gavinsmith0123@xxxxxxxxx>
• Re: autoconf-2.69c released [beta]
  • From: Gavin Smith <gavinsmith0123@xxxxxxxxx>
• Re: Debian archive rebuild with Autoconf 2.69c
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• Re: Debian archive rebuild with Autoconf 2.69c
  • From: Zack Weinberg <zackw@xxxxxxxxx>
• Re: Debian archive rebuild with Autoconf 2.69c
  • From: Lucas Nussbaum <lucas@xxxxxxxxxx>
• Debian archive rebuild with Autoconf 2.69c
  • From: Zack Weinberg <zackw@xxxxxxxxx>
• autoconf-2.69c released [beta]
  • From: Zack Weinberg <zackw@xxxxxxxxx>
• Re: Warning category skew between Autoconf and Automake - workaround in autoreconf?
  • From: Zack Weinberg <zackw@xxxxxxxxx>