Gnu Autoconf

• Thread Index

• Re: Warning category skew between Autoconf and Automake - workaround in autoreconf?
  • From: Zack Weinberg <zackw@xxxxxxxxx>
• Re: Warning category skew between Autoconf and Automake - workaround in autoreconf?
  • From: Karl Berry <karl@xxxxxxxxxxxxxxx>
• Re: Warning category skew between Autoconf and Automake - workaround in autoreconf?
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: Warning category skew between Autoconf and Automake - workaround in autoreconf?
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• Warning category skew between Autoconf and Automake - workaround in autoreconf?
  • From: Zack Weinberg <zackw@xxxxxxxxx>
• Re: [PATCH v2] Ensure standard file descriptors are open on start
  • From: Nick Bowler <nbowler@xxxxxxxxxx>
• Re: [PATCH v2] Ensure standard file descriptors are open on start
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: [PATCH v2] Ensure standard file descriptors are open on start
  • From: Zack Weinberg <zackw@xxxxxxxxx>
• Re: Exactly when does autoconf enter cross-compilation mode?
  • From: Nick Bowler <nbowler@xxxxxxxxxx>
• Re: Exactly when does autoconf enter cross-compilation mode?
  • From: wferi@xxxxxxx
• Re: Exactly when does autoconf enter cross-compilation mode?
  • From: Nick Bowler <nbowler@xxxxxxxxxx>
• Exactly when does autoconf enter cross-compilation mode?
  • From: wferi@xxxxxxx
• Re: autoconf-2.69b released [beta]
  • From: Joshua Branson via Discussion list for the autoconf build system <autoconf@xxxxxxx>
• Re: autoconf-2.69b released [beta]
  • From: John Calcote <john.calcote@xxxxxxxxx>
• Re: autoconf-2.69b released [beta]
  • From: Joshua Branson via Discussion list for the autoconf build system <autoconf@xxxxxxx>
• Re: Knowing which tool is being run, from M4
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Knowing which tool is being run, from M4
  • From: Zack Weinberg <zackw@xxxxxxxxx>
• Re: Who's the upstream owner of GNUmakefile?
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: Who's the upstream owner of GNUmakefile?
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: Who's the upstream owner of GNUmakefile?
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Who's the upstream owner of GNUmakefile?
  • From: Zack Weinberg <zackw@xxxxxxxxx>
• Re: feedback on 2.69b
  • From: Zack Weinberg <zackw@xxxxxxxxx>
• Re: Autoconf bug reports gone missing?
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• Re: Autoconf bug reports gone missing?
  • From: Zack Weinberg <zackw@xxxxxxxxx>
• Autoconf bug reports gone missing?
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• Re: feedback on 2.69b
  • From: Peter Eisentraut <peter@xxxxxxxxxxxxxx>
• Re: feedback on 2.69b
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• Re: feedback on 2.69b
  • From: Zack Weinberg <zackw@xxxxxxxxx>
• feedback on 2.69b
  • From: Peter Eisentraut <peter@xxxxxxxxxxxxxx>
