Gnu Autoconf

• Thread Index

• Re: aclocal's past and future home (was Re: Best practise for aclocal paths in cross builds)
  • From: Ross Burton <Ross.Burton@xxxxxxx>
• aclocal's past and future home (was Re: Best practise for aclocal paths in cross builds)
  • From: "Zack Weinberg" <zack@xxxxxxxxxxxx>
• Re: Best practise for aclocal paths in cross builds
  • From: Ross Burton <Ross.Burton@xxxxxxx>
• Re: Best practise for aclocal paths in cross builds
  • From: Nick Bowler <nbowler@xxxxxxxxxx>
• Best practise for aclocal paths in cross builds
  • From: Ross Burton <Ross.Burton@xxxxxxx>
• Re: stumped on a simple autoconf/m4/sh problem
  • From: "G. Branden Robinson" <g.branden.robinson@xxxxxxxxx>
• Re: stumped on a simple autoconf/m4/sh problem
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: stumped on a simple autoconf/m4/sh problem
  • From: "G. Branden Robinson" <g.branden.robinson@xxxxxxxxx>
• Re: stumped on a simple autoconf/m4/sh problem
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: Enabling shell error handling in configure.ac
  • From: "Zack Weinberg" <zack@xxxxxxxxxxxx>
• Re: stumped on a simple autoconf/m4/sh problem
  • From: "Zack Weinberg" <zack@xxxxxxxxxxxx>
• Re: stumped on a simple autoconf/m4/sh problem
  • From: Jacob Bachmeyer <jcb62281@xxxxxxxxx>
• Re: stumped on a simple autoconf/m4/sh problem
  • From: "G. Branden Robinson" <g.branden.robinson@xxxxxxxxx>
• Re: stumped on a simple autoconf/m4/sh problem
  • From: Jacob Bachmeyer <jcb62281@xxxxxxxxx>
• stumped on a simple autoconf/m4/sh problem
  • From: "G. Branden Robinson" <g.branden.robinson@xxxxxxxxx>
• Re: Enabling shell error handling in configure.ac
  • From: "R. Diez" <rdiez-2006@xxxxxxx>
• Re: Enabling shell error handling in configure.ac
  • From: "Zack Weinberg" <zack@xxxxxxxxxxxx>
• Re: Enabling shell error handling in configure.ac
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Enabling shell error handling in configure.ac
  • From: "R. Diez" <rdiez-2006@xxxxxxx>
• Is autoconf-patches still the correct place to send patches?
  • From: jack@xxxxxxxxxxxxxx
• Re: followup to AC_FUNC_MALLOC, AC_FUNC_REALLOC changes
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• followup to AC_FUNC_MALLOC, AC_FUNC_REALLOC changes
  • From: Bruno Haible via Discussion list for the autoconf build system <autoconf@xxxxxxx>
• Re: INSTALL mentions "bootstrap" file
  • From: Gavin Smith <gavinsmith0123@xxxxxxxxx>
• Re: INSTALL mentions "bootstrap" file
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• INSTALL mentions "bootstrap" file
  • From: Gavin Smith <gavinsmith0123@xxxxxxxxx>
• Re: How to make "configure: WARNING: unrecognized options: --enable-…" an error
  • From: "Murrell, Brian" <brian.murrell@xxxxxxxxx>
• Re: How to make "configure: WARNING: unrecognized options: --enable-…" an error
  • From: Nick Bowler <nbowler@xxxxxxxxxx>
• How to make "configure: WARNING: unrecognized options: --enable-…" an error
  • From: "Murrell, Brian" <brian.murrell@xxxxxxxxx>
• Re: config.status[12]: export: SHELL##: is not an identifier
  • From: Andy Fiddaman <andy@xxxxxxxxxx>
• Re: config.status[12]: export: SHELL##: is not an identifier
  • From: Nick Bowler <nbowler@xxxxxxxxxx>
• Re: config.status[12]: export: SHELL##: is not an identifier
  • From: "Zack Weinberg" <zack@xxxxxxxxxxxx>
• Re: config.status[12]: export: SHELL##: is not an identifier
  • From: Andy Fiddaman <andy@xxxxxxxxxx>
• Re: config.status[12]: export: SHELL##: is not an identifier
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: config.status[12]: export: SHELL##: is not an identifier
  • From: "Zack Weinberg" <zack@xxxxxxxxxxxx>
• Re: config.status[12]: export: SHELL##: is not an identifier
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: config.status[12]: export: SHELL##: is not an identifier
  • From: Bob Friesenhahn <graphicsmagick.project@xxxxxxxxx>
• Re: config.status[12]: export: SHELL##: is not an identifier
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: config.status[12]: export: SHELL##: is not an identifier
  • From: "Zack Weinberg" <zack@xxxxxxxxxxxx>
• Re: config.status[12]: export: SHELL##: is not an identifier
  • From: Bob Friesenhahn <graphicsmagick.project@xxxxxxxxx>
• Re: config.status[12]: export: SHELL##: is not an identifier
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: config.status[12]: export: SHELL##: is not an identifier
  • From: Bob Friesenhahn <graphicsmagick.project@xxxxxxxxx>
• Re: config.status[12]: export: SHELL##: is not an identifier
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: config.status[12]: export: SHELL##: is not an identifier
  • From: Bob Friesenhahn <graphicsmagick.project@xxxxxxxxx>
• Re: config.status[12]: export: SHELL##: is not an identifier
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• config.status[12]: export: SHELL##: is not an identifier
  • From: Bob Friesenhahn <graphicsmagick.project@xxxxxxxxx>
• Re: AC_FUNC_MMAP test fails on AIX for MAP_FIXED: who's at fault?
  • From: Russ Allbery <eagle@xxxxxxxxx>
• Re: AC_FUNC_MMAP test fails on AIX for MAP_FIXED: who's at fault?
  • From: Howard Chu via Discussion list for the autoconf build system <autoconf@xxxxxxx>
• Re: AC_FUNC_MMAP test fails on AIX for MAP_FIXED: who's at fault?
  • From: Russ Allbery <eagle@xxxxxxxxx>
• Re: AC_FUNC_MMAP test fails on AIX for MAP_FIXED: who's at fault?
  • From: "Zack Weinberg" <zack@xxxxxxxxxxxx>
• Re: AC_FUNC_MMAP test fails on AIX for MAP_FIXED: who's at fault?
  • From: "Yury V. Zaytsev" <yury@xxxxxxxxxx>
• Re: AC_FUNC_MMAP test fails on AIX for MAP_FIXED: who's at fault?
  • From: "Yury V. Zaytsev" <yury@xxxxxxxxxx>
• Re: AC_FUNC_MMAP test fails on AIX for MAP_FIXED: who's at fault?
  • From: Tim Rice <tim@xxxxxxxxxxxxxxxx>
• Re: AC_FUNC_MMAP test fails on AIX for MAP_FIXED: who's at fault?
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: First draft of application to Sovereign Tech Fund
  • From: Karl Berry <karl@xxxxxxxxxxxxxxx>
• Re: AC_FUNC_MMAP test fails on AIX for MAP_FIXED: who's at fault?
  • From: pluto--- via Discussion list for the autoconf build system <autoconf@xxxxxxx>
• Re: AC_FUNC_MMAP test fails on AIX for MAP_FIXED: who's at fault?
  • From: Howard Chu via Discussion list for the autoconf build system <autoconf@xxxxxxx>
• Re: First draft of application to Sovereign Tech Fund
  • From: "Zack Weinberg" <zack@xxxxxxxxxxxx>
• Re: AC_FUNC_MMAP test fails on AIX for MAP_FIXED: who's at fault?
  • From: "Zack Weinberg" <zack@xxxxxxxxxxxx>
• Re: First draft of application to Sovereign Tech Fund
  • From: Detlef Riekenberg <wine.dev@xxxxxx>
• Re: AC_FUNC_MMAP test fails on AIX for MAP_FIXED: who's at fault?
  • From: "Yury V. Zaytsev" <yury@xxxxxxxxxx>
• Re: AC_FUNC_MMAP test fails on AIX for MAP_FIXED: who's at fault?
  • From: Brooks Davis <brooks@xxxxxxxxxxx>
• Re: AC_FUNC_MMAP test fails on AIX for MAP_FIXED: who's at fault?
  • From: Howard Chu via Discussion list for the autoconf build system <autoconf@xxxxxxx>
• Re: AC_FUNC_MMAP test fails on AIX for MAP_FIXED: who's at fault?
  • From: Bob Friesenhahn <graphicsmagick.project@xxxxxxxxx>
• Re: AC_FUNC_MMAP test fails on AIX for MAP_FIXED: who's at fault?
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: AC_FUNC_MMAP test fails on AIX for MAP_FIXED: who's at fault?
  • From: "Yury V. Zaytsev" <yury@xxxxxxxxxx>
