Gnu Autoconf

• Thread Index

• 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>
• 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>