• CI for Autoconf (was Re: [PATCH] Revert 'Fix logic error in ...)
  • From: Zack Weinberg <zackw@xxxxxxxxx>
• Re: autoconf-2.69b released [beta]
  • From: Zack Weinberg <zackw@xxxxxxxxx>
• Re: autoconf-2.69b released [beta]
  • From: Dagobert Michelsen <dagobert@xxxxxxxxxxxxxxxxxxxx>
• autoconf-2.69b released [beta]
  • From: zackw@xxxxxxxxx (Zack Weinberg)
• Re: Please help wordsmith NEWS entry warning about AC_REQUIRE inside shell conditional
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Please help wordsmith NEWS entry warning about AC_REQUIRE inside shell conditional
  • From: Zack Weinberg <zackw@xxxxxxxxx>
• Re: [PATCH] bug fixes for AS_IF and _AC_LANG_COMPILER_GNU
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: Any chance to make a new autoconf release?
  • From: Luke Mewburn <lukem@xxxxxxxxxx>
• Re: testsuite could basename the "Generated from"
  • From: Luke Mewburn <lukem@xxxxxxxxxx>
• Re: Any chance to make a new autoconf release?
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: Patches waiting for review
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Patches waiting for review
  • From: Zack Weinberg <zackw@xxxxxxxxx>
• Re: Using @bindir@ etc. in C headers
  • From: Peter Johansson <trojkan@xxxxxxxxx>
• Re: Using @bindir@ etc. in C headers
  • From: Hans Ulrich Niedermann <hun@xxxxxxxxxxxxxxxx>
• Re: Check for experimental/unordered_set and experimental/unordered_map
  • From: Sergio Belkin <sebelk@xxxxxxxxx>
• Re: Using @bindir@ etc. in C headers
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Check for experimental/unordered_set and experimental/unordered_map
  • From: Sergio Belkin <sebelk@xxxxxxxxx>
• Re: Using @bindir@ etc. in C headers
  • From: pluto@xxxxxxxxxxxxxxx (Perry Hutchison)
• Re: Using @bindir@ etc. in C headers
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: Using @bindir@ etc. in C headers
  • From: pluto@xxxxxxxxxxxxxxx (Perry Hutchison)
• Re: Using @bindir@ etc. in C headers
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: Using @bindir@ etc. in C headers
  • From: Nick Bowler <nbowler@xxxxxxxxxx>
• Re: Using @bindir@ etc. in C headers
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: Using @bindir@ etc. in C headers
  • From: Nick Bowler <nbowler@xxxxxxxxxx>
• Re: Using @bindir@ etc. in C headers
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: Using @bindir@ etc. in C headers
  • From: Michael Orlitzky <michael@xxxxxxxxxxxx>
• Re: Using @bindir@ etc. in C headers
  • From: Peter Johansson <trojkan@xxxxxxxxx>
• Using @bindir@ etc. in C headers
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Multiple arguments to CONFIG_SITE
  • From: Ross Burton <ross.burton@xxxxxxxxx>
• My experience with autoconf master
  • From: Ross Burton <ross.burton@xxxxxxxxx>
• Re: New failures with autoconf master
  • From: Zack Weinberg <zackw@xxxxxxxxx>
• Re: Making Autoconf 2.70 happen in the near future
  • From: Zack Weinberg <zackw@xxxxxxxxx>
• Re: Making Autoconf 2.70 happen in the near future
  • From: Marko Lindqvist <cazfi74@xxxxxxxxx>
• Re: Making Autoconf 2.70 happen in the near future
  • From: NightStrike <nightstrike@xxxxxxxxx>
• Re: Making Autoconf 2.70 happen in the near future
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: M4sh tests 77 and 78 vs /bin/sh -> dash
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• Re: Making Autoconf 2.70 happen in the near future
  • From: Zack Weinberg <zackw@xxxxxxxxx>
• Re: M4sh tests 77 and 78 vs /bin/sh -> dash
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: M4sh tests 77 and 78 vs /bin/sh -> dash
  • From: Zack Weinberg <zackw@xxxxxxxxx>
• Re: M4sh tests 77 and 78 vs /bin/sh -> dash
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• Re: M4sh tests 77 and 78 vs /bin/sh -> dash
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Should AM_PROG_CC call AM_PROG_CPP?
  • From: Ross Burton <ross.burton@xxxxxxxxx>
• Re: M4sh tests 77 and 78 vs /bin/sh -> dash
  • From: Zack Weinberg <zackw@xxxxxxxxx>
• Re: M4sh tests 77 and 78 vs /bin/sh -> dash
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: What's the right way to put `dnl' in the body of AT_CONFIGURE_AC text?
  • From: Zack Weinberg <zackw@xxxxxxxxx>
• What's the right way to put `dnl' in the body of AT_CONFIGURE_AC text?
  • From: Zack Weinberg <zackw@xxxxxxxxx>
• Re: New failures with autoconf master
  • From: Nick Bowler <nbowler@xxxxxxxxxx>
• Re: New failures with autoconf master
  • From: Nick Bowler <nbowler@xxxxxxxxxx>
• Re: New failures with autoconf master
  • From: Ross Burton <ross.burton@xxxxxxxxx>
• Re: New failures with autoconf master
  • From: Zack Weinberg <zackw@xxxxxxxxx>
• New failures with autoconf master
  • From: Ross Burton <ross.burton@xxxxxxxxx>
• Re: autoconf git and no host help2man
  • From: Ross Burton <ross.burton@xxxxxxxxx>
• Re: autoconf git and no host help2man
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: debugging autoconf tests (was: gl_CACHE_VAL_SILENT)
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• [PATCH] bug fixes for AS_IF and _AC_LANG_COMPILER_GNU
  • From: "Jannick" <thirdedition@xxxxxxx>
• Re: debugging autoconf tests (was: gl_CACHE_VAL_SILENT)
  • From: Zack Weinberg <zackw@xxxxxxxxx>
• Re: autoconf git and no host help2man
  • From: Ross Burton <ross.burton@xxxxxxxxx>
• Re: debugging autoconf tests (was: gl_CACHE_VAL_SILENT)
  • From: Bruno Haible <bruno@xxxxxxxxx>
• Re: M4sh tests 77 and 78 vs /bin/sh -> dash
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: gl_CACHE_VAL_SILENT won't work correctly with upcoming autoconf 2.70
  • From: Nick Bowler <nbowler@xxxxxxxxxx>
• Re: gl_CACHE_VAL_SILENT won't work correctly with upcoming autoconf 2.70
  • From: Zack Weinberg <zackw@xxxxxxxxx>
• Re: autoconf git and no host help2man
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• autoconf git and no host help2man
  • From: Ross Burton <ross.burton@xxxxxxxxx>
• Re: gl_CACHE_VAL_SILENT won't work correctly with upcoming autoconf 2.70
  • From: Bruno Haible <bruno@xxxxxxxxx>
• Re: gl_CACHE_VAL_SILENT won't work correctly with upcoming autoconf 2.70
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: gl_CACHE_VAL_SILENT won't work correctly with upcoming autoconf 2.70
  • From: Nick Bowler <nbowler@xxxxxxxxxx>
• Re: gl_CACHE_VAL_SILENT won't work correctly with upcoming autoconf 2.70
  • From: Bruno Haible <bruno@xxxxxxxxx>
• Re: Making Autoconf 2.70 happen in the near future
  • From: Zack Weinberg <zackw@xxxxxxxxx>
• Re: Making Autoconf 2.70 happen in the near future
  • From: Bruno Haible <bruno@xxxxxxxxx>
• Re: M4sh tests 77 and 78 vs /bin/sh -> dash
  • From: Sébastien Hinderer <Sebastien.Hinderer@xxxxxxxx>
• Re: M4sh tests 77 and 78 vs /bin/sh -> dash
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• Re: M4sh tests 77 and 78 vs /bin/sh -> dash
  • From: Michael Orlitzky <michael@xxxxxxxxxxxx>
• Re: M4sh tests 77 and 78 vs /bin/sh -> dash
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• Re: M4sh tests 77 and 78 vs /bin/sh -> dash
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• Re: M4sh tests 77 and 78 vs /bin/sh -> dash
  • From: Sébastien Hinderer <Sebastien.Hinderer@xxxxxxxx>
• Re: M4sh tests 77 and 78 vs /bin/sh -> dash
  • From: Zack Weinberg <zackw@xxxxxxxxx>
• Re: M4sh tests 77 and 78 vs /bin/sh -> dash
  • From: Zack Weinberg <zackw@xxxxxxxxx>
• Re: M4sh tests 77 and 78 vs /bin/sh -> dash
  • From: Zack Weinberg <zackw@xxxxxxxxx>
• Re: M4sh tests 77 and 78 vs /bin/sh -> dash
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: M4sh tests 77 and 78 vs /bin/sh -> dash
  • From: Michael Orlitzky <michael@xxxxxxxxxxxx>
• Re: M4sh tests 77 and 78 vs /bin/sh -> dash
  • From: "Andrew W. Nosenko" <andrew.w.nosenko@xxxxxxxxx>
• Re: M4sh tests 77 and 78 vs /bin/sh -> dash
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• Re: M4sh tests 77 and 78 vs /bin/sh -> dash
  • From: Zack Weinberg <zackw@xxxxxxxxx>
• Re: M4sh tests 77 and 78 vs /bin/sh -> dash
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• M4sh tests 77 and 78 vs /bin/sh -> dash
  • From: Zack Weinberg <zackw@xxxxxxxxx>
• Re: Making Autoconf 2.70 happen in the near future
  • From: Michael Orlitzky <michael@xxxxxxxxxxxx>
• Re: Making Autoconf 2.70 happen in the near future
  • From: Zack Weinberg <zackw@xxxxxxxxx>
• Re: Making Autoconf 2.70 happen in the near future
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• Re: Making Autoconf 2.70 happen in the near future
  • From: NightStrike <nightstrike@xxxxxxxxx>
• Re: Making Autoconf 2.70 happen in the near future
  • From: Zack Weinberg <zackw@xxxxxxxxx>
• Re: Making Autoconf 2.70 happen in the near future
  • From: Zack Weinberg <zackw@xxxxxxxxx>
• Re: Making Autoconf 2.70 happen in the near future
  • From: Werner LEMBERG <wl@xxxxxxx>
• Re: Making Autoconf 2.70 happen in the near future
  • From: Michael Orlitzky <michael@xxxxxxxxxxxx>
• Re: Making Autoconf 2.70 happen in the near future
  • From: Per Bothner <per@xxxxxxxxxxx>
• Re: Making Autoconf 2.70 happen in the near future
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• Re: Making Autoconf 2.70 happen in the near future
  • From: Nicholas Clark <nicholas.clark@xxxxxxxxx>
• Making Autoconf 2.70 happen in the near future
  • From: Zack Weinberg <zackw@xxxxxxxxx>
• Re: Android and iOS triplets are not recognized
  • From: Joseph Myers <joseph@xxxxxxxxxxxxxxxx>
• Re: Android and iOS triplets are not recognized
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• Android and iOS triplets are not recognized
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Re: Is commit 2ca0d57 broken out of the box?
  • From: Zack Weinberg <zackw@xxxxxxxxx>
• Re: [PATCH] Fix `make syntax-check'.
  • From: Zack Weinberg <zackw@xxxxxxxxx>
• Re: [PATCH] Fix `make syntax-check'.
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• [PATCH] Fix `make syntax-check'.
  • From: Zack Weinberg <zackw@xxxxxxxxx>
• Re: Is commit 2ca0d57 broken out of the box?
  • From: Tadeus Prastowo <0x66726565@xxxxxxxxx>
• Re: Is commit 2ca0d57 broken out of the box?
  • From: Zack Weinberg <zackw@xxxxxxxxx>
• Is commit 2ca0d57 broken out of the box?
  • From: Tadeus Prastowo <0x66726565@xxxxxxxxx>
• Re: Commit 2ca0d57 breaks automake t/autohdr4.sh and t/autohdr-subdir-pr12495.sh
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: Commit 2ca0d57 breaks automake t/autohdr4.sh and t/autohdr-subdir-pr12495.sh
  • From: Tadeus Prastowo <0x66726565@xxxxxxxxx>
• Re: Commit 2ca0d57 breaks automake t/autohdr4.sh and t/autohdr-subdir-pr12495.sh
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Commit 2ca0d57 breaks automake t/autohdr4.sh and t/autohdr-subdir-pr12495.sh
  • From: Tadeus Prastowo <0x66726565@xxxxxxxxx>
• Re: Any plan to handle Bash 5.0 BASH_ARGC & BASH_ARGV?
  • From: Tadeus Prastowo <0x66726565@xxxxxxxxx>
• Re: Any plan to handle Bash 5.0 BASH_ARGC & BASH_ARGV?
  • From: Zack Weinberg <zackw@xxxxxxxxx>
• Any plan to handle Bash 5.0 BASH_ARGC & BASH_ARGV?
  • From: Tadeus Prastowo <0x66726565@xxxxxxxxx>
• Re: Why autoreconf complains about missing AM_GNU_GETTEXT
  • From: Nick Bowler <nbowler@xxxxxxxxxx>
• Why autoreconf complains about missing AM_GNU_GETTEXT
  • From: Jan Palus <atler@xxxxxxxxxxxxx>
• Re: No macro for C11/C18?
  • From: "Andrew W. Nosenko" <andrew.w.nosenko@xxxxxxxxx>
• Re: No macro for C11/C18?
  • From: Nick Bowler <nbowler@xxxxxxxxxx>
• Re: Makefile.am target name prefix *.o
  • From: Vincent Blondel <vbl5968@xxxxxxxxx>
• Re: Makefile.am target name prefix *.o
  • From: Russ Allbery <eagle@xxxxxxxxx>
• Re: Makefile.am target name prefix *.o
  • From: Sébastien Hinderer <Sebastien.Hinderer@xxxxxxxx>
• Makefile.am target name prefix *.o
  • From: Vincent Blondel <vbl5968@xxxxxxxxx>
• Re: No macro for C11/C18?
  • From: "Andrew W. Nosenko" <andrew.w.nosenko@xxxxxxxxx>
• Re: No macro for C11/C18?
  • From: Sébastien Hinderer <Sebastien.Hinderer@xxxxxxxx>
• GNU Tools Cauldron 2020
  • From: Olivier Hainque <hainque@xxxxxxxxxxx>
• Re: Autoconf Digest, Vol 187, Issue 4
  • From: Keith Bostic via Discussion list for the autoconf build system <autoconf@xxxxxxx>
• Re: No macro for C11/C18?
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: No macro for C11/C18?
  • From: Nick Bowler <nbowler@xxxxxxxxxx>
• Re: No macro for C11/C18?
  • From: Christian Biesinger <cbiesinger@xxxxxxxxxx>
• Re: No macro for C11/C18?
  • From: Nick Bowler <nbowler@xxxxxxxxxx>
• Re: No macro for C11/C18?
  • From: Nicholas Clark <nicholas.clark@xxxxxxxxx>
• Re: No macro for C11/C18?
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• No macro for C11/C18?
  • From: Christian Biesinger <cbiesinger@xxxxxxxxxx>
• Re: STDCXX issue
  • From: Vincent Blondel <vbl5968@xxxxxxxxx>
• Re: STDCXX issue
  • From: Zack Weinberg <zackw@xxxxxxxxx>
• Re: STDCXX issue
  • From: Zack Weinberg <zackw@xxxxxxxxx>
• Re: STDCXX issue
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• Re: STDCXX issue
  • From: Sébastien Hinderer <Sebastien.Hinderer@xxxxxxxx>
• Re: STDCXX issue
  • From: Sébastien Hinderer <Sebastien.Hinderer@xxxxxxxx>
• Re: STDCXX issue
  • From: Vincent Blondel <vbl5968@xxxxxxxxx>
• Re: STDCXX issue
  • From: Vincent Blondel <vbl5968@xxxxxxxxx>
• Re: STDCXX issue
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• Re: STDCXX issue
  • From: Sébastien Hinderer <Sebastien.Hinderer@xxxxxxxx>
• STDCXX issue
  • From: Vincent Blondel <vbl5968@xxxxxxxxx>
• Re: Autotools lint tool
  • From: Sébastien Hinderer <Sebastien.Hinderer@xxxxxxxx>
• Fyi: this list, autoconf, just had it's subject [tag] and footer removed
  • From: sysadmin@xxxxxxx
• Re: Autotools lint tool
  • From: "David A. Wheeler" <dwheeler@xxxxxxxxxxxx>
• Re: Autotools lint tool
  • From: Sébastien Hinderer <Sebastien.Hinderer@xxxxxxxx>
• Re: Any chance to make a new autoconf release?
  • From: Noah Misch <noah@xxxxxxxxxxxx>
• Re: Autotools lint tool
  • From: "David A. Wheeler" <dwheeler@xxxxxxxxxxxx>
• Re: Autotools lint tool
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• Re: Autotools lint tool
  • From: Richard Ash <richard@xxxxxxxxxxxxxxxx>
• Re: Autotools lint tool
  • From: "David A. Wheeler" <dwheeler@xxxxxxxxxxxx>
• Re: Autotools lint tool
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• Re: Autotools lint tool
  • From: Warren Young <warren@xxxxxxxxxxx>
• Re: Autotools lint tool
  • From: Warren Young <warren@xxxxxxxxxxx>
• Autotools lint tool
  • From: Gabriel Lisaca <gabriel.lisaca@xxxxxxxxx>
• Re: How should long messages be displayed
  • From: Sébastien Hinderer <Sebastien.Hinderer@xxxxxxxx>
• Re: How should long messages be displayed
  • From: Eric Blake <eblake@xxxxxxxxxx>
• How should long messages be displayed
  • From: Sébastien Hinderer <Sebastien.Hinderer@xxxxxxxx>
• Re: Check if a macro has already been defined with AC_DEFINE
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• Check if a macro has already been defined with AC_DEFINE
  • From: Quaquaraqua <nuquaquaraqua@xxxxxxxxx>
• Re: Conventions on build variables
  • From: Sébastien Hinderer <Sebastien.Hinderer@xxxxxxxx>
• Re: testsuite could basename the "Generated from"
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• testsuite could basename the "Generated from"
  • From: Luke Mewburn <lukem@xxxxxxxxxx>
• Re: Conventions on build variables
  • From: Nick Bowler <nbowler@xxxxxxxxxx>
• Re: Conventions on build variables
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• Re: Conventions on build variables
  • From: Sébastien Hinderer <Sebastien.Hinderer@xxxxxxxx>
• Re: Using AC_DEFINE with AC_ARG_ENABLE (or AC_ARG_WITH)
  • From: Chris Packham <Chris.Packham@xxxxxxxxxxxxxxxxxxx>
• Re: Using AC_DEFINE with AC_ARG_ENABLE (or AC_ARG_WITH)
  • From: Mauro Aranda <maurooaranda@xxxxxxxxx>
• Re: Using AC_DEFINE with AC_ARG_ENABLE (or AC_ARG_WITH)
  • From: Nick Bowler <nbowler@xxxxxxxxxx>
• Using AC_DEFINE with AC_ARG_ENABLE (or AC_ARG_WITH)
  • From: Chris Packham <Chris.Packham@xxxxxxxxxxxxxxxxxxx>
• Re: Conventions on build variables
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• Conventions on build variables
  • From: Sébastien Hinderer <Sebastien.Hinderer@xxxxxxxx>
• Re: Making a path absolute portably
  • From: Sébastien Hinderer <Sebastien.Hinderer@xxxxxxxx>
• Re: Making a path absolute portably
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• Re: Making a path absolute portably
  • From: Sébastien Hinderer <Sebastien.Hinderer@xxxxxxxx>
• Re: Making a path absolute portably
  • From: Andrew Price <anprice@xxxxxxxxxx>
• Re: Making a path absolute portably
  • From: Sébastien Hinderer <Sebastien.Hinderer@xxxxxxxx>
• Re: Making a path absolute portably
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• Re: Making a path absolute portably
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: Making a path absolute portably
  • From: Andrew Price <anprice@xxxxxxxxxx>
• Re: Making a path absolute portably
  • From: Markus Elfring <Markus.Elfring@xxxxxx>
• Re: Making a path absolute portably
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: Making a path absolute portably
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• Making a path absolute portably
  • From: Sébastien Hinderer <Sebastien.Hinderer@xxxxxxxx>
• Re: autotest/AT_CHECK: ways to pass additional options on to diff?
  • From: Luke Mewburn <lukem@xxxxxxxxxx>
• RE: autotest/AT_CHECK: ways to pass additional options on to diff?
  • From: "Jannick" <thirdedition@xxxxxxx>
• RE: autotest/AT_CHECK: ways to pass additional options on to diff?
  • From: "Jannick" <thirdedition@xxxxxxx>
• Re: Re-exec of $as_myself chooses wrong configure script from PATH
  • From: Michael Orlitzky <michael@xxxxxxxxxxxx>
• Re: autotest/AT_CHECK: ways to pass additional options on to diff?
  • From: Luke Mewburn <lukem@xxxxxxxxxx>
• Re: Re-exec of $as_myself chooses wrong configure script from PATH
  • From: Michael Orlitzky <michael@xxxxxxxxxxxx>
• Re: Re-exec of $as_myself chooses wrong configure script from PATH
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re-exec of $as_myself chooses wrong configure script from PATH
  • From: Michael Orlitzky <michael@xxxxxxxxxxxx>
• Re: iconv.m4 macro updates
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• iconv.m4 macro updates
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• RE: autotest/AT_CHECK: ways to pass additional options on to diff?
  • From: "Jannick" <thirdedition@xxxxxxx>
• Re: autotest/AT_CHECK: ways to pass additional options on to diff?
  • From: Nick Bowler <nbowler@xxxxxxxxxx>
• RE: autotest/AT_CHECK: ways to pass additional options on to diff?
  • From: "Jannick" <thirdedition@xxxxxxx>
• Re: OpenWatcom support
  • From: microsoft gaofei <wangziheng@xxxxxxxxxxx>
• Re: autotest/AT_CHECK: ways to pass additional options on to diff?
  • From: Nick Bowler <nbowler@xxxxxxxxxx>
• autotest/AT_CHECK: ways to pass additional options on to diff?
  • From: "Jannick" <thirdedition@xxxxxxx>
• Re: Package version number, autoconf, automake
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• Re: Package version number, autoconf, automake
  • From: Vivien Kraus <vivien@xxxxxxxxxxxxxxxx>
• Re: Package version number, autoconf, automake
  • From: Gavin Smith <gavinsmith0123@xxxxxxxxx>
• Package version number, autoconf, automake
  • From: Dudziak Krzysztof <krzysztof.dudziak@xxxxxxxxxxxxxxx>
• Re: Is it possible to include variables for installation paths in atconfig? [installcheck target]
  • From: Simon Sobisch <simonsobisch@xxxxxxx>
• Re: AC_PROG_CC’s recommendation for “: ${CFLAGS=""}”
  • From: Дилян Палаузов <dilyan.palauzov@xxxxxxxxx>
• Is it possible to include variables for installation paths in atconfig? [installcheck target]
  • From: Simon Sobisch <simonsobisch@xxxxxxx>
• Re: AC_PROG_CC’s recommendation for “: ${CFLAGS=""}”
  • From: Nick Bowler <nbowler@xxxxxxxxxx>
• AC_PROG_CC’s recommendation for “: ${CFLAGS=""}”
  • From: Дилян Палаузов <dilyan.palauzov@xxxxxxxxx>
• Re: [bug-gettext] failure in building po/Makefile due to crippled sed
  • From: Bruno Haible <bruno@xxxxxxxxx>
• Re: [bug-gettext] failure in building po/Makefile due to crippled sed
  • From: Warren Young <warren@xxxxxxxxxxx>
• Re: [bug-gettext] failure in building po/Makefile due to crippled sed
  • From: pluto@xxxxxxxxxxxxxxx (Perry Hutchison)
• Re: [bug-gettext] failure in building po/Makefile due to crippled sed
  • From: Bruno Haible <bruno@xxxxxxxxx>
• Re: failure in building po/Makefile due to crippled sed
  • From: Eric Blake <eblake@xxxxxxxxxx>
• failure in building po/Makefile due to crippled sed
  • From: pluto@xxxxxxxxxxxxxxx (Perry Hutchison)
• Re: Why does autoupdate remove spaces after commas in AC_INIT only?
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Why does autoupdate remove spaces after commas in AC_INIT only?
  • From: Matthieu Poullet <matthieu.poullet@xxxxxxxxx>
• Re: Any chance to make a new autoconf release?
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: Any chance to make a new autoconf release?
  • From: Paul Smith <psmith@xxxxxxx>
• Re: Any chance to make a new autoconf release?
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: Any chance to make a new autoconf release?
  • From: Nicholas Clark <nicholas.clark@xxxxxxxxx>
• Re: Any chance to make a new autoconf release?
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• Re: Any chance to make a new autoconf release?
  • From: bill-auger <bill-auger@peers.community>
• Re: Any chance to make a new autoconf release?
  • From: Nicholas Clark <nicholas.clark@xxxxxxxxx>
• Re: Any chance to make a new autoconf release?
  • From: bill-auger <bill-auger@peers.community>
• Re: Any chance to make a new autoconf release?
  • From: Tomasz Kłoczko <kloczko.tomasz@xxxxxxxxx>
• Re: Any chance to make a new autoconf release?
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Any chance to make a new autoconf release?
  • From: Tomasz Kłoczko <kloczko.tomasz@xxxxxxxxx>
• Checking for an icon pack
  • From: Alexandros Theodotou <alextee@xxxxxxxxxx>
• Re: autoreconf and depcomp
  • From: Eric Blake <eblake@xxxxxxxxxx>
• autoreconf and depcomp
  • From: bill-auger <bill-auger@peers.community>
• Re: Where are the original commands defined?
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: Where are the original commands defined?
  • From: Peng Yu <pengyu.ut@xxxxxxxxx>
• Re: Where are the original commands defined?
  • From: Zack Weinberg <zackw@xxxxxxxxx>
• Where are the original commands defined?
  • From: Peng Yu <pengyu.ut@xxxxxxxxx>
• Re: how to let configure know include and library path for library foo?
  • From: Sébastien Hinderer <Sebastien.Hinderer@xxxxxxxx>
• Re: how to let configure know include and library path for library foo?
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• Re: how to let configure know include and library path for library foo?
  • From: Sébastien Hinderer <Sebastien.Hinderer@xxxxxxxx>
• Re: how to let configure know include and library path for library foo?
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• Re: how to let configure know include and library path for library foo?
  • From: Peter Johansson <trojkan@xxxxxxxxx>
• how to let configure know include and library path for library foo?
  • From: Sébastien Hinderer <Sebastien.Hinderer@xxxxxxxx>
• Re: What is the correct way to disable -O2?
  • From: Eric Blake <eblake@xxxxxxxxxx>
• What is the correct way to disable -O2?
  • From: Peng Yu <pengyu.ut@xxxxxxxxx>
• Re: Caching compiler features?
  • From: "David A. Wheeler" <dwheeler@xxxxxxxxxxxx>
• Caching compiler features?
  • From: Andrew Pennebaker <andrew.pennebaker@xxxxxxxxx>
• [PATCH] doc/autoconf.texi: fix spelling/grammar nits
  • From: Jim Meyering <jim@xxxxxxxxxxxx>
• Re: Arguments to configure
  • From: Sébastien Hinderer <Sebastien.Hinderer@xxxxxxxx>
• Re: Arguments to configure
  • From: Sébastien Hinderer <Sebastien.Hinderer@xxxxxxxx>
• Re: configure: error: C preprocessor "/lib/cpp" fails sanity check
  • From: Fabiano Sidler <fabianosidler@xxxxxxxxxxxxxx>
• Re: configure: error: C preprocessor "/lib/cpp" fails sanity check
  • From: Earnie <earnie@xxxxxxxxxxxxxxxxxxxxx>
• Re: configure: error: C preprocessor "/lib/cpp" fails sanity check
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: configure: error: C preprocessor "/lib/cpp" fails sanity check
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• configure: error: C preprocessor "/lib/cpp" fails sanity check
  • From: Fabiano Sidler <fabianosidler@xxxxxxxxxxxxxx>
• Re: Arguments to configure
  • From: Sébastien Hinderer <Sebastien.Hinderer@xxxxxxxx>
• Re: Arguments to configure
  • From: Gavin Smith <gavinsmith0123@xxxxxxxxx>
• Re: Arguments to configure
  • From: Gavin Smith <gavinsmith0123@xxxxxxxxx>
• Re: Arguments to configure
  • From: Nick Bowler <nbowler@xxxxxxxxxx>
• Re: Arguments to configure
  • From: Vivien Kraus <vivien@xxxxxxxxxxxxxxxx>
• Re: Arguments for OCaml build configuration
  • From: SF Markus Elfring <elfring@xxxxxxxxxxxxxxxxxxxxx>
• Re: Arguemnts to configure
  • From: Sébastien Hinderer <Sebastien.Hinderer@xxxxxxxx>
• Re: Arguments to configure
  • From: Sébastien Hinderer <Sebastien.Hinderer@xxxxxxxx>
• Re: Arguemnts to configure
  • From: Vivien Kraus <vivien@xxxxxxxxxxxxxxxx>
• Re: Arguemnts to configure
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Arguemnts to configure
  • From: Sébastien Hinderer <Sebastien.Hinderer@xxxxxxxx>
• Re: Checking support of #! scripts
  • From: Sébastien Hinderer <Sebastien.Hinderer@xxxxxxxx>
• Checking support of #! scripts
  • From: Sébastien Hinderer <Sebastien.Hinderer@xxxxxxxx>
• Re: non standard name of a dependency
  • From: Catonano <catonano@xxxxxxxxx>
• Re: non standard name of a dependency
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: non standard name of a dependency
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• non standard name of a dependency
  • From: Catonano <catonano@xxxxxxxxx>
• Re: automatically showing test-suite.log on failure?
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: Skip all version checks with autoconf?
  • From: Earnie <earnie@xxxxxxxxxxxxxxxxxxxxx>
• Re: Skip all version checks with autoconf?
  • From: Keith Marshall <keith@xxxxxxxxxxxxx>
• Re: Skip all version checks with autoconf?
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• Re: Skip all version checks with autoconf?
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: Skip all version checks with autoconf?
  • From: Marko Lindqvist <cazfi74@xxxxxxxxx>
• Re: Skip all version checks with autoconf?
  • From: Warren Young <warren@xxxxxxxxxxx>
• Re: Skip all version checks with autoconf?
  • From: Basin Ilya <basinilya@xxxxxxxxx>
• Re: Skip all version checks with autoconf?
  • From: Nicholas Clark <nicholas.clark@xxxxxxxxx>
• Re: Skip all version checks with autoconf?
  • From: Basin Ilya <basinilya@xxxxxxxxx>
• Re: Skip all version checks with autoconf?
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: Skip all version checks with autoconf?
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Re: Skip all version checks with autoconf?
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Re: Skip all version checks with autoconf?
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Skip all version checks with autoconf?
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Re: cl.exe and system types
  • From: Sébastien Hinderer <Sebastien.Hinderer@xxxxxxxx>
• Re: cl.exe and system types
  • From: Keith Marshall <keith@xxxxxxxxxxxxx>
• Re: cl.exe and system types
  • From: Sébastien Hinderer <Sebastien.Hinderer@xxxxxxxx>
• Re: cl.exe and system types
  • From: Keith Marshall <keith@xxxxxxxxxxxxx>
• Re: cl.exe and system types
  • From: Earnie <earnie@xxxxxxxxxxxxxxxxxxxxx>
• Re: cl.exe and system types
  • From: Sébastien Hinderer <Sebastien.Hinderer@xxxxxxxx>
• Re: cl.exe and system types
  • From: Sébastien Hinderer <Sebastien.Hinderer@xxxxxxxx>
• Re: cl.exe and system types
  • From: Earnie <earnie@xxxxxxxxxxxxxxxxxxxxx>
• Re: Conflict between standard headers and winsock(2).h
  • From: Peter Rosin <peda@xxxxxxxxxxxxxx>
• Re: cl.exe and system types
  • From: Peter Rosin <peda@xxxxxxxxxxxxxx>
• Re: cl.exe and system types
  • From: Nick Bowler <nbowler@xxxxxxxxxx>
• Re: cl.exe and system types
  • From: Sébastien Hinderer <Sebastien.Hinderer@xxxxxxxx>
• Re: cl.exe and system types
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• Re: cl.exe and system types
  • From: Earnie <earnie@xxxxxxxxxxxxxxxxxxxxx>
• Re: cl.exe and system types
  • From: Sébastien Hinderer <Sebastien.Hinderer@xxxxxxxx>
• Re: cl.exe and system types
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• Re: cl.exe and system types
  • From: Sébastien Hinderer <Sebastien.Hinderer@xxxxxxxx>
• Re: cl.exe and system types
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• Re: cl.exe and system types
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• cl.exe and system types
  • From: Sébastien Hinderer <Sebastien.Hinderer@xxxxxxxx>
• Re: Cross-platform "warning is an error" with Autoconf?
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: Cross-platform "warning is an error" with Autoconf?
  • From: Nick Bowler <nbowler@xxxxxxxxxx>
• Re: How can we run all tests using C++ specified compiler?
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• Re: How can we run all tests using C++ specified compiler?
  • From: Václav Haisman <vhaisman@xxxxxxxxx>
• How can we run all tests using C++ specified compiler?
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Re: Cross-platform "warning is an error" with Autoconf?
  • From: Peter Johansson <trojkan@xxxxxxxxx>
• Cross-platform "warning is an error" with Autoconf?
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• How to suppress -blibpath on AIX?
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Re: Make and subdir
  • From: Václav Haisman <vhaisman@xxxxxxxxx>
• Re: Make and subdir
  • From: Warren Young <warren@xxxxxxxxxxx>
• Make and subdir
  • From: Mauricio Ramirez <mauricio.ramirez@xxxxxxxxxx>
• Re: How to write directly to config.h from configure?
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Re: How to write directly to config.h from configure?
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• Re: How to write directly to config.h from configure?
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: How to write directly to config.h from configure?
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Re: How to write directly to config.h from configure?
  • From: Warren Young <warren@xxxxxxxxxxx>
• Re: AC_COMPILE_ELSEIF and AC_LINK_ELSEIF misdetections
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Re: AC_COMPILE_ELSEIF and AC_LINK_ELSEIF misdetections
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Re: How to write directly to config.h from configure?
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: How to write directly to config.h from configure?
  • From: Nick Bowler <nbowler@xxxxxxxxxx>
• Re: AC_COMPILE_ELSEIF and AC_LINK_ELSEIF misdetections
  • From: Zack Weinberg <zackw@xxxxxxxxx>
• Re: How to write directly to config.h from configure?
  • From: Zack Weinberg <zackw@xxxxxxxxx>
• AC_COMPILE_ELSEIF and AC_LINK_ELSEIF misdetections
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• How to write directly to config.h from configure?
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• C compiler detection question
  • From: Sébastien Hinderer <Sebastien.Hinderer@xxxxxxxx>
• Detecting object file format
  • From: Sébastien Hinderer <Sebastien.Hinderer@xxxxxxxx>
• Re: Configure tests using pipes
  • From: Earnie <earnie@xxxxxxxxxxxxxxxxxxxxx>
• Re: Configure tests using pipes
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: Configure tests using pipes
  • From: NightStrike <nightstrike@xxxxxxxxx>
• Re: Configure tests using pipes
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Configure tests using pipes
  • From: NightStrike <nightstrike@xxxxxxxxx>
• Re: Release request
  • From: Nicholas Clark <nicholas.clark@xxxxxxxxx>
• Re: Release request
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Release request
  • From: Steven Winfield <Steven.Winfield@xxxxxxxxxxxxxxxxx>
• Re: config.status: error: cannot find input file: ` .in'
  • From: John Calcote <john.calcote@xxxxxxxxx>
• Re: config.status: error: cannot find input file: ` .in'
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: config.status: error: cannot find input file: ` .in'
  • From: John Calcote <john.calcote@xxxxxxxxx>
• config.status: error: cannot find input file: ` .in'
  • From: Sascha Manns <Sascha.Manns@xxxxxxxxxx>
• Re: Makefiles guidance
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• Re: Makefiles guidance
  • From: Anmol Mishra <anmolmishra.jiit@xxxxxxxxx>
• Re: Makefiles guidance
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• Makefiles guidance
  • From: Anmol Mishra <anmolmishra.jiit@xxxxxxxxx>
• Re: Help for makefiles
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• Re: Help for makefiles
  • From: Anmol Mishra <anmolmishra.jiit@xxxxxxxxx>
• Re: Help for makefiles
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• Help for makefiles
  • From: Anmol Mishra <anmolmishra.jiit@xxxxxxxxx>
• Re: using autoconf to create build scripts for Assembly language programs
  • From: mallapadi niranjan <niranjan.ashok@xxxxxxxxx>
• Re: using autoconf to create build scripts for Assembly language programs
  • From: Basin Ilya <basinilya@xxxxxxxxx>
• Re: using autoconf to create build scripts for Assembly language programs
  • From: mallapadi niranjan <niranjan.ashok@xxxxxxxxx>
• Re: using autoconf to create build scripts for Assembly language programs
  • From: Basin Ilya <basinilya@xxxxxxxxx>
• Re: configure[xxxx]: : is not an identifer
  • From: "Kevin R. Bulgrien" <kevinb@xxxxxxxxxxxxxxxxxxxx>
• Re: configure[xxxx]: : is not an identifer
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: configure[xxxx]: : is not an identifer
  • From: "Kevin R. Bulgrien" <kevinb@xxxxxxxxxxxxxxxxxxxx>
• Re: configure[xxxx]: : is not an identifer
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: configure[xxxx]: : is not an identifer
  • From: "Kevin R. Bulgrien" <kevinb@xxxxxxxxxxxxxxxxxxxx>
• Re: configure[xxxx]: : is not an identifer
  • From: Eric Blake <eblake@xxxxxxxxxx>
• configure[xxxx]: : is not an identifer
  • From: "Kevin R. Bulgrien" <kevinb@xxxxxxxxxxxxxxxxxxxx>
• Re: using autoconf to create build scripts for Assembly language programs
  • From: mallapadi niranjan <niranjan.ashok@xxxxxxxxx>
• Re: using autoconf to create build scripts for Assembly language programs
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: using autoconf to create build scripts for Assembly language programs
  • From: mallapadi niranjan <niranjan.ashok@xxxxxxxxx>
• Re: using autoconf to create build scripts for Assembly language programs
  • From: Eric Blake <eblake@xxxxxxxxxx>
• using autoconf to create build scripts for Assembly language programs
  • From: mallapadi niranjan <niranjan.ashok@xxxxxxxxx>
• Re: sharedlocalstate default - does anybody use this?
  • From: Russ Allbery <eagle@xxxxxxxxx>
• Re: sharedlocalstate default - does anybody use this?
  • From: Eric Blake <eblake@xxxxxxxxxx>
• sharedlocalstate default - does anybody use this?
  • From: "Mariano, Adrian V." <adrian@xxxxxxxxx>
• Re: why generate output to tmp file and mv to actual file?
  • From: John Calcote <john.calcote@xxxxxxxxx>
• Re: why generate output to tmp file and mv to actual file?
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: why generate output to tmp file and mv to actual file?
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• why generate output to tmp file and mv to actual file?
  • From: John Calcote <john.calcote@xxxxxxxxx>
• Re: unable to escape ! in autotest stdout comparison text
  • From: Gavin Smith <gavinsmith0123@xxxxxxxxx>
• Re: Problem with --version after compiling autoconf
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: Problem with --version after compiling autoconf
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: Problem with --version after compiling autoconf
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: Problem with --version after compiling autoconf
  • From: Andy Armstrong <andyarmstrong@xxxxxxxxxxxxx>
• Re: unable to escape ! in autotest stdout comparison text
  • From: John Calcote <john.calcote@xxxxxxxxx>
• Re: unable to escape ! in autotest stdout comparison text
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: unable to escape ! in autotest stdout comparison text
  • From: John Calcote <john.calcote@xxxxxxxxx>
• Re: unable to escape ! in autotest stdout comparison text
  • From: Nick Bowler <nbowler@xxxxxxxxxx>
• unable to escape ! in autotest stdout comparison text
  • From: John Calcote <john.calcote@xxxxxxxxx>
• Re: Problem with --version after compiling autoconf
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Problem with --version after compiling autoconf
  • From: Andy Armstrong <andyarmstrong@xxxxxxxxxxxxx>
• Re: Does a 2.70 release exist?
  • From: Nicholas Clark <nicholas.clark@xxxxxxxxx>
• Re: Does a 2.70 release exist?
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Does a 2.70 release exist?
  • From: Nicholas Clark <nicholas.clark@xxxxxxxxx>
• Re: [autoconf archive] syntax error in ax_lib_postgresql.m4 script.
  • From: Jules Lamur <jules.lamur@xxxxxxxxx>
• Re: [autoconf archive] syntax error in ax_lib_postgresql.m4 script.
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: [autoconf archive] syntax error in ax_lib_postgresql.m4 script.
  • From: Eric Blake <eblake@xxxxxxxxxx>
• [autoconf archive] syntax error in ax_lib_postgresql.m4 script.
  • From: Jules Lamur <jules.lamur@xxxxxxxxx>
• Re: How to change the shebang in 'configure' to require Bash
  • From: Warren Young <warren@xxxxxxxxxxx>
• Re: Conflict between standard headers and winsock(2).h
  • From: Marko Lindqvist <cazfi74@xxxxxxxxx>
• Re: How to change the shebang in 'configure' to require Bash
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• Re: How to change the shebang in 'configure' to require Bash
  • From: Russell Shaw <rjshaw@xxxxxxxxxxxxxxx>
• Re: How to change the shebang in 'configure' to require Bash
  • From: Russell Shaw <rjshaw@xxxxxxxxxxxxxxx>
• Re: How to change the shebang in 'configure' to require Bash
  • From: "R. Diez" <rdiezmail-temp2@xxxxxxxx>
• Re: How to change the shebang in 'configure' to require Bash
  • From: Warren Young <warren@xxxxxxxxxxx>
• Re: How to change the shebang in 'configure' to require Bash
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• Re: How to change the shebang in 'configure' to require Bash
  • From: Eric Blake <eblake@xxxxxxxxxx>
• How to change the shebang in 'configure' to require Bash
  • From: "R. Diez" <rdiezmail-temp2@xxxxxxxx>
• Re: Please add an option to fetch missing pieces online
  • From: Vivien Kraus <vivien@xxxxxxxxxxxxxxxx>
• Please add an option to fetch missing pieces online
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Re: Autoconf protype breaks GCC builtin inlining
  • From: Nick Bowler <nbowler@xxxxxxxxxx>
• Re: Autoconf protype breaks GCC builtin inlining
  • From: wferi@xxxxxxx (Ferenc Wágner)
• Re: Autoconf protype breaks GCC builtin inlining
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Re: Autoconf protype breaks GCC builtin inlining
  • From: wferi@xxxxxxx (Ferenc Wágner)
• Re: CFLAGS for GCC
  • From: Mike Frysinger <vapier@xxxxxxxxxx>
• CFLAGS for GCC
  • From: Victor Porton <porton@xxxxxxxx>
• Re: Autoconf protype breaks GCC builtin inlining
  • From: Zack Weinberg <zackw@xxxxxxxxx>
• Re: Autoconf protype breaks GCC builtin inlining
  • From: Zack Weinberg <zackw@xxxxxxxxx>
• Re: Autoconf protype breaks GCC builtin inlining
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Autoconf protype breaks GCC builtin inlining
  • From: wferi@xxxxxxx (Ferenc Wágner)
• Re: m4_map and AC_REQUIRE hoisting
  • From: Nick Bowler <nbowler@xxxxxxxxxx>
• Re: m4_map and AC_REQUIRE hoisting
  • From: Eric Blake <eblake@xxxxxxxxxx>
• m4_map and AC_REQUIRE hoisting
  • From: Nick Bowler <nbowler@xxxxxxxxxx>
• Re: Should I define _GNU_SOURCE?
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: Should I define _GNU_SOURCE?
  • From: Mathieu Lirzin <mthl@xxxxxxx>
• Re: Should I define _GNU_SOURCE?
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: Should I define _GNU_SOURCE?
  • From: Mathieu Lirzin <mthl@xxxxxxx>
• Re: Should I define _GNU_SOURCE?
  • From: Mathieu Lirzin <mthl@xxxxxxx>
• Should I define _GNU_SOURCE?
  • From: Victor Porton <porton@xxxxxxxx>
• how do I substitute the library prefix?
  • From: Sam Steingold <sds@xxxxxxx>
• Re: How to configure Autoconf in /usr/local to use M4 in /usr/local?
  • From: Earnie <earnie@xxxxxxxxxxxxxxxxxxxxx>
• Re: How to configure Autoconf in /usr/local to use M4 in /usr/local?
  • From: Earnie <earnie@xxxxxxxxxxxxxxxxxxxxx>
• Re: How to configure Autoconf in /usr/local to use M4 in /usr/local?
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• How to configure Autoconf in /usr/local to use M4 in /usr/local?
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Re: How to check for SIGABRT?
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• Re: How to check for SIGABRT?
  • From: Russ Allbery <eagle@xxxxxxxxx>
• Re: How to check for SIGABRT?
  • From: Eric Blake <eblake@xxxxxxxxxx>
• How to check for SIGABRT?
  • From: Simon Sobisch <simonsobisch@xxxxxx>
• make check and output to stdout/stderr
  • From: Rainer Gerhards <rgerhards@xxxxxxxxx>
• Re: Autoconf and Fedora x86_64 /usr/local/lib64?
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Re: Autoconf and Fedora x86_64 /usr/local/lib64?
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Autoconf and Fedora x86_64 /usr/local/lib64?
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Re: [Autoconf] help configure project for HPC - non-standard ways to run the executable
  • From: Christian Feld <c.feld@xxxxxxxxxxxxx>
• Re: [Autoconf] help configure project for HPC - non-standard ways to run the executable
  • From: suzuki toshiya <mpsuzuki@xxxxxxxxxxxxxxxxx>
• Re: [Autoconf] help configure project for HPC - non-standard ways to run the executable
  • From: Anton Shterenlikht <as@xxxxxxxx>
• Re: [Autoconf] help configure project for HPC - non-standard ways to run the executable
  • From: suzuki toshiya <mpsuzuki@xxxxxxxxxxxxxxxxx>
• Re: [Autoconf] help configure project for HPC - non-standard ways to run the executable
  • From: suzuki toshiya <mpsuzuki@xxxxxxxxxxxxxxxxx>
• help configure project for HPC - non-standard ways to run the executable
  • From: Anton Shterenlikht <as@xxxxxxxx>
• Re: Bug#850329: autoconf tries to execute foreign binaries
  • From: Keith Marshall <keith.d.marshall@xxxxxxxxxxxx>
• Re: Bug#850329: autoconf tries to execute foreign binaries
  • From: Earnie <earnie@xxxxxxxxxxxxxxxxxxxxx>
• Re: Bug#850329: autoconf tries to execute foreign binaries
  • From: Ben Pfaff <blp@xxxxxxxxxxxxxxx>
• Re: Why my AT_CHECK() can't work?
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: Why my AT_CHECK() can't work?
  • From: Sam <batmanustc@xxxxxxxxx>
• Re: "Packing" binary data into object files using autotools
  • From: Gavin Smith <gavinsmith0123@xxxxxxxxx>
• Re: "Packing" binary data into object files using autotools
  • From: Thomas Nyberg <tomuxiong@xxxxxxx>
• Re: "Packing" binary data into object files using autotools
  • From: Thomas Nyberg <tomuxiong@xxxxxxx>
• "Packing" binary data into object files using autotools
  • From: Thomas Nyberg <tomuxiong@xxxxxxx>
• Re: Why my AT_CHECK() can't work?
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: Why my AT_CHECK() can't work?
  • From: Sam <batmanustc@xxxxxxxxx>
• Re: Why my AT_CHECK() can't work?
  • From: Sam <batmanustc@xxxxxxxxx>
• Re: Why my AT_CHECK() can't work?
  • From: Zack Weinberg <zackw@xxxxxxxxx>
• Re: Why my AT_CHECK() can't work?
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: Why my AT_CHECK() can't work?
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Why my AT_CHECK() can't work?
  • From: Sam <batmanustc@xxxxxxxxx>
• Re: Why my AT_CHECK() can't work?
  • From: Sam <batmanustc@xxxxxxxxx>
• Re: Determination of default configuration values for build projects and checking the settings
  • From: SF Markus Elfring <elfring@xxxxxxxxxxxxxxxxxxxxx>
• Safe descriptions for configuration variables?
  • From: SF Markus Elfring <elfring@xxxxxxxxxxxxxxxxxxxxx>
• Re: Determination of default configuration values for build projects and checking the settings
  • From: Zack Weinberg <zackw@xxxxxxxxx>
• Clarification for defining variables?
  • From: SF Markus Elfring <elfring@xxxxxxxxxxxxxxxxxxxxx>
• Re: Determination of default configuration values for build projects and checking the settings
  • From: SF Markus Elfring <elfring@xxxxxxxxxxxxxxxxxxxxx>
• Re: Determination of default configuration values for build projects and checking the settings
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Determination of default configuration values for build projects and checking the settings
  • From: SF Markus Elfring <elfring@xxxxxxxxxxxxxxxxxxxxx>
• Re: How to deal with test data in ouf of source tree builds?
  • From: Peter Johansson <trojkan@xxxxxxxxx>
• Re: How to deal with test data in ouf of source tree builds?
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• Re: How to deal with test data in ouf of source tree builds?
  • From: Nick Bowler <nbowler@xxxxxxxxxx>
• How to deal with test data in ouf of source tree builds?
  • From: Paul Menzel <pmenzel@xxxxxxxxxxxxx>
• Re: Why doesn't Autotools makefile update Bash hash cache after install?
  • From: Earnie <earnie@xxxxxxxxxxxxxxxxxxxxx>
• Re: Why doesn't Autotools makefile update Bash hash cache after install?
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Re: Why doesn't Autotools makefile update Bash hash cache after install?
  • From: Zack Weinberg <zackw@xxxxxxxxx>
• Re: Timeline for 2.70 (hit issue fixed in e17a30e9)
  • From: Václav Haisman <vhaisman@xxxxxxxxx>
• Re: Why doesn't Autotools makefile update Bash hash cache after install?
  • From: Zack Weinberg <zackw@xxxxxxxxx>
• Why doesn't Autotools makefile update Bash hash cache after install?
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Management for relative paths in global build system settings
  • From: SF Markus Elfring <elfring@xxxxxxxxxxxxxxxxxxxxx>
• Re: absolute beginner
  • From: Catonano <catonano@xxxxxxxxx>
• Re: absolute beginner
  • From: Marco Maggi <marco.maggi-ipsu@xxxxxxxx>
• absolute beginner
  • From: Catonano <catonano@xxxxxxxxx>
• Re: Fortran wrappers
  • From: Andy May <ajmay81@xxxxxxxxx>
• Re: Fortran wrappers
  • From: "Daily, Jeff A" <jeff.daily@xxxxxxxx>
• Re: Fortran wrappers
  • From: Rhys Ulerich <rhys.ulerich@xxxxxxxxx>
• Fortran wrappers
  • From: Andy May <ajmay81@xxxxxxxxx>
• Re: AC_CHECK_HEADERS, preprocessor call and Solaris
  • From: Rainer Gerhards <rgerhards@xxxxxxxxx>
• AC_CHECK_HEADERS, preprocessor call and Solaris
  • From: Rainer Gerhards <rgerhards@xxxxxxxxx>
• Re: Variable expansin in AC_PREFIX_DEFAULT
  • From: Joakim Jalap <joakim.jalap@xxxxxxxxxxxx>
• Re: Variable expansin in AC_PREFIX_DEFAULT
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Variable expansin in AC_PREFIX_DEFAULT
  • From: Joakim Jalap <joakim.jalap@xxxxxxxxxxxx>
• Re: Proper location to install shell function libraries?
  • From: Andreas Kusalananda Kähäri <andreas.kahari@xxxxxxx>
• Re: Proper location to install shell function libraries?
  • From: Andreas Kusalananda Kähäri <andreas.kahari@xxxxxxxxx>
• Re: Proper location to install shell function libraries?
  • From: Ralf Corsepius <rc040203@xxxxxxxxxx>
• Re: Proper location to install shell function libraries?
  • From: Basin Ilya <basinilya@xxxxxxxxx>
• Re: Proper location to install shell function libraries?
  • From: Russ Allbery <eagle@xxxxxxxxx>
• Re: Proper location to install shell function libraries?
  • From: Andreas Kusalananda Kähäri <andreas.kahari@xxxxxxxxx>
• Re: Proper location to install shell function libraries?
  • From: Nick Bowler <nbowler@xxxxxxxxxx>
• Re: Proper location to install shell function libraries?
  • From: Ralf Corsepius <rc040203@xxxxxxxxxx>
• Re: Proper location to install shell function libraries?
  • From: Nick Bowler <nbowler@xxxxxxxxxx>
• Re: Proper location to install shell function libraries?
  • From: Ralf Corsepius <rc040203@xxxxxxxxxx>
• Proper location to install shell function libraries?
  • From: Andreas Kusalananda Kähäri <andreas.kahari@xxxxxxxxx>
• Re: unexpected token `build_old_libs,'
  • From: Gavin Smith <gavinsmith0123@xxxxxxxxx>
• Re: #ifndef BIGENDIAN #undef BIGENDIAN ?
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Problems configuring sipxportlib with autoconf 2.69 (works with 2.57)
  • From: <amit.chaudhuri@xxxxxx>
• #ifndef BIGENDIAN #undef BIGENDIAN ?
  • From: Kai Noda <nodakai@xxxxxxxxx>
• unexpected token `build_old_libs,'
  • From: Sascha Manns <Sascha.Manns@xxxxxxxxxxx>
• Re: Configure breaks by build
  • From: Sascha Manns <Sascha.Manns@xxxxxxxxxxx>
• Re: Configure breaks by build
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: Configure breaks by build
  • From: Zack Weinberg <zackw@xxxxxxxxx>
• Configure breaks by build
  • From: Sascha Manns <Sascha.Manns@xxxxxxxxxxx>
• Re: Ggradebook; request for assistance
  • From: Russell Shaw <rjshaw@xxxxxxxxxxxxxxx>
• Re: Ggradebook; request for assistance
  • From: Norbert de Jonge <mail@xxxxxxxxxxxxxxxxx>
• Ggradebook; request for assistance
  • From: Norbert de Jonge <mail@xxxxxxxxxxxxxxxxx>
• Re: Couldn't locate INSTALL file
  • From: Ying Chang <changyi@xxxxxxxxxxxxxxxxxxxxxxx>
• Re: Couldn't locate INSTALL file
  • From: John Calcote <john.calcote@xxxxxxxxx>
• Re: Couldn't locate INSTALL file
  • From: Rudra Banerjee <bnrj.rudra@xxxxxxxx>
• Re: Couldn't locate INSTALL file
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Couldn't locate INSTALL file
  • From: Ying Chang <changyi@xxxxxxxxxxxxxxxxxxxxxxx>
• Re: config.status and /bin/sh on Solaris
  • From: Zack Weinberg <zackw@xxxxxxxxx>
• Re: configure fails when PATH=/usr/xpg4/bin:/usr/bin on Solaris 11
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• Re: config.status and /bin/sh on Solaris
  • From: Dimitrios Apostolou <jimis@xxxxxxx>
• configure fails when PATH=/usr/xpg4/bin:/usr/bin on Solaris 11
  • From: Dimitrios Apostolou <jimis@xxxxxxx>
• Re: config.status and /bin/sh on Solaris
  • From: Dimitrios Apostolou <jimis@xxxxxxx>
• Re: config.status and /bin/sh on Solaris
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• Re: config.status and /bin/sh on Solaris
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• Re: config.status and /bin/sh on Solaris
  • From: Dimitrios Apostolou <jimis@xxxxxxx>
• Re: config.status and /bin/sh on Solaris
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• Re: config.status and /bin/sh on Solaris
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Re: config.status and /bin/sh on Solaris
  • From: Dimitrios Apostolou <jimis@xxxxxxx>
• Re: config.status and /bin/sh on Solaris
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• Re: config.status and /bin/sh on Solaris
  • From: Dimitrios Apostolou <jimis@xxxxxxx>
• Re: config.status and /bin/sh on Solaris
  • From: Dimitrios Apostolou <jimis@xxxxxxx>
• Re: config.status and /bin/sh on Solaris
  • From: Zack Weinberg <zackw@xxxxxxxxx>
• Re: config.status and /bin/sh on Solaris
  • From: Dimitrios Apostolou <jimis@xxxxxxx>
• Re: config.status and /bin/sh on Solaris
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: config.status and /bin/sh on Solaris
  • From: Dimitrios Apostolou <jimis@xxxxxxx>
• Re: config.status and /bin/sh on Solaris
  • From: Zack Weinberg <zackw@xxxxxxxxx>
• config.status and /bin/sh on Solaris
  • From: Dimitrios Apostolou <jimis@xxxxxxx>
• Re: complex configure tests involving multiple files and possibly libtool/automake
  • From: Peter Johansson <trojkan@xxxxxxxxx>
• Re: Defining data files to install
  • From: Julie Marchant <onpon4@xxxxxxxxxx>
• Re: complex configure tests involving multiple files and possibly libtool/automake
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: complex configure tests involving multiple files and possibly libtool/automake
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: Defining data files to install
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Defining data files to install
  • From: Julie Marchant <onpon4@xxxxxxxxxx>
• Re: autoconf: AC_SYS_LARGEFILE documentation misleading
  • From: Thorsten Glaser <t.glaser@xxxxxxxxx>
• Re: autoconf: AC_SYS_LARGEFILE documentation misleading
  • From: Thorsten Glaser <t.glaser@xxxxxxxxx>
• complex configure tests involving multiple files and possibly libtool/automake
  • From: Václav Haisman <vhaisman@xxxxxxxxx>
• Re: autoconf: AC_SYS_LARGEFILE should output to CPPFLAGS
  • From: Thorsten Glaser <t.glaser@xxxxxxxxx>
• Re: autoconf: AC_SYS_LARGEFILE documentation misleading
  • From: Thorsten Glaser <t.glaser@xxxxxxxxx>
• Re: autoconf: AC_SYS_LARGEFILE documentation misleading
  • From: Zack Weinberg <zackw@xxxxxxxxx>
• Re: autoconf: AC_SYS_LARGEFILE documentation misleading
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: autoconf: AC_SYS_LARGEFILE should output to CPPFLAGS
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: autoconf: AC_SYS_LARGEFILE should output to CPPFLAGS
  • From: Zack Weinberg <zackw@xxxxxxxxx>
• Re: autoconf: AC_SYS_LARGEFILE should output to CPPFLAGS
  • From: Thorsten Glaser <t.glaser@xxxxxxxxx>
• Re: autoconf: AC_SYS_LARGEFILE should output to CPPFLAGS
  • From: Zack Weinberg <zackw@xxxxxxxxx>
• Re: autoconf: AC_SYS_LARGEFILE documentation misleading
  • From: Thorsten Glaser <t.glaser@xxxxxxxxx>
• Re: autoconf: AC_SYS_LARGEFILE should output to CPPFLAGS
  • From: Thorsten Glaser <t.glaser@xxxxxxxxx>
• Re: autoconf: AC_SYS_LARGEFILE should output to CPPFLAGS
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: autoconf: AC_SYS_LARGEFILE documentation misleading
  • From: Eric Blake <eblake@xxxxxxxxxx>
• autoconf: AC_SYS_LARGEFILE should output to CPPFLAGS
  • From: Thorsten Glaser <t.glaser@xxxxxxxxx>
• autoconf: AC_SYS_LARGEFILE documentation misleading
  • From: Thorsten Glaser <t.glaser@xxxxxxxxx>
• AC_PROG_CXX in autoconf 2.70
  • From: Peter Johansson <trojkan@xxxxxxxxx>
• Re: AC_PROG_CC_C89 is not adding -std=c89 to CFLAGS
  • From: Zack Weinberg <zackw@xxxxxxxxx>
• Re: AC_PROG_CC_C89 is not adding -std=c89 to CFLAGS
  • From: Dimitrios Apostolou <jimis@xxxxxxx>
• Re: AC_PROG_CC_C89 is not adding -std=c89 to CFLAGS
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• AC_PROG_CC_C89 is not adding -std=c89 to CFLAGS
  • From: Dimitrios Apostolou <jimis@xxxxxxx>
• FYI: updated copyright dates for 2.17
  • From: Jim Meyering <jim@xxxxxxxxxxxx>
• Re: Compile-Run Cycle
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: Compile-Run Cycle
  • From: Gavin Smith <gavinsmith0123@xxxxxxxxx>