• Re: AC_FUNC_MMAP test fails on AIX for MAP_FIXED: who's at fault?
  • From: "Yury V. Zaytsev" <yury@xxxxxxxxxx>
• Re: AC_FUNC_MMAP test fails on AIX for MAP_FIXED: who's at fault?
  • From: "Zack Weinberg" <zack@xxxxxxxxxxxx>
• Re: AC_FUNC_MMAP test fails on AIX for MAP_FIXED: who's at fault?
  • From: Bob Friesenhahn <graphicsmagick.project@xxxxxxxxx>
• Re: AC_FUNC_MMAP test fails on AIX for MAP_FIXED: who's at fault?
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: AC_FUNC_MMAP test fails on AIX for MAP_FIXED: who's at fault?
  • From: Bob Friesenhahn <graphicsmagick.project@xxxxxxxxx>
• Re: AC_FUNC_MMAP test fails on AIX for MAP_FIXED: who's at fault?
  • From: "Yury V. Zaytsev" <yury@xxxxxxxxxx>
• AC_FUNC_MMAP test fails on AIX for MAP_FIXED: who's at fault?
  • From: "Yury V. Zaytsev" <yury@xxxxxxxxxx>
• Re: First draft of application to Sovereign Tech Fund
  • From: Karl Berry <karl@xxxxxxxxxxxxxxx>
• Re: First draft of application to Sovereign Tech Fund
  • From: Christoph Grüninger <foss@xxxxxxxxxxxxx>
• Re: First draft of application to Sovereign Tech Fund
  • From: Karl Berry <karl@xxxxxxxxxxxxxxx>
• Re: First draft of application to Sovereign Tech Fund
  • From: Christoph Grüninger <foss@xxxxxxxxxxxxx>
• Re: AC_TRY_COMMAND use case
  • From: "Zack Weinberg" <zack@xxxxxxxxxxxx>
• AC_TRY_COMMAND use case
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: First draft of application to Sovereign Tech Fund
  • From: Karl Berry <karl@xxxxxxxxxxxxxxx>
• Re: RFC: Add public macros AC_LOG_CMD and AC_LOG_FILE.
  • From: "Zack Weinberg" <zack@xxxxxxxxxxxx>
• Re: RFC: Add public macros AC_LOG_CMD and AC_LOG_FILE.
  • From: Karl Berry <karl@xxxxxxxxxxxxxxx>
• Re: RFC: Add public macros AC_LOG_CMD and AC_LOG_FILE.
  • From: Nick Bowler <nbowler@xxxxxxxxxx>
• Re: RFC: Add public macros AC_LOG_CMD and AC_LOG_FILE.
  • From: "Zack Weinberg" <zack@xxxxxxxxxxxx>
• Re: RFC: Add public macros AC_LOG_CMD and AC_LOG_FILE.
  • From: Nick Bowler <nbowler@xxxxxxxxxx>
• RFC: Add public macros AC_LOG_CMD and AC_LOG_FILE.
  • From: "Zack Weinberg" <zack@xxxxxxxxxxxx>
• Re: Bug Resilience Program of German Sovereign Tech Fund
  • From: Christoph Grüninger <foss@xxxxxxxxxxxxx>
• First draft of application to Sovereign Tech Fund
  • From: Christoph Grüninger <foss@xxxxxxxxxxxxx>
• Re: Bug Resilience Program of German Sovereign Tech Fund
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: Bug Resilience Program of German Sovereign Tech Fund
  • From: Christoph Grüninger <foss@xxxxxxxxxxxxx>
• Re: Bug Resilience Program of German Sovereign Tech Fund
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: Bug Resilience Program of German Sovereign Tech Fund
  • From: Christoph Grüninger <foss@xxxxxxxxxxxxx>
• Re: Bug Resilience Program of German Sovereign Tech Fund
  • From: Christoph Grüninger <foss@xxxxxxxxxxxxx>
• Re: Bug Resilience Program of German Sovereign Tech Fund
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: Bug Resilience Program of German Sovereign Tech Fund
  • From: "Zack Weinberg" <zack@xxxxxxxxxxxx>
• Re: configure adds -std=gnu++11 to CXX variable
  • From: Jason Merrill <jason@xxxxxxxxxx>
• Re: configure adds -std=gnu++11 to CXX variable
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: configure adds -std=gnu++11 to CXX variable
  • From: Joseph Myers <josmyers@xxxxxxxxxx>
• Re: configure adds -std=gnu++11 to CXX variable
  • From: Jason Merrill <jason@xxxxxxxxxx>
• Re: configure adds -std=gnu++11 to CXX variable
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: configure adds -std=gnu++11 to CXX variable
  • From: Jason Merrill <jason@xxxxxxxxxx>
• Re: configure adds -std=gnu++11 to CXX variable
  • From: Jakub Jelinek <jakub@xxxxxxxxxx>
• Re: configure adds -std=gnu++11 to CXX variable
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: configure adds -std=gnu++11 to CXX variable
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: configure adds -std=gnu++11 to CXX variable
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: configure adds -std=gnu++11 to CXX variable
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: configure adds -std=gnu++11 to CXX variable
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: configure adds -std=gnu++11 to CXX variable
  • From: Jakub Jelinek <jakub@xxxxxxxxxx>
• Re: configure adds -std=gnu++11 to CXX variable
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: configure adds -std=gnu++11 to CXX variable
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: configure adds -std=gnu++11 to CXX variable
  • From: "Zack Weinberg" <zack@xxxxxxxxxxxx>
• Re: configure adds -std=gnu++11 to CXX variable
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: configure adds -std=gnu++11 to CXX variable
  • From: Peter Johansson <trojkan@xxxxxxxxx>
• Re: C23 support in Autoconf
  • From: Alan Coopersmith <alan.coopersmith@xxxxxxxxxx>
• Re: C23 support in Autoconf
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: C23 support in Autoconf
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: C23 support in Autoconf
  • From: Nick Bowler <nbowler@xxxxxxxxxx>
• Re: C23 support in Autoconf
  • From: Jacob Bachmeyer <jcb62281@xxxxxxxxx>
• Re: C23 support in Autoconf
  • From: Antonin Décimo <antonin@xxxxxxxxxxx>
• Re: C23 support in Autoconf
  • From: Alan Coopersmith <alan.coopersmith@xxxxxxxxxx>
• Re: C23 support in Autoconf
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: C23 support in Autoconf
  • From: "Zack Weinberg" <zack@xxxxxxxxxxxx>
• Re: C23 support in Autoconf
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: Making MSVC/clang-cl succeed AC_PROG_CC C11 discovery
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: C23 support in Autoconf
  • From: "Zack Weinberg" <zack@xxxxxxxxxxxx>
• Re: C23 support in Autoconf
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: C23 support in Autoconf
  • From: Alan Coopersmith <alan.coopersmith@xxxxxxxxxx>
• Re: Making MSVC/clang-cl succeed AC_PROG_CC C11 discovery
  • From: Sam James <sam@xxxxxxxxxx>
• Re: Making MSVC/clang-cl succeed AC_PROG_CC C11 discovery
  • From: Werner LEMBERG <wl@xxxxxxx>
• Re: Making MSVC/clang-cl succeed AC_PROG_CC C11 discovery
  • From: Antonin Décimo <antonin@xxxxxxxxxxx>
• Re: Making MSVC/clang-cl succeed AC_PROG_CC C11 discovery
  • From: Antonin Décimo <antonin@xxxxxxxxxxx>
• Re: Making MSVC/clang-cl succeed AC_PROG_CC C11 discovery
  • From: Sam James <sam@xxxxxxxxxx>
• C23 support in Autoconf
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: Making MSVC/clang-cl succeed AC_PROG_CC C11 discovery
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: Making MSVC/clang-cl succeed AC_PROG_CC C11 discovery
  • From: Antonin Décimo <antonin@xxxxxxxxxxx>
• Re: Making MSVC/clang-cl succeed AC_PROG_CC C11 discovery
  • From: Zack Weinberg <zack@xxxxxxxxxxxx>
• Making MSVC/clang-cl succeed AC_PROG_CC C11 discovery
  • From: Antonin Décimo <antonin.decimo@xxxxxxxxx>
• Making MSVC/clang-cl succeed AC_PROG_CC C11 discovery
  • From: Antonin Décimo <antonin@xxxxxxxxxxx>
• Re: configure adds -std=gnu++11 to CXX variable
  • From: Peter Johansson <trojkan@xxxxxxxxx>
• Re: configure adds -std=gnu++11 to CXX variable
  • From: "Zack Weinberg" <zack@xxxxxxxxxxxx>
• Re: configure adds -std=gnu++11 to CXX variable
  • From: "Zack Weinberg" <zack@xxxxxxxxxxxx>
• configure adds -std=gnu++11 to CXX variable
  • From: Peter Johansson <trojkan@xxxxxxxxx>
• Re: Is it safe to use ax_gcc_builtin to detect __builtin_offsetof?
  • From: Jacob Bachmeyer <jcb62281@xxxxxxxxx>
• Re: Is it safe to use ax_gcc_builtin to detect __builtin_offsetof?
  • From: Nick Bowler <nbowler@xxxxxxxxxx>
• Re: Is it safe to use ax_gcc_builtin to detect __builtin_offsetof?
  • From: "Zack Weinberg" <zack@xxxxxxxxxxxx>
• Re: Is it safe to use ax_gcc_builtin to detect __builtin_offsetof?
  • From: Peter Hull <peterhull90@xxxxxxxxx>
• Re: Is it safe to use ax_gcc_builtin to detect __builtin_offsetof?
  • From: pluto--- via Discussion list for the autoconf build system <autoconf@xxxxxxx>
• Re: Is it safe to use ax_gcc_builtin to detect __builtin_offsetof?
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Is it safe to use ax_gcc_builtin to detect __builtin_offsetof?
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Re: Android and iOS triplets are not recognized
  • From: Mike Frysinger <vapier@xxxxxxxxxx>
• Re: Android and iOS triplets are not recognized
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: Android and iOS triplets are not recognized
  • From: Mike Frysinger <vapier@xxxxxxxxxx>
• Re: Embed newlines in AC_MSG_* output
  • From: Nick Bowler <nbowler@xxxxxxxxxx>
• Re: Embed newlines in AC_MSG_* output
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Embed newlines in AC_MSG_* output
  • From: Dave Hart <davehart@xxxxxxxxx>
• Unavailable due to hardware problems
  • From: "Zack Weinberg" <zack@xxxxxxxxxxxx>
• Re: bug#68274: automake 1.16j nonnumerical version confuses scripts
  • From: Sam James <sam@xxxxxxxxxx>
• Re: bug#68274: automake 1.16j nonnumerical version confuses scripts
  • From: "Zack Weinberg" <zack@xxxxxxxxxxxx>
• Re: Future plans for Autotools
  • From: Michael Orlitzky <michael@xxxxxxxxxxxx>
• Re: Future plans for Autotools
  • From: Adam Faiz via Discussion list for the autoconf build system <autoconf@xxxxxxx>
• autoconf-2.72 released [stable]
  • From: "Zack Weinberg" <zack@xxxxxxxxxxxx>
• Re: AT_MTIME_DELAY not working?
  • From: "Zack Weinberg" <zack@xxxxxxxxxxxx>
• Re: AT_MTIME_DELAY not working?
  • From: Nick Bowler <nbowler@xxxxxxxxxx>
• Re: AT_MTIME_DELAY not working? (was: Re: [platform-testers] autoconf-2.72e released [release candidate])
  • From: "Zack Weinberg" <zack@xxxxxxxxxxxx>
• AT_MTIME_DELAY not working? (was: Re: [platform-testers] autoconf-2.72e released [release candidate])
  • From: Jacob Bachmeyer <jcb62281@xxxxxxxxx>
• Re: autoconf-2.72e released [release candidate]
  • From: "Zack Weinberg" <zack@xxxxxxxxxxxx>
• Re: [platform-testers] autoconf-2.72e released [release candidate]
  • From: "Zack Weinberg" <zack@xxxxxxxxxxxx>
• Re: autoconf-2.72e released [release candidate]
  • From: Alan Coopersmith <alan.coopersmith@xxxxxxxxxx>
• Re: [platform-testers] autoconf-2.72e released [release candidate]
  • From: Frederic Berat <fberat@xxxxxxxxxx>
• Re: [platform-testers] autoconf-2.72e released [release candidate]
  • From: "Zack Weinberg" <zack@xxxxxxxxxxxx>
• Re: [platform-testers] autoconf-2.72e released [release candidate]
  • From: Frederic Berat <fberat@xxxxxxxxxx>
• autoconf-2.72e released [release candidate]
  • From: Zack Weinberg <zack@xxxxxxxxxxxx>
• Re: AC_FUNC_MMAP not testing what the comments say
  • From: "Zack Weinberg" <zack@xxxxxxxxxxxx>
• Re: AC_FUNC_MMAP not testing what the comments say
  • From: Brooks Davis <brooks@xxxxxxxxxxx>
• Re: AC_FUNC_MMAP not testing what the comments say
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• AC_FUNC_MMAP not testing what the comments say
  • From: Brooks Davis <brooks@xxxxxxxxxxx>
• Re: Will autoconf work with -Werror=implicit-int and -Werror=implicit-function-declaration ?
  • From: "Zack Weinberg" <zack@xxxxxxxxxxxx>
• Re: Will autoconf work with -Werror=implicit-int and -Werror=implicit-function-declaration ?
  • From: Sam James <sam@xxxxxxxxxx>
• Re: Will autoconf work with -Werror=implicit-int and -Werror=implicit-function-declaration ?
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: Will autoconf work with -Werror=implicit-int and -Werror=implicit-function-declaration ?
  • From: Frederic Berat <fberat@xxxxxxxxxx>
• Re: Will autoconf work with -Werror=implicit-int and -Werror=implicit-function-declaration ?
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: Will autoconf work with -Werror=implicit-int and -Werror=implicit-function-declaration ?
  • From: "Zack Weinberg" <zack@xxxxxxxxxxxx>
• Re: Will autoconf work with -Werror=implicit-int and -Werror=implicit-function-declaration ?
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: Yet another license clarification
  • From: Sergey Kosukhin <skosukhin@xxxxxxxxx>
• Re: Yet another license clarification
  • From: Nick Bowler <nbowler@xxxxxxxxxx>
• Re: Yet another license clarification
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Yet another license clarification
  • From: Sergey Kosukhin <skosukhin@xxxxxxxxx>
• Re: Will autoconf work with -Werror=implicit-int and -Werror=implicit-function-declaration ?
  • From: Arsen Arsenović <arsen@xxxxxxxxx>
• Re: Will autoconf work with -Werror=implicit-int and -Werror=implicit-function-declaration ?
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: Will autoconf work with -Werror=implicit-int and -Werror=implicit-function-declaration ?
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: Will autoconf work with -Werror=implicit-int and -Werror=implicit-function-declaration ?
  • From: "Zack Weinberg" <zack@xxxxxxxxxxxx>
• Re: Will autoconf work with -Werror=implicit-int and -Werror=implicit-function-declaration ?
  • From: Michael Orlitzky <michael@xxxxxxxxxxxx>
• Will autoconf work with -Werror=implicit-int and -Werror=implicit-function-declaration ?
  • From: "David A. Wheeler" <dwheeler@xxxxxxxxxxxx>
• Bug triage for 2.72 complete; release freeze begins now
  • From: "Zack Weinberg" <zack@xxxxxxxxxxxx>
• Re: [platform-testers] autoconf-2.72d released [beta]
  • From: Frederic Berat <fberat@xxxxxxxxxx>
• Re: autoconf-2.72d released [beta]
  • From: "Zack Weinberg" <zack@xxxxxxxxxxxx>
• Re: autoconf-2.72d released [beta]
  • From: Richard Purdie <richard.purdie@xxxxxxxxxxxxxxxxxxx>
• New branch zack/ac-prog-lex-rewrite, please test
  • From: "Zack Weinberg" <zack@xxxxxxxxxxxx>
• autoconf-2.72d released [beta]
  • From: "Zack Weinberg" <zack@xxxxxxxxxxxx>
• Re: Evaluating arithmetic expressions with macros (eval)
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: Evaluating arithmetic expressions with macros (eval)
  • From: Peter Hull <peterhull90@xxxxxxxxx>
• Re: Evaluating arithmetic expressions with macros (eval)
  • From: Sébastien Hinderer <Sebastien.Hinderer@xxxxxxxx>
• Re: Evaluating arithmetic expressions with macros (eval)
  • From: Peter Hull <peterhull90@xxxxxxxxx>
• Re: Evaluating arithmetic expressions with macros (eval)
  • From: Sébastien Hinderer <Sebastien.Hinderer@xxxxxxxx>
• Re: How to get autoconf to respect CC="gcc -std=c89"?
  • From: Niels Möller <nisse@xxxxxxxxxxxxxx>
• Re: How to get autoconf to respect CC="gcc -std=c89"?
  • From: "Zack Weinberg" <zack@xxxxxxxxxxxx>
• Re: How to get autoconf to respect CC="gcc -std=c89"?
  • From: Evgeny Grin <k2k@xxxxxxxxx>
• Re: How to get autoconf to respect CC="gcc -std=c89"?
  • From: "Zack Weinberg" <zack@xxxxxxxxxxxx>
• Re: How to get autoconf to respect CC="gcc -std=c89"?
  • From: Evgeny Grin <k2k@xxxxxxxxx>
• Re: How to get autoconf to respect CC="gcc -std=c89"?
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• Re: How to get autoconf to respect CC="gcc -std=c89"?
  • From: Evgeny Grin <k2k@xxxxxxxxx>
• Re: How to get autoconf to respect CC="gcc -std=c89"?
  • From: Niels Möller <nisse@xxxxxxxxxxxxxx>
• Re: How to get autoconf to respect CC="gcc -std=c89"?
  • From: Nick Bowler <nbowler@xxxxxxxxxx>
• Re: How to get autoconf to respect CC="gcc -std=c89"?
  • From: Jacob Bachmeyer <jcb62281@xxxxxxxxx>
• Re: How to get autoconf to respect CC="gcc -std=c89"?
  • From: Niels Möller <nisse@xxxxxxxxxxxxxx>
• Re: How to get autoconf to respect CC="gcc -std=c89"?
  • From: Jacob Bachmeyer <jcb62281@xxxxxxxxx>
• Re: How to get autoconf to respect CC="gcc -std=c89"?
  • From: Evgeny Grin <k2k@xxxxxxxxx>
• Re: How to get autoconf to respect CC="gcc -std=c89"?
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: How to get autoconf to respect CC="gcc -std=c89"?
  • From: Niels Möller <nisse@xxxxxxxxxxxxxx>
• Re: How to get autoconf to respect CC="gcc -std=c89"?
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: How to get autoconf to respect CC="gcc -std=c89"?
  • From: Niels Möller <nisse@xxxxxxxxxxxxxx>
• Re: How to get autoconf to respect CC="gcc -std=c89"?
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• Re: How to get autoconf to respect CC="gcc -std=c89"?
  • From: Niels Möller <nisse@xxxxxxxxxxxxxx>
• Re: How to get autoconf to respect CC="gcc -std=c89"?
  • From: "Zack Weinberg" <zack@xxxxxxxxxxxx>
• How to get autoconf to respect CC="gcc -std=c89"?
  • From: Niels Möller <nisse@xxxxxxxxxxxxxx>
• Re: Evaluating arithmetic expressions with macros (eval)
  • From: Andreas Kähäri <andreas.kahari@xxxxxx>
• Re: Evaluating arithmetic expressions with macros (eval)
  • From: Nick Bowler <nbowler@xxxxxxxxxx>
• Evaluating arithmetic expressions with macros (eval)
  • From: Sébastien Hinderer <Sebastien.Hinderer@xxxxxxxx>
• Re: autoconf documentation for m4_bregexp and m4_bpatsubst
  • From: Luke Mewburn <luke@xxxxxxxxxxx>
• Re: tcc 0.9.28rc testing: bug in autoconf 2.71 with AC_CHECK_DEFINE
  • From: Detlef Riekenberg <wine.dev@xxxxxx>
• Re: tcc 0.9.28rc testing: bug in autoconf 2.71 with AC_CHECK_DEFINE
  • From: Detlef Riekenberg <wine.dev@xxxxxx>
• Re: tcc 0.9.28rc testing: bug in autoconf 2.71 with AC_CHECK_DEFINE
  • From: Nick Bowler <nbowler@xxxxxxxxxx>
• Re: tcc 0.9.28rc testing: bug in autoconf 2.71 with AC_CHECK_DEFINE
  • From: Peter Johansson <trojkan@xxxxxxxxx>
• Re: tcc 0.9.28rc testing: bug in autoconf 2.71 with AC_CHECK_DEFINE
  • From: Nick Bowler <nbowler@xxxxxxxxxx>
• Re: tcc 0.9.28rc testing: bug in autoconf 2.71 with AC_CHECK_DEFINE
  • From: Nick Bowler <nbowler@xxxxxxxxxx>
• tcc 0.9.28rc testing: bug in autoconf 2.71 with AC_CHECK_DEFINE
  • From: Detlef Riekenberg <wine.dev@xxxxxx>
• Re: AC_SYS_LARGEFILE
  • From: Evgeny Grin <k2k@xxxxxxxxx>
• Re: AC_SYS_LARGEFILE
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: AC_SYS_LARGEFILE
  • From: Evgeny Grin <k2k@xxxxxxxxx>
• Re: AC_SYS_LARGEFILE
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: AC_SYS_LARGEFILE
  • From: Sébastien Hinderer <Sebastien.Hinderer@xxxxxxxx>
• Re: AC_SYS_LARGEFILE
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: AC_SYS_LARGEFILE
  • From: Sébastien Hinderer <Sebastien.Hinderer@xxxxxxxxxxxx>
• Re: AC_SYS_LARGEFILE
  • From: Sébastien Hinderer <Sebastien.Hinderer@xxxxxxxxxxxx>
• Re: AC_SYS_LARGEFILE
  • From: Sébastien Hinderer <Sebastien.Hinderer@xxxxxxxx>
• Re: AC_SYS_LARGEFILE
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: AC_SYS_LARGEFILE
  • From: Russ Allbery <eagle@xxxxxxxxx>
• Re: AC_SYS_LARGEFILE
  • From: Nick Bowler <nbowler@xxxxxxxxxx>
• Re: AC_SYS_LARGEFILE
  • From: Sébastien Hinderer <Sebastien.Hinderer@xxxxxxxx>
• Re: AC_SYS_LARGEFILE
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• AC_SYS_LARGEFILE
  • From: Sébastien Hinderer <Sebastien.Hinderer@xxxxxxxxxxxx>
• Re: Option autoconf option --debug no longer working
  • From: Thomas Jahns <jahns@xxxxxxx>
• Re: Option autoconf option --debug no longer working
  • From: Thomas Jahns <jahns@xxxxxxx>
• Re: Option autoconf option --debug no longer working
  • From: Thomas Jahns <jahns@xxxxxxx>
• Re: Option autoconf option --debug no longer working
  • From: Thomas Jahns <jahns@xxxxxxx>
• Re: Option autoconf option --debug no longer working
  • From: Thomas Jahns <jahns@xxxxxxx>
• Option autoconf option --debug no longer working
  • From: Thomas Jahns <jahns@xxxxxxx>
• Re: INSTALL nits
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: INSTALL nits
  • From: Gavin Smith <gavinsmith0123@xxxxxxxxx>
• Re: INSTALL nits
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: INSTALL nits
  • From: Russ Allbery <eagle@xxxxxxxxx>
• Re: INSTALL nits
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: INSTALL nits
  • From: Thomas Jahns <Thomas.Jahns@xxxxxxx>
• Re: INSTALL nits
  • From: Peter Johansson <trojkan@xxxxxxxxx>
• Re: INSTALL nits
  • From: "Zack Weinberg" <zack@xxxxxxxxxxxx>
• Re: INSTALL nits
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• Re: INSTALL nits
  • From: Gavin Smith <gavinsmith0123@xxxxxxxxx>
• Re: INSTALL nits
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: INSTALL nits
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: INSTALL nits
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• INSTALL nits
  • From: Gavin Smith <gavinsmith0123@xxxxxxxxx>
• Re: libtool (use with autotest)
  • From: Simon Sobisch <simonsobisch@xxxxxxx>
• Re: libtool (use with autotest)
  • From: Nick Bowler <nbowler@xxxxxxxxxx>
• libtool (use with autotest)
  • From: Simon Sobisch <simonsobisch@xxxxxxx>
• Re: autoconf documentation for m4_bregexp and m4_bpatsubst
  • From: Luke Mewburn <luke@xxxxxxxxxxx>
• Re: autoconf: 2 testsuite failures on CentOS Stream 8
  • From: Luke Mewburn <luke@xxxxxxxxxxx>
• Re: autoconf documentation for m4_bregexp and m4_bpatsubst
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: autoconf: 2 testsuite failures on CentOS Stream 8
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• autoconf documentation for m4_bregexp and m4_bpatsubst
  • From: Luke Mewburn <luke@xxxxxxxxxxx>
• autoconf: 2 testsuite failures on CentOS Stream 8
  • From: Luke Mewburn <luke@xxxxxxxxxxx>
• "ac_fn_c_try_run" clause not executing.
  • From: alexandre schenberg <ale.schenberg@xxxxxxxxxx>
• Re: AS_ECHO and printf
  • From: Po Lu <luangruo@xxxxxxxxx>
• Re: AS_ECHO and printf
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: AS_ECHO and printf
  • From: "Zack Weinberg" <zack@xxxxxxxxxxxx>
• AS_ECHO and printf
  • From: Po Lu <luangruo@xxxxxxxxx>
• Re: remaining tasks before Autoconf release
  • From: Bruno Haible <bruno@xxxxxxxxx>
• Re: remaining tasks before Autoconf release
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: remaining tasks before Autoconf release
  • From: Bruno Haible <bruno@xxxxxxxxx>
• Re: remaining tasks before Autoconf release
  • From: Jacob Bachmeyer <jcb62281@xxxxxxxxx>
• Re: remaining tasks before Autoconf release
  • From: Bruno Haible <bruno@xxxxxxxxx>
• Re: remaining tasks before Autoconf release
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: remaining tasks before Autoconf release
  • From: Bruno Haible <bruno@xxxxxxxxx>
• Re: remaining tasks before Autoconf release
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: parallelization of ./configure compiler test processes
  • From: madmurphy <madmurphy333@xxxxxxxxx>
• Re: uname -p on Fedora 38
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• uname -p on Fedora 38
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Re: remaining tasks before Autoconf release
  • From: Bruno Haible <bruno@xxxxxxxxx>
• Re: remaining tasks before Autoconf release
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: AC_SYS_LARGEFILE_REQUIRED vs. AC_SYS_YEAR2038_REQUIRED on MSVC
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: remaining tasks before Autoconf release
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: AC_SYS_LARGEFILE_REQUIRED vs. AC_SYS_YEAR2038_REQUIRED on MSVC
  • From: Adhemerval Zanella <adhemerval.zanella@xxxxxxxxxx>
• remaining tasks before Autoconf release
  • From: Bruno Haible <bruno@xxxxxxxxx>
• Re: AC_SYS_LARGEFILE_REQUIRED vs. AC_SYS_YEAR2038_REQUIRED on MSVC
  • From: Bruno Haible <bruno@xxxxxxxxx>
• Re: AC_SYS_LARGEFILE_REQUIRED vs. AC_SYS_YEAR2038_REQUIRED on MSVC
  • From: Bruno Haible <bruno@xxxxxxxxx>
• Re: AC_SYS_LARGEFILE_REQUIRED vs. AC_SYS_YEAR2038_REQUIRED on MSVC
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: AC_SYS_LARGEFILE_REQUIRED vs. AC_SYS_YEAR2038_REQUIRED on MSVC
  • From: Bruno Haible <bruno@xxxxxxxxx>
• Re: AC_SYS_LARGEFILE_REQUIRED vs. AC_SYS_YEAR2038_REQUIRED on MSVC
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: year 2038 support: fix for mingw
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• AC_SYS_LARGEFILE_REQUIRED vs. AC_SYS_YEAR2038_REQUIRED on MSVC
  • From: Bruno Haible <bruno@xxxxxxxxx>
• year 2038 support: fix for mingw
  • From: Bruno Haible <bruno@xxxxxxxxx>
• Re: eval clauses not executing.
  • From: alexandre schenberg <ale.schenberg@xxxxxxxxxx>
• Re: autoconf 2.72/2.73 on RCS
  • From: Frederic Berat <fberat@xxxxxxxxxx>
• Re: autoconf 2.72/2.73 on RCS
  • From: "Zack Weinberg" <zack@xxxxxxxxxxxx>
• Re: autoconf 2.72/2.73 on RCS
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: Anyone remember what AC_PROG_GCC_TRADITIONAL was testing for?
  • From: "Zack Weinberg" <zack@xxxxxxxxxxxx>
• Re: Anyone remember what AC_PROG_GCC_TRADITIONAL was testing for?
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: Anyone remember what AC_PROG_GCC_TRADITIONAL was testing for?
  • From: Alexandre Oliva <oliva@xxxxxxx>
• Re: eval clauses not executing.
  • From: "Zack Weinberg" <zack@xxxxxxxxxxxx>
• eval clauses not executing.
  • From: alexandre schenberg <ale.schenberg@xxxxxxxxxx>
• Anyone remember what AC_PROG_GCC_TRADITIONAL was testing for?
  • From: "Zack Weinberg" <zack@xxxxxxxxxxxx>
• Re: AC_PROG_EGREP and $EGREP_TRADITIONAL and shell conditional statements
  • From: "Zack Weinberg" <zack@xxxxxxxxxxxx>
• Re: AC_PROG_EGREP and $EGREP_TRADITIONAL and shell conditional statements
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: rhel8 test failure confirmation? [PATCH for problem affecting Automake testsuite]
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: AC_PROG_EGREP and $EGREP_TRADITIONAL and shell conditional statements
  • From: Khem Raj <raj.khem@xxxxxxxxx>
• Re: rhel8 test failure confirmation? [PATCH for problem affecting Automake testsuite]
  • From: Jacob Bachmeyer <jcb62281@xxxxxxxxx>
• Re: rhel8 test failure confirmation? [PATCH for problem affecting Automake testsuite]
  • From: Bogdan <bogdro_rep@xxxxxx>
• Re: new snapshot available: autoconf-2.72c
  • From: Richard Purdie <richard.purdie@xxxxxxxxxxxxxxxxxxx>
• Re: [platform-testers] new snapshot available: autoconf-2.72c
  • From: Sam James <sam@xxxxxxxxxx>
• Re: new snapshot available: autoconf-2.72c
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: new snapshot available: autoconf-2.72c
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: Which Perl versions Autoconf needs [PATCH included]
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: AC_PROG_EGREP and $EGREP_TRADITIONAL and shell conditional statements
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: Which Perl versions Autoconf needs [PATCH included]
  • From: Jacob Bachmeyer <jcb62281@xxxxxxxxx>
• Re: Which Perl versions Autoconf needs [PATCH included]
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: parallelization of ./configure compiler test processes
  • From: "Zack Weinberg" <zack@xxxxxxxxxxxx>
• Re: Which Perl versions Autoconf needs [PATCH included]
  • From: Jacob Bachmeyer <jcb62281@xxxxxxxxx>
• Re: Which Perl versions Autoconf needs
  • From: Jacob Bachmeyer <jcb62281@xxxxxxxxx>
• Re: parallelization of ./configure compiler test processes
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• Re: parallelization of ./configure compiler test processes
  • From: Thomas Jahns <jahns@xxxxxxx>
• Re: Which Perl versions Autoconf needs [PATCH included]
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: Which Perl versions Autoconf needs [PATCH included]
  • From: Jacob Bachmeyer <jcb62281@xxxxxxxxx>
• Re: Which Perl versions Autoconf needs
  • From: Gavin Smith <gavinsmith0123@xxxxxxxxx>
• Re: Which Perl versions Autoconf needs [PATCH included]
  • From: Nick Bowler <nbowler@xxxxxxxxxx>
• Re: parallelization of ./configure compiler test processes
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• Re: AC_PROG_EGREP and $EGREP_TRADITIONAL and shell conditional statements
  • From: "Zack Weinberg" <zack@xxxxxxxxxxxx>
• Re: Which Perl versions Autoconf needs
  • From: Warren Young <warren@xxxxxxxxxxx>
• Re: Which Perl versions Autoconf needs [PATCH included]
  • From: "Zack Weinberg" <zack@xxxxxxxxxxxx>
• Re: Which Perl versions Autoconf needs [PATCH included]
  • From: Jacob Bachmeyer <jcb62281@xxxxxxxxx>
• Re: Which Perl versions Autoconf needs
  • From: Jacob Bachmeyer <jcb62281@xxxxxxxxx>
• Which Perl versions Autoconf needs
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: parallelization of ./configure compiler test processes
  • From: Thomas Jahns <jahns@xxxxxxx>
• Re: parallelization of ./configure compiler test processes
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• parallelization of ./configure compiler test processes
  • From: Danny McClanahan <dmcc2@xxxxxxxxxxxxx>
• Re: [bug#61240] [PATCH 2/2] Gracefully degrade if Time::HiRes is not available
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: new snapshot available: autoconf-2.72c
  • From: "Zack Weinberg" <zack@xxxxxxxxxxxx>
• Re: new snapshot available: autoconf-2.72c
  • From: Frederic Berat <fberat@xxxxxxxxxx>
• Re: [bug#61240] [PATCH 2/2] Gracefully degrade if Time::HiRes is not available
  • From: Jacob Bachmeyer <jcb62281@xxxxxxxxx>
• Re: [bug#61240] [PATCH 2/2] Gracefully degrade if Time::HiRes is not available
  • From: Jacob Bachmeyer <jcb62281@xxxxxxxxx>
• Re: [platform-testers] new snapshot available: autoconf-2.72c
  • From: Richard Purdie <richard.purdie@xxxxxxxxxxxxxxxxxxx>
• Re: [platform-testers] new snapshot available: autoconf-2.72c
  • From: Bruno Haible <bruno@xxxxxxxxx>
• Re: new snapshot available: autoconf-2.72c
  • From: Richard Purdie <richard.purdie@xxxxxxxxxxxxxxxxxxx>
• Re: AC_PROG_EGREP and $EGREP_TRADITIONAL and shell conditional statements
  • From: Frederic Berat <fberat@xxxxxxxxxx>
• Re: AC_PROG_EGREP and $EGREP_TRADITIONAL and shell conditional statements
  • From: Nick Bowler <nbowler@xxxxxxxxxx>
• Re: [bug#61240] [PATCH 2/2] Gracefully degrade if Time::HiRes is not available
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: new snapshot available: autoconf-2.72c
  • From: "Zack Weinberg" <zack@xxxxxxxxxxxx>
• AC_PROG_EGREP and $EGREP_TRADITIONAL and shell conditional statements
  • From: "Zack Weinberg" <zack@xxxxxxxxxxxx>
• Re: new snapshot available: autoconf-2.72c
  • From: Frederic Berat <fberat@xxxxxxxxxx>
• Re: new snapshot available: autoconf-2.72c
  • From: Jim Meyering <jim@xxxxxxxxxxxx>
• Re: [bug#61240] [PATCH 2/2] Gracefully degrade if Time::HiRes is not available
  • From: Warren Young <warren@xxxxxxxxxxx>
• Re: new snapshot available: autoconf-2.72c
  • From: Richard Purdie <richard.purdie@xxxxxxxxxxxxxxxxxxx>
• Re: new snapshot available: autoconf-2.72c
  • From: Frederic Berat <fberat@xxxxxxxxxx>
• Re: new snapshot available: autoconf-2.72c
  • From: Richard Purdie <richard.purdie@xxxxxxxxxxxxxxxxxxx>
• Re: new snapshot available: autoconf-2.72c
  • From: Richard Purdie <richard.purdie@xxxxxxxxxxxxxxxxxxx>
• Re: new snapshot available: autoconf-2.72c
  • From: Richard Purdie <richard.purdie@xxxxxxxxxxxxxxxxxxx>
• Re: [bug#61240] [PATCH 2/2] Gracefully degrade if Time::HiRes is not available
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: new snapshot available: autoconf-2.72c
  • From: Jim Meyering <jim@xxxxxxxxxxxx>
• Re: new snapshot available: autoconf-2.72c
  • From: Jim Meyering <jim@xxxxxxxxxxxx>
• Re: new snapshot available: autoconf-2.72c
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: new snapshot available: autoconf-2.72c
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: new snapshot available: autoconf-2.72c
  • From: Václav Haisman <vhaisman@xxxxxxxxx>
• Re: new snapshot available: autoconf-2.72c
  • From: "Zack Weinberg" <zack@xxxxxxxxxxxx>
• Re: new snapshot available: autoconf-2.72c
  • From: "Carlos O'Donell" <carlos@xxxxxxxxxx>
• Re: new snapshot available: autoconf-2.72c
  • From: Sam James <sam@xxxxxxxxxx>
• Re: new snapshot available: autoconf-2.72c
  • From: "Zack Weinberg" <zack@xxxxxxxxxxxx>
• new snapshot available: autoconf-2.72c
  • From: Jim Meyering <jim@xxxxxxxxxxxx>
• snapshot preparations
  • From: Jim Meyering <jim@xxxxxxxxxxxx>
• Re: On time64 and Large File Support
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: On time64 and Large File Support
  • From: Andreas Schwab <schwab@xxxxxxx>
• Re: On time64 and Large File Support
  • From: Arsen Arsenović <arsen@xxxxxxxxxx>
• Re: On time64 and Large File Support
  • From: Daniel P. Berrangé <berrange@xxxxxxxxxx>
• Re: On time64 and Large File Support
  • From: Wookey <wookey@xxxxxxxxxxxx>
• Re: On time64 and Large File Support
  • From: "Richard W.M. Jones" <rjones@xxxxxxxxxx>
• Re: On time64 and Large File Support
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: On time64 and Large File Support
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: On time64 and Large File Support
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: On time64 and Large File Support
  • From: Wookey <wookey@xxxxxxxxxxxx>
• Re: On time64 and Large File Support
  • From: Andreas Schwab <schwab@xxxxxxx>
• Re: On time64 and Large File Support
  • From: "Richard W.M. Jones" <rjones@xxxxxxxxxx>
• Re: On time64 and Large File Support
  • From: Daniel P. Berrangé <berrange@xxxxxxxxxx>
• Re: On time64 and Large File Support
  • From: Daniel P. Berrangé <berrange@xxxxxxxxxx>
• Re: On time64 and Large File Support
  • From: "Richard W.M. Jones" <rjones@xxxxxxxxxx>
• Re: On time64 and Large File Support
  • From: Bruno Haible <bruno@xxxxxxxxx>
• Re: On time64 and Large File Support
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: On time64 and Large File Support
  • From: Demi Marie Obenour <demiobenour@xxxxxxxxx>
• Re: On time64 and Large File Support
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Best-practice for (not?) re-using/caching computed --with options
  • From: Simon Sobisch <simonsobisch@xxxxxxx>
• Re: autoconf, clang static analyser and C++17
  • From: Arsen Arsenović <arsen@xxxxxxxxx>
• autoconf, clang static analyser and C++17
  • From: Peter Hull <peterhull90@xxxxxxxxx>
• How can I make an arbitrary directory of M4 macros available to autoconf?
  • From: Olav Fosse <post@xxxxxxxxxxxx>
• Automatic conditional use of compilers (and how to conditionally use macros which REQUIRE them)
  • From: Diab Jerius <djerius@xxxxxxxxxxxxxxx>
• Re: Conditional AC_CHECK_HEADER
  • From: Sam James <sam@xxxxxxxxxx>
• Re: Conditional AC_CHECK_HEADER
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: Conditional AC_CHECK_HEADER
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: Conditional AC_CHECK_HEADER
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: Conditional AC_CHECK_HEADER
  • From: Russ Allbery <eagle@xxxxxxxxx>
• Re: Conditional AC_CHECK_HEADER
  • From: Sam James <sam@xxxxxxxxxx>
• Conditional AC_CHECK_HEADER
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Patch at sr #110713
  • From: Detlef Riekenberg <wine.dev@xxxxxx>
• Disabling the default linker behaviour of libtool (linking all dependent libraries)
  • From: Годин Алексей Александрович via Discussion list for the autoconf build system <autoconf@xxxxxxx>
• Re: [LTP] [PATCH 2/2] configure.ac: Update AC_PROG_AR related comment
  • From: Richard Palethorpe <rpalethorpe@xxxxxxx>
• Re: [LTP] [PATCH 2/2] configure.ac: Update AC_PROG_AR related comment
  • From: Petr Vorel <pvorel@xxxxxxx>
• Re: [LTP] [PATCH 2/2] configure.ac: Update AC_PROG_AR related comment
  • From: Zack Weinberg <zack@xxxxxxxxxxxx>
• Re: [PATCH] fix AC_CHECK_HEADER_STDBOOL regression
  • From: Sam James <sam@xxxxxxxxxx>
• Re: [PATCH] fix AC_CHECK_HEADER_STDBOOL regression
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• [PATCH] fix AC_CHECK_HEADER_STDBOOL regression
  • From: "Todd C. Miller" <Todd.Miller@xxxxxxx>
• Re: [PATCH] AC_HEADER_MAJOR: Probe <sys/sysmacros.h> first
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: [PATCH] AC_HEADER_MAJOR: Probe <sys/sysmacros.h> first
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: [PATCH] AC_HEADER_MAJOR: Probe <sys/sysmacros.h> first
  • From: "Zack Weinberg" <zack@xxxxxxxxxxxx>
• Re: Possible regressions with trunk autoconf (vs 2.71)
  • From: Frederic Berat <fberat@xxxxxxxxxx>
• [PATCH] AC_HEADER_MAJOR: Probe <sys/sysmacros.h> first
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: Possible regressions with trunk autoconf (vs 2.71)
  • From: Frederic Berat <fberat@xxxxxxxxxx>
• Re: Possible regressions with trunk autoconf (vs 2.71)
  • From: Frederic Berat <fberat@xxxxxxxxxx>
• Re: Possible regressions with trunk autoconf (vs 2.71)
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• Re: Possible regressions with trunk autoconf (vs 2.71)
  • From: Nick Bowler <nbowler@xxxxxxxxxx>
• Re: Possible regressions with trunk autoconf (vs 2.71)
  • From: Sam James <sam@xxxxxxxxxx>
• Re: Possible regressions with trunk autoconf (vs 2.71)
  • From: Frederic Berat <fberat@xxxxxxxxxx>
• Re: Possible regressions with trunk autoconf (vs 2.71)
  • From: Frederic Berat <fberat@xxxxxxxxxx>
• Re: Possible regressions with trunk autoconf (vs 2.71)
  • From: Frederic Berat <fberat@xxxxxxxxxx>
• Re: How can Autoconf help with the transition to stricter compilation defaults?
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: How can Autoconf help with the transition to stricter compilation defaults?
  • From: Bruno Haible <bruno@xxxxxxxxx>
• Re: How can Autoconf help with the transition to stricter compilation defaults?
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: How can Autoconf help with the transition to stricter compilation defaults?
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: Possible regressions with trunk autoconf (vs 2.71)
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: Possible regressions with trunk autoconf (vs 2.71)
  • From: Zack Weinberg <zack@xxxxxxxxxxxx>
• Re: Possible regressions with trunk autoconf (vs 2.71)
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: Possible regressions with trunk autoconf (vs 2.71)
  • From: "Zack Weinberg" <zack@xxxxxxxxxxxx>
• Re: How can Autoconf help with the transition to stricter compilation defaults?
  • From: Jason Merrill <jason@xxxxxxxxxx>
• Re: How can Autoconf help with the transition to stricter compilation defaults?
  • From: Michael Matz <matz@xxxxxxx>
• Re: Possible regressions with trunk autoconf (vs 2.71)
  • From: Frederic Berat <fberat@xxxxxxxxxx>
• Re: How can Autoconf help with the transition to stricter compilation defaults?
  • From: "Zack Weinberg" <zack@xxxxxxxxxxxx>
• Re: How can Autoconf help with the transition to stricter compilation defaults?
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Re: Possible regressions with trunk autoconf (vs 2.71)
  • From: "Zack Weinberg" <zack@xxxxxxxxxxxx>
• AC_CHECK_HEADER_STDBOOL regression with trunk autoconf
  • From: "Todd C. Miller" <Todd.Miller@xxxxxxxxxxx>
• Re: How can Autoconf help with the transition to stricter compilation defaults?
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: Possible regressions with trunk autoconf (vs 2.71)
  • From: Frederic Berat <fberat@xxxxxxxxxx>
• Re: How can Autoconf help with the transition to stricter compilation defaults?
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: How can Autoconf help with the transition to stricter compilation defaults?
  • From: Michael Matz <matz@xxxxxxx>
• Re: How can Autoconf help with the transition to stricter compilation defaults?
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Possible regressions with trunk autoconf (vs 2.71)
  • From: Arsen Arsenović <arsen@xxxxxxxxx>
• Re: How can Autoconf help with the transition to stricter compilation defaults?
  • From: Michael Matz <matz@xxxxxxx>
• Re: Possible regressions with trunk autoconf (vs 2.71)
  • From: Frederic Berat <fberat@xxxxxxxxxx>
• Re: How can Autoconf help with the transition to stricter compilation defaults?
  • From: Sam James <sam@xxxxxxxxxx>
• Re: How can Autoconf help with the transition to stricter compilation defaults?
  • From: Richard Biener <richard.guenther@xxxxxxxxx>
• Re: Possible regressions with trunk autoconf (vs 2.71)
  • From: Sam James <sam@xxxxxxxxxx>
• Re: Possible regressions with trunk autoconf (vs 2.71)
  • From: Sam James <sam@xxxxxxxxxx>
• Re: How can Autoconf help with the transition to stricter compilation defaults?
  • From: Michael Matz <matz@xxxxxxx>
• Re: How can Autoconf help with the transition to stricter compilation defaults?
  • From: Michael Matz <matz@xxxxxxx>
• Re: How can Autoconf help with the transition to stricter compilation defaults?
  • From: Alexander Monakov <amonakov@xxxxxxxxx>
• Re: Possible regressions with trunk autoconf (vs 2.71)
  • From: Frederic Berat <fberat@xxxxxxxxxx>
• Re: Possible regressions with trunk autoconf (vs 2.71)
  • From: Frederic Berat <fberat@xxxxxxxxxx>
• Possible regressions with trunk autoconf (vs 2.71)
  • From: Frederic Berat <fberat@xxxxxxxxxx>
• Re: How can Autoconf help with the transition to stricter compilation defaults?
  • From: Ben Boeckel <ben.boeckel@xxxxxxxxxxx>
• Re: How can Autoconf help with the transition to stricter compilation defaults?
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• Re: How can Autoconf help with the transition to stricter compilation defaults?
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: How can Autoconf help with the transition to stricter compilation defaults?
  • From: Aaron Ballman <aaron@xxxxxxxxxxxxxxxx>
• Re: How can Autoconf help with the transition to stricter compilation defaults?
  • From: Aaron Ballman <aaron@xxxxxxxxxxxxxxxx>
• Re: How can Autoconf help with the transition to stricter compilation defaults?
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: How can Autoconf help with the transition to stricter compilation defaults?
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: How can Autoconf help with the transition to stricter compilation defaults?
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: How can Autoconf help with the transition to stricter compilation defaults?
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: How can Autoconf help with the transition to stricter compilation defaults?
  • From: Sam James <sam@xxxxxxxxxx>
• Re: How can Autoconf help with the transition to stricter compilation defaults?
  • From: "Zack Weinberg" <zack@xxxxxxxxxxxx>
• Re: On time64 and Large File Support
  • From: Arsen Arsenović <arsen@xxxxxxxxx>
• Re: On time64 and Large File Support
  • From: Sam James <sam@xxxxxxxxxx>
• Re: How can Autoconf help with the transition to stricter compilation defaults?
  • From: Sam James <sam@xxxxxxxxxx>
• Re: On time64 and Large File Support
  • From: Adam Sampson <ats@xxxxxxxxx>
• Re: On time64 and Large File Support
  • From: Arsen Arsenović <arsen@xxxxxxxxx>
• Re: How can Autoconf help with the transition to stricter compilation defaults?
  • From: Aaron Ballman <aaron@xxxxxxxxxxxxxxxx>
• Re: How can Autoconf help with the transition to stricter compilation defaults?
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: On time64 and Large File Support
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: On time64 and Large File Support
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: How can Autoconf help with the transition to stricter compilation defaults?
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: How can Autoconf help with the transition to stricter compilation defaults?
  • From: Aaron Ballman <aaron@xxxxxxxxxxxxxxxx>
• Re: How can Autoconf help with the transition to stricter compilation defaults?
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: How can Autoconf help with the transition to stricter compilation defaults?
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: How can Autoconf help with the transition to stricter compilation defaults?
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: How can Autoconf help with the transition to stricter compilation defaults?
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: On time64 and Large File Support
  • From: "Zack Weinberg" <zack@xxxxxxxxxxxx>
• Re: On time64 and Large File Support
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: On time64 and Large File Support
  • From: Russ Allbery <eagle@xxxxxxxxx>
• Re: On time64 and Large File Support
  • From: Wookey <wookey@xxxxxxxxxxxx>
• Re: On time64 and Large File Support
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: On time64 and Large File Support
  • From: Bruno Haible <bruno@xxxxxxxxx>
• Re: On time64 and Large File Support
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: On time64 and Large File Support
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: On time64 and Large File Support
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: How can Autoconf help with the transition to stricter compilation defaults?
  • From: Zack Weinberg <zack@xxxxxxxxxxxx>
• Re: How can Autoconf help with the transition to stricter compilation defaults?
  • From: Wookey <wookey@xxxxxxxxxxxx>
• Re: How can Autoconf help with the transition to stricter compilation defaults?
  • From: Zack Weinberg <zack@xxxxxxxxxxxx>
• Re: How can Autoconf help with the transition to stricter compilation defaults?
  • From: Zack Weinberg <zack@xxxxxxxxxxxx>
• Re: On time64 and Large File Support
  • From: Zack Weinberg <zack@xxxxxxxxxxxx>
• Re: How can Autoconf help with the transition to stricter compilation defaults?
  • From: Zack Weinberg <zack@xxxxxxxxxxxx>
• Re: On time64 and Large File Support
  • From: Sam James <sam@xxxxxxxxxx>
• Re: On time64 and Large File Support
  • From: Wookey <wookey@xxxxxxxxxxxx>
• Re: On time64 and Large File Support
  • From: Sam James <sam@xxxxxxxxxx>
• Re: On time64 and Large File Support
  • From: Wookey <wookey@xxxxxxxxxxxx>
• Re: How can Autoconf help with the transition to stricter compilation defaults?
  • From: Sam James <sam@xxxxxxxxxx>
• Re: On time64 and Large File Support
  • From: Sam James <sam@xxxxxxxxxx>
• Re: How can Autoconf help with the transition to stricter compilation defaults?
  • From: Zack Weinberg <zack@xxxxxxxxxxxx>
• Re: How can Autoconf help with the transition to stricter compilation defaults?
  • From: Joseph Myers <joseph@xxxxxxxxxxxxxxxx>
• Re: How can Autoconf help with the transition to stricter compilation defaults?
  • From: Sam James <sam@xxxxxxxxxx>
• Re: How can Autoconf help with the transition to stricter compilation defaults?
  • From: Zack Weinberg <zack@xxxxxxxxxxxx>
• Re: How can Autoconf help with the transition to stricter compilation defaults?
  • From: Zack Weinberg <zack@xxxxxxxxxxxx>
• Re: How can Autoconf help with the transition to stricter compilation defaults?
  • From: Zack Weinberg <zack@xxxxxxxxxxxx>
• Re: How can Autoconf help with the transition to stricter compilation defaults?
  • From: Demi Marie Obenour <demiobenour@xxxxxxxxx>
• Re: On time64 and Large File Support
  • From: Zack Weinberg <zack@xxxxxxxxxxxx>
• Re: How can Autoconf help with the transition to stricter compilation defaults?
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: On time64 and Large File Support
  • From: Joseph Myers <joseph@xxxxxxxxxxxxxxxx>
• Re: How can Autoconf help with the transition to stricter compilation defaults?
  • From: Sam James <sam@xxxxxxxxxx>
• Re: On time64 and Large File Support
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: On time64 and Large File Support
  • From: Palmer Dabbelt <palmer@xxxxxxxxxxx>
• Re: On time64 and Large File Support
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: On time64 and Large File Support
  • From: "Andreas K. Huettel" <dilfridge@xxxxxxxxxx>
• Re: How can Autoconf help with the transition to stricter compilation defaults?
  • From: Aaron Ballman <aaron@xxxxxxxxxxxxxxxx>
• Re: On time64 and Large File Support
  • From: "Andreas K. Huettel" <dilfridge@xxxxxxxxxx>
• Re: On time64 and Large File Support
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: On time64 and Large File Support
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: On time64 and Large File Support
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: On time64 and Large File Support
  • From: Richard Purdie <richard.purdie@xxxxxxxxxxxxxxxxxxx>
• Re: On time64 and Large File Support
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: On time64 and Large File Support
  • From: Sam James <sam@xxxxxxxxxx>
• Re: On time64 and Large File Support
  • From: Sam James <sam@xxxxxxxxxx>
• Re: On time64 and Large File Support
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: On time64 and Large File Support
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: How can Autoconf help with the transition to stricter compilation defaults?
  • From: Sam James <sam@xxxxxxxxxx>
• Re: How can Autoconf help with the transition to stricter compilation defaults?
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: How can Autoconf help with the transition to stricter compilation defaults?
  • From: Sam James <sam@xxxxxxxxxx>
• On time64 and Large File Support
  • From: Sam James <sam@xxxxxxxxxx>
• Re: How can Autoconf help with the transition to stricter compilation defaults?
  • From: "Zack Weinberg" <zack@xxxxxxxxxxxx>
• Re: How can Autoconf help with the transition to stricter compilation defaults?
  • From: Sam James <sam@xxxxxxxxxx>
• Re: How can Autoconf help with the transition to stricter compilation defaults?
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: How can Autoconf help with the transition to stricter compilation defaults?
  • From: Michael Orlitzky <michael@xxxxxxxxxxxx>
• Re: How can Autoconf help with the transition to stricter compilation defaults?
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: How can Autoconf help with the transition to stricter compilation defaults?
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: How can Autoconf help with the transition to stricter compilation defaults?
  • From: Aaron Ballman <aaron@xxxxxxxxxxxxxxxx>
• Re: How can Autoconf help with the transition to stricter compilation defaults?
  • From: Rich Felker <dalias@xxxxxxxx>
• Re: How can Autoconf help with the transition to stricter compilation defaults?
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: How can Autoconf help with the transition to stricter compilation defaults?
  • From: Aaron Ballman <aaron@xxxxxxxxxxxxxxxx>
• Re: How can Autoconf help with the transition to stricter compilation defaults?
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: How can Autoconf help with the transition to stricter compilation defaults?
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• Re: How can Autoconf help with the transition to stricter compilation defaults?
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: How can Autoconf help with the transition to stricter compilation defaults?
  • From: Nick Bowler <nbowler@xxxxxxxxxx>
• How can Autoconf help with the transition to stricter compilation defaults?
  • From: "Zack Weinberg" <zack@xxxxxxxxxxxx>
• Re: [cfarm-users] Missing "make" on gcc210 or gcc211.fsffrance.org / or wrong autoconf - thank you very much
  • From: "Jaroslav Fojtik" <Jafojtik@xxxxxxxxxx>
• Re: [cfarm-users] Missing "make" on gcc210 or gcc211.fsffrance.org / or wrong autoconf - any idea?
  • From: Peter Gutmann <pgut001@xxxxxxxxxxxxxxxxx>
• Re: [cfarm-users] Missing "make" on gcc210 or gcc211.fsffrance.org / or wrong autoconf - any idea?
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: Dependency tracking not working on macOS
  • From: Paul Smith <psmith@xxxxxxx>
• Re: Dependency tracking not working on macOS
  • From: Christoph Grüninger <foss@xxxxxxxxxxxxx>
• Re: [Autoconf] Re: Dependency tracking not working on macOS
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: Dependency tracking not working on macOS
  • From: Paul Smith <psmith@xxxxxxx>
• Re: Dependency tracking not working on macOS
  • From: "David A. Wheeler" <dwheeler@xxxxxxxxxxxx>
• Re: [Autoconf] Re: Dependency tracking not working on macOS
  • From: Paul Smith <psmith@xxxxxxx>
• Re: Dependency tracking not working on macOS
  • From: Paul Smith <psmith@xxxxxxx>
• Re: [Autoconf] Re: Dependency tracking not working on macOS
  • From: suzuki toshiya <mpsuzuki@xxxxxxxxxxxxxxxxx>
• Re: Dependency tracking not working on macOS
  • From: Christoph Grüninger <pr@xxxxxxxxxxxxx>
• Re: Dependency tracking not working on macOS
  • From: Christoph Grüninger <foss@xxxxxxxxxxxxx>
• Re: Dependency tracking not working on macOS
  • From: "Zack Weinberg" <zack@xxxxxxxxxxxx>
• Re: Dependency tracking not working on macOS
  • From: Christoph Grüninger <foss@xxxxxxxxxxxxx>
• Re: Dependency tracking not working on macOS
  • From: "Zack Weinberg" <zack@xxxxxxxxxxxx>
• Re: Dependency tracking not working on macOS
  • From: Christoph Grüninger <foss@xxxxxxxxxxxxx>
• Re: [Autoconf] Re: Dependency tracking not working on macOS
  • From: suzuki toshiya <mpsuzuki@xxxxxxxxxxxxxxxxx>
• Re: [Autoconf] Re: Dependency tracking not working on macOS
  • From: Paul Smith <psmith@xxxxxxx>
• Re: [Autoconf] Re: Dependency tracking not working on macOS
  • From: suzuki toshiya <mpsuzuki@xxxxxxxxxxxxxxxxx>
• Re: Dependency tracking not working on macOS
  • From: Werner LEMBERG <wl@xxxxxxx>
• Re: Dependency tracking not working on macOS
  • From: Paul Smith <psmith@xxxxxxx>
• Re: Dependency tracking not working on macOS
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: Dependency tracking not working on macOS
  • From: Christoph Grüninger <foss@xxxxxxxxxxxxx>
• Re: Dependency tracking not working on macOS
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: Dependency tracking not working on macOS
  • From: Christoph Grüninger <foss@xxxxxxxxxxxxx>
• Re: Dependency tracking not working on macOS
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: Dependency tracking not working on macOS
  • From: Christoph Grüninger <foss@xxxxxxxxxxxxx>
• Re: Dependency tracking not working on macOS
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: Dependency tracking not working on macOS
  • From: Paul Smith <psmith@xxxxxxx>
• Re: Dependency tracking not working on macOS
  • From: "Zack Weinberg" <zack@xxxxxxxxxxxx>
• Re: Dependency tracking not working on macOS
  • From: Paul Smith <psmith@xxxxxxx>
• Dependency tracking not working on macOS
  • From: Christoph Grüninger <pr@xxxxxxxxxxxxx>
• Re: Bash 5.2 SHLVL change and autoconf test failures
  • From: "Zack Weinberg" <zack@xxxxxxxxxxxx>
• Re: Bash 5.2 SHLVL change and autoconf test failures
  • From: Chet Ramey <chet.ramey@xxxxxxxx>
• Re: Bash 5.2 SHLVL change and autoconf test failures
  • From: Xi Ruoyao <xry111@xxxxxxxxxxx>
• Re: Bash 5.2 SHLVL change and autoconf test failures
  • From: Chet Ramey <chet.ramey@xxxxxxxx>
• Bash 5.2 SHLVL change and autoconf test failures
  • From: Xi Ruoyao <xry111@xxxxxxxxxxx>