Gnu Autoconf

• Thread Index

• Re: [configure.ac/uClinux] Adding code for fork/vfork?
  • From: Harlan Stenn <stenn@xxxxxxx>
• Re: [configure.ac/uClinux] Adding code for fork/vfork?
  • From: Gilles <codecomplete@xxxxxxx>
• Re: [configure.ac/uClinux] Adding code for fork/vfork?
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• AC_CHECK_LIB for X11 libraries
  • From: imacky <ian@xxxxxxxxx>
• Re: Proper m4 quoting
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: Proper m4 quoting
  • From: "Too, Justin A." <too1@xxxxxxxx>
• Re: Proper m4 quoting
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: Proper m4 quoting
  • From: "Too, Justin A." <too1@xxxxxxxx>
• Re: Proper m4 quoting
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Proper m4 quoting
  • From: "Too, Justin A." <too1@xxxxxxxx>
• [configure.ac/uClinux] Adding code for fork/vfork?
  • From: Gilles <codecomplete@xxxxxxx>
• Re: Never mind: no AC_LANG_SOURCE call detected in body
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• RE: error: '' is already registered with AC_CONFIG_FILES
  • From: Stephen Henry <Stephen.Henry@xxxxxxxxxxxx>
• Re: error: '' is already registered with AC_CONFIG_FILES
  • From: Eric Blake <eblake@xxxxxxxxxx>
• error: '' is already registered with AC_CONFIG_FILES
  • From: Stephen Henry <Stephen.Henry@xxxxxxxxxxxx>
• Re: Handling multiple conditions in if statements
  • From: Adam Mercer <ramercer@xxxxxxxxx>
• Re: Handling multiple conditions in if statements
  • From: Adam Mercer <ramercer@xxxxxxxxx>
• Re: Handling multiple conditions in if statements
  • From: Eric Blake <eblake@xxxxxxxxxx>
• RE: Handling multiple conditions in if statements
  • From: "Daily, Jeff A" <jeff.daily@xxxxxxx>
• Handling multiple conditions in if statements
  • From: Adam Mercer <ram@xxxxxxxxxxxxxxxxxxxx>
• Re: facing error making autoconf - make[3]: *** [m4sugar.m4f] Error 1
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: facing error making autoconf - make[3]: *** [m4sugar.m4f] Error 1
  • From: rden <remi.denis@xxxxxx>
• Re: Adding malloc configure test?
  • From: Gilles Ganault <gilles.ganault@xxxxxxx>
• Re: Adding malloc configure test?
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Adding malloc configure test?
  • From: Gilles Ganault <gilles.ganault@xxxxxxx>
• Never mind: no AC_LANG_SOURCE call detected in body
  • From: Bruce Korb <bkorb@xxxxxxx>
• no AC_LANG_SOURCE call detected in body
  • From: Bruce Korb <bruce.korb@xxxxxxxxx>
• Re: Multiple subdirectories with non-similar configure needs
  • From: Jim Galarowicz <jeg@xxxxxxxxxxxxx>
• Re: Question about installation configuration
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: Question about installation configuration
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Question about installation configuration
  • From: Kevin Anthony <kevin.s.anthony@xxxxxxxxx>
• Re: ac 2.68 - AC_LANG_SOURCE
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: ac 2.68 - AC_LANG_SOURCE
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• ac 2.68 - AC_LANG_SOURCE
  • From: Jan Engelhardt <jengelh@xxxxxxxxxx>
• Re: autocache
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: autocache
  • From: ams@xxxxxxx (Alfred M. Szmidt)
• Re: Multiple subdirectories with non-similar configure needs
  • From: Christian Rössel <c.roessel@xxxxxxxxxxxxx>
• Re: ax_prefix_config_h.m4 causes files to be left after "make distclean"
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: Multiple subdirectories with non-similar configure needs
  • From: Harlan Stenn <stenn@xxxxxxx>
• Re: Multiple subdirectories with non-similar configure needs
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: Multiple subdirectories with non-similar configure needs
  • From: Harlan Stenn <stenn@xxxxxxx>
• Re: Multiple subdirectories with non-similar configure needs
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: Multiple subdirectories with non-similar configure needs
  • From: Harlan Stenn <stenn@xxxxxxx>
• Re: Multiple subdirectories with non-similar configure needs
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: autocache
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: arm gcc 4.1.3 -O2 dead code removal breaks configure test
  • From: Dave Hart <hart@xxxxxxx>
• Re: arm gcc 4.1.3 -O2 dead code removal breaks configure test
  • From: Dave Hart <hart@xxxxxxx>
• Re: arm gcc 4.1.3 -O2 dead code removal breaks configure test
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: arm gcc 4.1.3 -O2 dead code removal breaks configure test
  • From: "Andrew W. Nosenko" <andrew.w.nosenko@xxxxxxxxx>
• Re: Multiple subdirectories with non-similar configure needs
  • From: Harlan Stenn <stenn@xxxxxxx>
• Re: Multiple subdirectories with non-similar configure needs
  • From: Ralf Corsepius <rc040203@xxxxxxxxxx>
• Re: arm gcc 4.1.3 -O2 dead code removal breaks configure test
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: Multiple subdirectories with non-similar configure needs
  • From: Jim Galarowicz <jeg@xxxxxxxxxxxxx>
• Re: arm gcc 4.1.3 -O2 dead code removal breaks configure test
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: Multiple subdirectories with non-similar configure needs
  • From: Stefano Lattarini <stefano.lattarini@xxxxxxxxx>
• Re: Multiple subdirectories with non-similar configure needs
  • From: NightStrike <nightstrike@xxxxxxxxx>
• Re: Multiple subdirectories with non-similar configure needs
  • From: Jim Galarowicz <jeg@xxxxxxxxxxxxx>
• arm gcc 4.1.3 -O2 dead code removal breaks configure test
  • From: Dave Hart <hart@xxxxxxx>
• Re: Multiple subdirectories with non-similar configure needs
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Multiple subdirectories with non-similar configure needs
  • From: Jim Galarowicz <jeg@xxxxxxxxxxxxx>
• autocache
  • From: ams@xxxxxxx (Alfred M. Szmidt)
• Re: ax_prefix_config_h.m4 causes files to be left after "make distclean"
  • From: David Bruce <davidstuartbruce@xxxxxxxxx>
• Re: deleting config.cache upon CFLAGS variable change
  • From: Eric Blake <eblake@xxxxxxxxxx>
• deleting config.cache upon CFLAGS variable change
  • From: Mathieu Lacage <mathieu.lacage@xxxxxxxxx>
• Re: Broken autoconf mmap test
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: Broken autoconf mmap test
  • From: Ken Brown <kbrown@xxxxxxxxxxx>
• Re: Broken autoconf mmap test
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• Re: Broken autoconf mmap test
  • From: Ken Brown <kbrown@xxxxxxxxxxx>
• Re: Broken autoconf mmap test
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Broken autoconf mmap test
  • From: Ken Brown <kbrown@xxxxxxxxxxx>
• Document conftest.err for AC_LINK_IFELSE, possibly AC_RUN_IFELSE
  • From: Dave Hart <hart@xxxxxxx>
• Re: auto* tools to package for shared library?
  • From: John Calcote <john.calcote@xxxxxxxxx>
• Re: auto* tools to package for shared library?
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• auto* tools to package for shared library?
  • From: Paul Elliott <pelliott@xxxxxxxxxxxxxxxxxxx>
• Re: autoconf 2.68 errors
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• autoconf 2.68 errors
  • From: Naresh Kumar Panthangi <kumarnaresh.p@xxxxxxxxx>
• Re: checking twice the same library with AC_CHECK_LIB
  • From: Vincent Torri <vtorri@xxxxxxxxxxxx>
• Re: checking twice the same library with AC_CHECK_LIB
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: checking twice the same library with AC_CHECK_LIB
  • From: Peter Breitenlohner <peb@xxxxxxxxxxxx>
• Re: checking twice the same library with AC_CHECK_LIB
  • From: Vincent Torri <vtorri@xxxxxxxxxxxx>
• Re: checking twice the same library with AC_CHECK_LIB
  • From: Eric Blake <eblake@xxxxxxxxxx>
• checking twice the same library with AC_CHECK_LIB
  • From: Vincent Torri <vtorri@xxxxxxxxxxxx>
• Re: Keep variable un-expanded in configure script
  • From: "Too, Justin A." <too1@xxxxxxxx>
• Re: Keep variable un-expanded in configure script
  • From: Andres Perera <andres.p@xxxxxxxx>
• Re: Keep variable un-expanded in configure script
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: Keep variable un-expanded in configure script
  • From: Andres Perera <andres.p@xxxxxxxx>
• Re: Keep variable un-expanded in configure script
  • From: "Too, Justin A." <too1@xxxxxxxx>
• Re: Keep variable un-expanded in configure script
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: Keep variable un-expanded in configure script
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Keep variable un-expanded in configure script
  • From: "Too, Justin A." <too1@xxxxxxxx>
• Re: What is "ac_nonexistent.h"?
  • From: NightStrike <nightstrike@xxxxxxxxx>
• Re: How do parallel builds scale?
  • From: ludovic.courtes@xxxxxxxx (Ludovic Courtès)
• Re: How do parallel builds scale?
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• Re: How do parallel builds scale?
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: What is "ac_nonexistent.h"?
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: How do parallel builds scale?
  • From: ludovic.courtes@xxxxxxxx (Ludovic Courtès)
• Re: What is "ac_nonexistent.h"?
  • From: Eric Blake <eblake@xxxxxxxxxx>
• What is "ac_nonexistent.h"?
  • From: 杨勇勇 <yyymiss@xxxxxxxx>
• Re: How do parallel builds scale?
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: How do parallel builds scale?
  • From: ludovic.courtes@xxxxxxxx (Ludovic Courtès)
• Re: How do parallel builds scale?
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• Re: How do parallel builds scale?
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: Setting external directory in ./configure --options
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Setting external directory in ./configure --options
  • From: Xochitl Lunde <Xochitl_Lunde@xxxxxxxxxxxxx>
• Re: How do parallel builds scale?
  • From: Howard Chu <hyc@xxxxxxxxxxxxxxx>
• How do parallel builds scale?
  • From: ludo@xxxxxxx (Ludovic Courtès)
• Re: /var/cache/ccache/tmp
  • From: Eric Blake <eblake@xxxxxxxxxx>
• /var/cache/ccache/tmp
  • From: don-sourceforge-xxz@xxxxxxxxxxxxxxxx (Don Cohen)
• Re: Version number constructed with m4_esyscmd not a literal?
  • From: "Gary V. Vaughan" <gary@xxxxxxx>
• Version number constructed with m4_esyscmd not a literal?
  • From: Marko Lindqvist <cazfi74@xxxxxxxxx>
• Re: Testsuite 147,148,149,150
  • From: "Tadeus (Eus) Prastowo" <0x657573@xxxxxxxxxxxxxx>
• Re: Testsuite 147,148,149,150
  • From: "Tadeus (Eus) Prastowo" <0x657573@xxxxxxxxxxxxxx>
• Re: Testsuite 147,148,149,150
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: Testsuite 147,148,149,150
  • From: "Tadeus (Eus) Prastowo" <0x657573@xxxxxxxxxxxxxx>
• Re: Testsuite 147,148,149,150
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: Testsuite 147,148,149,150
  • From: "Tadeus (Eus) Prastowo" <0x657573@xxxxxxxxxxxxxx>
• Re: Testsuite 147,148,149,150
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: Testsuite 147,148,149,150
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Testsuite 147,148,149,150
  • From: "Tadeus (Eus) Prastowo" <0x657573@xxxxxxxxxxxxxx>
• Invitation to connect on LinkedIn
  • From: Lyre Li <4179e1@xxxxxxxxx>
• Re: AC_OPENMP broken for IBM xl Fortran compilers
  • From: Christian Rössel <christian.roessel@xxxxxx>
• Re: AC_OPENMP broken for IBM xl Fortran compilers
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• AC_OPENMP broken for IBM xl Fortran compilers
  • From: Christian Rössel <christian.roessel@xxxxxx>
• Re: configure -C by default?
  • From: Steffen Dettmer <steffen.dettmer@xxxxxxxxxxxxxx>
• Re: autoconf suggestion
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: bug#8044: Automake should support autotest-based testsuites.
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: bug#8044: Automake should support autotest-based testsuites.
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: Paralizing configure
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• debbugs, and a FAQ, for Autotools
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: Detect Cross Compiler
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: AC_SUBST(CCLD)
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: Update GTK+ autotools configuration
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: configure.ac vs configure.in
  • From: Ralf Corsepius <rc040203@xxxxxxxxxx>
• configure.ac vs configure.in
  • From: Reuben Hawkins <reubenhwk@xxxxxxxxx>
• Re: What shells fail to work if comparing with "" ?
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• Re: Update GTK+ autotools configuration
  • From: Javier Jardón <javierjc1982@xxxxxxxxx>
• Re: AM_COND_IF with m4_foreach+m4_include
  • From: Dave Goodell <goodell@xxxxxxxxxxx>
• Re: AM_COND_IF with m4_foreach+m4_include
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: What shells fail to work if comparing with "" ?
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: AM_COND_IF with m4_foreach+m4_include
  • From: Eric Blake <eblake@xxxxxxxxxx>
• AM_COND_IF with m4_foreach+m4_include
  • From: Dave Goodell <goodell@xxxxxxxxxxx>
• Re: What shells fail to work if comparing with "" ?
  • From: David Kirkby <david.kirkby@xxxxxxxxxx>
• Re: What shells fail to work if comparing with "" ?
  • From: Stefano Lattarini <stefano.lattarini@xxxxxxxxx>
• Re: What shells fail to work if comparing with "" ?
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: Paralizing configure
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: Use pipe and sed in configure.ac
  • From: "Peter O'Gorman" <peter@xxxxxxxxx>
• Re: Use pipe and sed in configure.ac
  • From: Lyre <4179e1@xxxxxxxxx>
• Re: Use pipe and sed in configure.ac
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: What shells fail to work if comparing with "" ?
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: Use pipe and sed in configure.ac
  • From: "Gary V. Vaughan" <gary@xxxxxxx>
• What shells fail to work if comparing with "" ?
  • From: "Dr. David Kirkby" <david.kirkby@xxxxxxxxxx>
• Re: Use pipe and sed in configure.ac
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: Paralizing configure
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: Use pipe and sed in configure.ac
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Detect Cross Compiler
  • From: "Too, Justin A." <too1@xxxxxxxx>
• Re: Paralizing configure
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• Re: Paralizing configure
  • From: Olaf Lenz <olenz@xxxxxxxxxxxxxxxxxxxx>
• AC_SUBST(CCLD)
  • From: "Too, Justin A." <too1@xxxxxxxx>
• AC_SUBST(CCLD)
  • From: "Too, Justin A." <too1@xxxxxxxx>
• Use pipe and sed in configure.ac
  • From: Lyre <4179e1@xxxxxxxxx>
• Re: autotools presentation (was: Paralizing configure)
  • From: Marian Marinov <mm@xxxxxxxx>
• autotools presentation (was: Paralizing configure)
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: Paralizing configure
  • From: Javier Jardón <javierjc1982@xxxxxxxxx>
• Re: Paralizing configure
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• Re: Paralizing configure
  • From: Peter Rosin <peda@xxxxxxxxxxxxxx>
• Re: Paralizing configure
  • From: Miles Bader <miles@xxxxxxx>
• Re: Paralizing configure
  • From: Peter Rosin <peda@xxxxxxxxxxxxxx>
• Re: Paralizing configure
  • From: Miles Bader <miles@xxxxxxx>
• Re: Paralizing configure
  • From: Ralf Corsepius <rc040203@xxxxxxxxxx>
• Re: Paralizing configure
  • From: Miles Bader <miles@xxxxxxx>
• Re: Paralizing configure
  • From: Marian Marinov <mm@xxxxxxxx>
• Re: Paralizing configure
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: Paralizing configure
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: Paralizing configure
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Paralizing configure
  • From: Marian Marinov <mm@xxxxxxxx>
• Paralization in configure
  • From: Marian Marinov <mm@xxxxxxxx>
• Re: configure -C by default?
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: configure -C by default?
  • From: Vincent Torri <vtorri@xxxxxxxxxxxx>
• Re: Update GTK+ autotools configuration
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: configure -C by default?
  • From: Peter Breitenlohner <peb@xxxxxxxxxxxx>
• Re: configure -C by default?
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: configure -C by default?
  • From: Russell Shaw <rjshaw@xxxxxxxxxxxxxxx>
• Re: configure -C by default?
  • From: Peter Rosin <peda@xxxxxxxxxxxxxx>
• Re: configure -C by default?
  • From: Peter Rosin <peda@xxxxxxxxxxxxxx>
• Re: configure -C by default?
  • From: Brian Gough <bjg@xxxxxxx>
• Re: configure -C by default?
  • From: Ralf Corsepius <rc040203@xxxxxxxxxx>
• Re: configure -C by default?
  • From: Ralf Corsepius <rc040203@xxxxxxxxxx>
• Re: configure -C by default?
  • From: Ralf Corsepius <rc040203@xxxxxxxxxx>
• Re: configure -C by default?
  • From: Ralf Corsepius <rc040203@xxxxxxxxxx>
• Re: configure -C by default?
  • From: Miles Bader <miles@xxxxxxx>
• hierarchical config.site from distros? (was: configure -C by default?)
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Update GTK+ autotools configuration
  • From: Javier Jardón <jjardon@xxxxxxxxx>
• configure -C by default?
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Update GTK+ autotools configuration
  • From: Javier Jardón <javierjc1982@xxxxxxxxx>
• Re: HAVE_STDBOOL_H, AC_HEADER_STDBOOL, and AM_STDBOOL_H
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: Passing flags to Makefile.ac's in subdirs
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: Passing flags to Makefile.ac's in subdirs
  • From: dzinoviev <dmitry@xxxxxxxxxxxxxxx>
• Re: Passing flags to Makefile.ac's in subdirs
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Passing flags to Makefile.ac's in subdirs
  • From: dzinoviev <dmitry@xxxxxxxxxxxxxxx>
• Re: flags for different fortran compilers
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: flags for different fortran compilers
  • From: Eve-Marie Devaliere <Eve-Marie.Devaliere@xxxxxxxx>
• Re: produce *mod with fortran
  • From: Eve-Marie Devaliere <Eve-Marie.Devaliere@xxxxxxxx>
• Re: flags for different fortran compilers
  • From: Eve-Marie Devaliere <Eve-Marie.Devaliere@xxxxxxxx>
• Re: HAVE_STDBOOL_H, AC_HEADER_STDBOOL, and AM_STDBOOL_H
  • From: Simon Josefsson <simon@xxxxxxxxxxxxx>
• Re: produce *mod with fortran
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: produce *mod with fortran
  • From: Eve-Marie Devaliere <Eve-Marie.Devaliere@xxxxxxxx>
• Re: flags for different fortran compilers
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: flags for different fortran compilers
  • From: Eve-Marie Devaliere <Eve-Marie.Devaliere@xxxxxxxx>
• Re: HAVE_STDBOOL_H, AC_HEADER_STDBOOL, and AM_STDBOOL_H
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: HAVE_STDBOOL_H, AC_HEADER_STDBOOL, and AM_STDBOOL_H
  • From: Russ Allbery <rra@xxxxxxxxxxxx>
• Re: HAVE_STDBOOL_H, AC_HEADER_STDBOOL, and AM_STDBOOL_H
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: HAVE_STDBOOL_H, AC_HEADER_STDBOOL, and AM_STDBOOL_H
  • From: Simon Josefsson <simon@xxxxxxxxxxxxx>
• Re: HAVE_STDBOOL_H, AC_HEADER_STDBOOL, and AM_STDBOOL_H
  • From: Ralf Corsepius <ralf.corsepius@xxxxxxxxx>
• Re: HAVE_STDBOOL_H, AC_HEADER_STDBOOL, and AM_STDBOOL_H
  • From: Russ Allbery <rra@xxxxxxxxxxxx>
• Re: HAVE_STDBOOL_H, AC_HEADER_STDBOOL, and AM_STDBOOL_H
  • From: Eric Blake <eblake@xxxxxxxxxx>
• HAVE_STDBOOL_H, AC_HEADER_STDBOOL, and AM_STDBOOL_H
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: flags for different fortran compilers
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: produce *mod with fortran
  • From: Eve-Marie Devaliere <Eve-Marie.Devaliere@xxxxxxxx>
• Re: Problems when using an alternative autotools installation
  • From: Jim Galarowicz <jeg@xxxxxxxxxxxxx>
• Re: Problems when using an alternative autotools installation
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: Problems when using an alternative autotools installation
  • From: Jim Galarowicz <jeg@xxxxxxxxxxxxx>
• Re: produce *mod with fortran
  • From: Christopher Hulbert <cchgroupmail@xxxxxxxxx>
• Re: Problems when using an alternative autotools installation
  • From: Peter Breitenlohner <peb@xxxxxxxxxxxx>
• Problems when using an alternative autotools installation
  • From: Jim Galarowicz <jeg@xxxxxxxxxxxxx>
• Re: produce *mod with fortran
  • From: Eve-Marie Devaliere <Eve-Marie.Devaliere@xxxxxxxx>
• flags for different fortran compilers
  • From: Eve-Marie Devaliere <Eve-Marie.Devaliere@xxxxxxxx>
• Re: AT_CHECK within for loop
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: echo arbitrary text in autotest?
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: AT_CHECK within for loop
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: AT_CHECK within for loop
  • From: "Joel E. Denny" <joeldenny@xxxxxxxxxxxxx>
• echo arbitrary text in autotest?
  • From: "Daily, Jeff A" <jeff.daily@xxxxxxx>
• Re: AT_CHECK within for loop
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: AT_CHECK within for loop
  • From: "Joel E. Denny" <joeldenny@xxxxxxxxxxxxx>
• Re: AT_CHECK within for loop
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: AT_CHECK within for loop
  • From: "Joel E. Denny" <joeldenny@xxxxxxxxxxxxx>
• Re: AT_CHECK within for loop
  • From: Eric Blake <eblake@xxxxxxxxxxxxxx>
• AT_CHECK within for loop
  • From: "Daily, Jeff A" <jeff.daily@xxxxxxx>
• Re: make test with fortran programs
  • From: Eve-Marie Devaliere <Eve-Marie.Devaliere@xxxxxxxx>
• Re: make test with fortran programs
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: make test with fortran programs
  • From: Eve-Marie Devaliere <Eve-Marie.Devaliere@xxxxxxxx>
• Re: Check for global symbol
  • From: Sergio Belkin <sebelk@xxxxxxxxx>
• Re: Check for global symbol
  • From: tom fogal <tfogal@xxxxxxxxxxxx>
• Re: make test
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: Check for global symbol
  • From: "Peter O'Gorman" <peter@xxxxxxxxx>
• Re: Check for global symbol
  • From: tom fogal <tfogal@xxxxxxxxxxxx>
• Check for global symbol
  • From: Sergio Belkin <sebelk@xxxxxxxxx>
• Re: make test
  • From: Eve-Marie Devaliere <Eve-Marie.Devaliere@xxxxxxxx>
• Re: make test
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: make test
  • From: Frank Lahm <franklahm@xxxxxxxxxxxxxx>
• make test
  • From: Eve-Marie Devaliere <Eve-Marie.Devaliere@xxxxxxxx>
• Re: linking to Fortran libraries from C fails with suncc and sunf90
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: Configure Fail
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Configure Fail
  • From: aaliya zarrin <aaliya.zarrin@xxxxxxxxx>
• Re: Override default CXXFLAGS
  • From: Richard Ash <richard@xxxxxxxxxxxxxxxx>
• Re: Override default CXXFLAGS
  • From: Ralf Corsepius <rc040203@xxxxxxxxxx>
• Re: Override default CXXFLAGS
  • From: Sergio Belkin <sebelk@xxxxxxxxx>
• Override default CXXFLAGS
  • From: Sergio Belkin <sebelk@xxxxxxxxx>
• RE: linking to Fortran libraries from C fails with suncc and sunf90
  • From: "Daily, Jeff A" <jeff.daily@xxxxxxx>
• Re: linking to Fortran libraries from C fails with suncc and sunf90
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• linking to Fortran libraries from C fails with suncc and sunf90
  • From: "Daily, Jeff A" <jeff.daily@xxxxxxx>
• Re: Help with path expansion
  • From: John Calcote <john.calcote@xxxxxxxxx>
• Re: Help with path expansion
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Help with path expansion
  • From: Mike Gran <spk121@xxxxxxxxx>
• Re: produce *mod with fortran
  • From: Christopher Hulbert <cchgroupmail@xxxxxxxxx>
• Re: produce *mod with fortran
  • From: Eve-Marie Devaliere <Eve-Marie.Devaliere@xxxxxxxx>
• Re: Enforcing cross-compilation
  • From: David Nečas <yeti@xxxxxxxxxxxxxxx>
• Re: produce *mod with fortran
  • From: Christopher Hulbert <cchgroupmail@xxxxxxxxx>
• Re: produce *mod with fortran
  • From: Anthony Chan <chan@xxxxxxxxxxx>
• Re: produce *mod with fortran
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: produce *mod with fortran
  • From: Eve-Marie Devaliere <Eve-Marie.Devaliere@xxxxxxxx>
• Re: produce *mod with fortran
  • From: Eve-Marie Devaliere <Eve-Marie.Devaliere@xxxxxxxx>
• Re: produce *mod with fortran
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: produce *mod with fortran
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: produce *mod with fortran
  • From: Eve-Marie Devaliere <Eve-Marie.Devaliere@xxxxxxxx>
• Re: produce *mod with fortran
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: ax_prefix_config_h.m4 causes files to be left after "make distclean"
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: produce *mod with fortran
  • From: Eve-Marie Devaliere <Eve-Marie.Devaliere@xxxxxxxx>
• produce *mod with fortran
  • From: Eve-Marie Devaliere <Eve-Marie.Devaliere@xxxxxxxx>
• Re: ax_prefix_config_h.m4 causes files to be left after "make distclean"
  • From: Steffen Dettmer <steffen.dettmer@xxxxxxxxxxxxxx>
• Re: Macro for compile, run, and return output
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: ax_prefix_config_h.m4 causes files to be left after "make distclean"
  • From: David Bruce <davidstuartbruce@xxxxxxxxx>
• Re: ax_prefix_config_h.m4 causes files to be left after "make distclean"
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: Enforcing cross-compilation
  • From: Robert Woodworth <robertjwoodworth@xxxxxxxxx>
• Re: Enforcing cross-compilation
  • From: Nick Bowler <nbowler@xxxxxxxxxxxxxxxx>
• Re: Enforcing cross-compilation
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: [autoconf] Enforcing cross-compilation
  • From: suzuki toshiya <mpsuzuki@xxxxxxxxxxxxxxxxx>
• Enforcing cross-compilation
  • From: David Nečas <yeti@xxxxxxxxxxxxxxx>
• Macro for compile, run, and return output
  • From: Lyle Brooks <brooks@xxxxxxxxxxx>
• Re: ax_prefix_config_h.m4 causes files to be left after "make distclean"
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: ax_prefix_config_h.m4 causes files to be left after "make distclean"
  • From: David Bruce <davidstuartbruce@xxxxxxxxx>
• Re: newbie - autoscan for f90
  • From: Eric Blake <eblake@xxxxxxxxxx>
• newbie - autoscan for f90
  • From: Eve-Marie Devaliere <Eve-Marie.Devaliere@xxxxxxxx>
• Re: ax_prefix_config_h.m4 causes files to be left after "make distclean"
  • From: Rhys Ulerich <rhys.ulerich@xxxxxxxxx>
• ax_prefix_config_h.m4 causes files to be left after "make distclean"
  • From: David Bruce <davidstuartbruce@xxxxxxxxx>
• Re: Bison
  • From: David Fang <fang@xxxxxxxxxxxxxxx>
• Re: Bison
  • From: Russell Shaw <rjshaw@xxxxxxxxxxxxxxx>
• Re: Bison
  • From: John Calcote <john.calcote@xxxxxxxxx>
• Re: Bison
  • From: tom fogal <tfogal@xxxxxxxxxxxx>
• Bison
  • From: Russell Shaw <rjshaw@xxxxxxxxxxxxxxx>
• Re: Best practice for user decided unusual library paths ?
  • From: Johan Persson <johanp@xxxxxxxxx>
• Re: Best practice for user decided unusual library paths ?
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Best practice for user decided unusual library paths ?
  • From: Johan Persson <johanp@xxxxxxxxx>
• Re: fatal: ambiguous message
  • From: Bruce Korb <bruce.korb@xxxxxxxxx>
• Re: fatal: ambiguous message
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: fatal: ambiguous message
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: fatal: ambiguous message
  • From: Jonathan Nieder <jrnieder@xxxxxxxxx>
• Re: fatal: ambiguous message
  • From: Bruce Korb <bruce.korb@xxxxxxxxx>
• Re: fatal: ambiguous message
  • From: Bruce Korb <bruce.korb@xxxxxxxxx>
• Re: fatal: ambiguous message
  • From: Bruce Korb <bruce.korb@xxxxxxxxx>
• Re: fatal: ambiguous message
  • From: Eric Blake <eblake@xxxxxxxxxx>
• fatal: ambiguous message
  • From: Bruce Korb <bruce.korb@xxxxxxxxx>
• Re: linkat, LINK_FOLLOWS_SYMLINKS, and Solaris
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: -xc99=all and libraries on Solaris 10
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: linkat, LINK_FOLLOWS_SYMLINKS, and Solaris
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: -xc99=all and libraries on Solaris 10
  • From: "Peter O'Gorman" <pogma@xxxxxxxxxxxxxxxxxx>
• Re: linkat, LINK_FOLLOWS_SYMLINKS, and Solaris
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• Re: linkat, LINK_FOLLOWS_SYMLINKS, and Solaris
  • From: Bruno Haible <bruno@xxxxxxxxx>
• Re: linkat, LINK_FOLLOWS_SYMLINKS, and Solaris
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: -xc99=all and libraries on Solaris 10
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• Re: -xc99=all and libraries on Solaris 10
  • From: Bruno Haible <bruno@xxxxxxxxx>
• Re: Macro to add more compiler warnings
  • From: Stefano Lattarini <stefano.lattarini@xxxxxxxxx>
• Macro to add more compiler warnings
  • From: Javier Jardón <javierjc1982@xxxxxxxxx>
• Re: AW: MPI recognition
  • From: Olaf Lenz <olenz@xxxxxxxxxxxxxxxxxxxx>
• AW: MPI recognition
  • From: "Carsten Heinrici" <carsten@xxxxxxxxxxxx>
• Re: How does one specify linking to 64 bit libraries when there is a choice?
  • From: Ralf Corsepius <rc040203@xxxxxxxxxx>
• Re: MPI recognition
  • From: Olaf Lenz <olenz@xxxxxxxxxxxxxxxxxxxx>
• Re: How does one specify linking to 64 bit libraries when there is a choice?
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: MPI recognition
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: Question about AC_TRY_LINK_FUNC
  • From: Sergio Belkin <sebelk@xxxxxxxxx>
• Re: MPI recognition
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: MPI recognition
  • From: Olaf Lenz <olenz@xxxxxxxxxxxxxxxxxxxx>
• Re: Question about AC_TRY_LINK_FUNC
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Question about AC_TRY_LINK_FUNC
  • From: Sergio Belkin <sebelk@xxxxxxxxx>
• MPI recognition
  • From: Olaf Lenz <olenz@xxxxxxxxxxxxxxxxxxxx>
• Re: How does one specify linking to 64 bit libraries when there is a choice?
  • From: Bruce Korb <bruce.korb@xxxxxxxxx>
• Re: How does one specify linking to 64 bit libraries when there is a choice?
  • From: Bruce Korb <bkorb@xxxxxxx>
• Re: How does one specify linking to 64 bit libraries when there is a choice?
  • From: "Peter O'Gorman" <peter@xxxxxxxxx>
• Re: How does one specify linking to 64 bit libraries when there is a choice?
  • From: Nick Bowler <nbowler@xxxxxxxxxxxxxxxx>
• Re: How does one specify linking to 64 bit libraries when there is a choice?
  • From: Bruce Korb <bkorb@xxxxxxx>
• Re: How does one specify linking to 64 bit libraries when there is a choice?
  • From: Ralf Corsepius <rc040203@xxxxxxxxxx>
• Re: How does one specify linking to 64 bit libraries when there is a choice?
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: How does one specify linking to 64 bit libraries when there is a choice?
  • From: Ralf Corsepius <rc040203@xxxxxxxxxx>
• Re: How does one specify linking to 64 bit libraries when there is a choice?
  • From: Ralf Corsepius <rc040203@xxxxxxxxxx>
• Re: How does one specify linking to 64 bit libraries when there is a choice?
  • From: Ralf Corsepius <rc040203@xxxxxxxxxx>
• Re: How does one specify linking to 64 bit libraries when there is a choice?
  • From: Peter Breitenlohner <peb@xxxxxxxxxxxx>
• Re: How does one specify linking to 64 bit libraries when there is a choice?
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: How does one specify linking to 64 bit libraries when there is a choice?
  • From: Bruce Korb <bkorb@xxxxxxx>
• Re: Lost commit
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Lost commit
  • From: Andreas Schwab <schwab@xxxxxxxxxxxxxx>
• Positioning code from first expansion of AC_CHECK_HEADER
  • From: JFii <John.Field@xxxxxxxxxxxx>
• Re: Arithmetic Shift
  • From: "Andrew W. Nosenko" <andrew.w.nosenko@xxxxxxxxx>
• Re: Arithmetic Shift
  • From: "Andrew W. Nosenko" <andrew.w.nosenko@xxxxxxxxx>
• Re: Arithmetic Shift
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: Arithmetic Shift
  • From: "Andrew W. Nosenko" <andrew.w.nosenko@xxxxxxxxx>
• Re: Arithmetic Shift
  • From: "Andrew W. Nosenko" <andrew.w.nosenko@xxxxxxxxx>
• Re: Arithmetic Shift
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• Re: Arithmetic Shift
  • From: Ben Pfaff <blp@xxxxxxxxxxxxxxx>
• Re: Arithmetic Shift
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: Arithmetic Shift
  • From: Dave Goodell <goodell@xxxxxxxxxxx>
• Re: Arithmetic Shift
  • From: Ben Pfaff <blp@xxxxxxxxxxxxxxx>
• Re: Arithmetic Shift
  • From: "Andrew W. Nosenko" <andrew.w.nosenko@xxxxxxxxx>
• Re: Arithmetic Shift
  • From: Peter Breitenlohner <peb@xxxxxxxxxxxx>
• Re: Arithmetic Shift
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: Arithmetic Shift
  • From: "Andrew W. Nosenko" <andrew.w.nosenko@xxxxxxxxx>
• Re: Arithmetic Shift
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: Arithmetic Shift
  • From: Mike Gibson <megibson@xxxxxxxxx>
• Re: Arithmetic Shift
  • From: Philip Herron <redbrain@xxxxxxxxxxx>
• Re: Arithmetic Shift
  • From: Mike Gibson <megibson@xxxxxxxxx>
• Invalid expansion of AC_CHECK_FUNCS in 2.64+?
  • From: autoconf@xxxxxxxxxxxxxxxxx
• Arithmetic Shift
  • From: Mike Gibson <megibson@xxxxxxxxx>
• Re: Fwd: [Bug 347095] installing m4 macros that break random packages
  • From: Bruce Korb <bkorb@xxxxxxx>
• Re: Fwd: [Bug 347095] installing m4 macros that break random packages
  • From: Mike Frysinger <vapier@xxxxxxxxxx>
• Re: Fwd: [Bug 347095] installing m4 macros that break random packages
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: Fwd: [Bug 347095] installing m4 macros that break random packages
  • From: Bruce Korb <bkorb@xxxxxxx>
• Re: Fwd: [Bug 347095] installing m4 macros that break random packages
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Fwd: [Bug 347095] installing m4 macros that break random packages
  • From: Bruce Korb <bkorb@xxxxxxx>
• Re: How to best prevent autoreconf from recursing into a subdir
  • From: Ralf Corsepius <rc040203@xxxxxxxxxx>
• Re: How to best prevent autoreconf from recursing into a subdir
  • From: Peter Breitenlohner <peb@xxxxxxxxxxxx>
• Re: How to best prevent autoreconf from recursing into a subdir
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• How to best prevent autoreconf from recursing into a subdir
  • From: Peter Breitenlohner <peb@xxxxxxxxxxxx>
• Re: autotest: problem testing daemons, with possible fix
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: autotest: problem testing daemons, with possible fix
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: autotest: problem testing daemons, with possible fix
  • From: Paolo Bonzini <bonzini@xxxxxxx>
• Re: autotest: problem testing daemons, with possible fix
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: autotest: problem testing daemons, with possible fix
  • From: Luke Mewburn <lukem@xxxxxxxxxx>
• Re: autotest: problem testing daemons, with possible fix
  • From: Luke Mewburn <lukem@xxxxxxxxxx>
• Re: autotest: problem testing daemons, with possible fix
  • From: "Andrew W. Nosenko" <andrew.w.nosenko@xxxxxxxxx>
• Re: autotest: problem testing daemons, with possible fix
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• autotest: problem testing daemons, with possible fix
  • From: Luke Mewburn <lukem@xxxxxxxxxx>
• Re: How to test a particular <lib>X11 feature ?
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• How to test a particular <lib>X11 feature ?
  • From: Konstantin Andreev <andreev@xxxxxxxxx>
• Re: Qt4 autoconf macros
  • From: Alberto Luaces <aluaces@xxxxxx>
• Re: Default host other than local system
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: Detecting an adequate id program
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: Detecting an adequate id program
  • From: Michael Grünewald <michael.grunewald@xxxxxxxxxxx>
• Re: Detecting an adequate id program
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Detecting an adequate id program
  • From: Michael Grünewald <michael.grunewald@xxxxxxxxxxx>
• Re: Default host other than local system
  • From: Robert Woodworth <robertjwoodworth@xxxxxxxxx>
• Re: Default host other than local system
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: Default host other than local system
  • From: Robert Woodworth <robertjwoodworth@xxxxxxxxx>
• Re: exec 0</dev/null vs. nohup?
  • From: Ralf <ralf.wildenhues@xxxxxx>
• Re: exec 0</dev/null vs. nohup?
  • From: Eric Blake <eblake@xxxxxxxxxx>
• RE: exec 0</dev/null vs. nohup?
  • From: Jay K <jay.krell@xxxxxxxxxxx>
• Re: SRPMs and RHEL 5/6 and SLES 11
  • From: Jeff Squyres <jsquyres@xxxxxxxxx>
• Re: SRPMs and RHEL 5/6 and SLES 11
  • From: Eric Blake <eblake@xxxxxxxxxx>
• SRPMs and RHEL 5/6 and SLES 11
  • From: Jeff Squyres <jsquyres@xxxxxxxxx>
• Re: minimum m4 version
  • From: Adam Mercer <ramercer@xxxxxxxxx>
• Re: minimum m4 version
  • From: "Gary V. Vaughan" <gary@xxxxxxx>
• minimum m4 version
  • From: Adam Mercer <ramercer@xxxxxxxxx>
• Re: best way to check for compiler _warnings_?
  • From: Peter Rosin <peda@xxxxxxxxxxxxxx>
• Re: best way to check for compiler _warnings_?
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: best way to check for compiler _warnings_?
  • From: Miles Bader <miles@xxxxxxx>
• Re: best way to check for compiler _warnings_?
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: best way to check for compiler _warnings_?
  • From: Miles Bader <miles@xxxxxxx>
• Re: best way to check for compiler _warnings_?
  • From: Peter Rosin <peda@xxxxxxxxxxxxxx>
• Re: best way to check for compiler _warnings_?
  • From: Miles Bader <miles@xxxxxxx>
• Re: best way to check for compiler _warnings_?
  • From: Peter Rosin <peda@xxxxxxxxxxxxxx>
• Re: best way to check for compiler _warnings_?
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: best way to check for compiler _warnings_?
  • From: "Joseph S. Myers" <joseph@xxxxxxxxxxxxxxxx>
• Re: best way to check for compiler _warnings_?
  • From: Miles Bader <miles@xxxxxxx>
• Re: best way to check for compiler _warnings_?
  • From: Miles Bader <miles@xxxxxxx>
• Re: Problem with LIBS generated by a macro
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: best way to check for compiler _warnings_?
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: question about AC_STRUCT_DIRENT_D_TYPE
  • From: Eric Blake <eblake@xxxxxxxxxx>
• best way to check for compiler _warnings_?
  • From: Miles Bader <miles@xxxxxxx>
• Re: Problem with LIBS generated by a macro
  • From: Sergio Belkin <sebelk@xxxxxxxxx>
• Re: Problem with LIBS generated by a macro
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Problem with LIBS generated by a macro
  • From: Sergio Belkin <sebelk@xxxxxxxxx>
• question about AC_STRUCT_DIRENT_D_TYPE
  • From: Vincent Torri <vtorri@xxxxxxxxxxxx>
• Re: using autoconf with ppuxlc++,spuxlc++
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: using autoconf with ppuxlc++,spuxlc++
  • From: John Wohlbier <johnwohlbier@xxxxxxxxx>
• using autoconf with ppuxlc++,spuxlc++
  • From: John Wohlbier <johnwohlbier@xxxxxxxxx>
• Re: Use resolution file, autoconf help needed
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: could not setup config headers machinery
  • From: "Dr. David Kirkby" <david.kirkby@xxxxxxxxxx>
• Use resolution file, autoconf help needed
  • From: Jan Hubicka <hubicka@xxxxxx>
• Re: Use resolution file, autoconf help needed
  • From: Jan Hubicka <hubicka@xxxxxx>
• Re: Use resolution file, autoconf help needed
  • From: Paolo Bonzini <bonzini@xxxxxxx>
• Re: could not setup config headers machinery
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: could not setup config headers machinery
  • From: "Dr. David Kirkby" <david.kirkby@xxxxxxxxxx>
• Re: AC_CHECK_LIB: Library is found on build host but is not on a target host
  • From: Sergio Belkin <sebelk@xxxxxxxxx>
• Re: Qt4 autoconf macros
  • From: santilistas <listas@xxxxxxxxxxxx>
• Re: AC_CHECK_LIB: Library is found on build host but is not on a target host
  • From: Sergio Belkin <sebelk@xxxxxxxxx>
• Re: AC_SEARCH_LIBS directories on 32-bit and 64-bit
  • From: Sergio Belkin <sebelk@xxxxxxxxx>
• Re: AC_CHECK_LIB: Library is found on build host but is not on a target host
  • From: Sergio Belkin <sebelk@xxxxxxxxx>
• Re: Qt4 autoconf macros
  • From: Christian Rössel <c.roessel@xxxxxxxxxxxxx>
• Qt4 autoconf macros
  • From: santilin <santi@xxxxxxxxxxxx>
• Re: inadvisable to have configure script send me an email when user runs it?
  • From: Steffen Dettmer <steffen.dettmer@xxxxxxxxxxxxxx>
• Re: inadvisable to have configure script send me an email when user runs it?
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• Re: inadvisable to have configure script send me an email when user runs it?
  • From: Miles Bader <miles@xxxxxxx>
• Re: Qt4 autoconf macros
  • From: Frederik Heber1 <heber@xxxxxxxxxxxxxxx>
• Qt4 autoconf macros
  • From: santilistas <listas@xxxxxxxxxxxx>
• Re: AC_SEARCH_LIBS directories on 32-bit and 64-bit
  • From: Eric Blake <eblake@xxxxxxxxxx>
• AC_SEARCH_LIBS directories on 32-bit and 64-bit
  • From: Sergio Belkin <sebelk@xxxxxxxxx>
• Re: inadvisable to have configure script send me an email when user runs it?
  • From: Eric Blake <eblake@xxxxxxxxxx>
• inadvisable to have configure script send me an email when user runs it?
  • From: Ed Hartnett <ed@xxxxxxxxxxxxxxxx>
• Re: Testing for GCC-like attributes and compiler switches
  • From: Peter Rosin <peda@xxxxxxxxxxxxxx>
• Re: Testing for GCC-like attributes and compiler switches
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: Testing for GCC-like attributes and compiler switches
  • From: Václav Haisman <v.haisman@xxxxxxxxxx>
• Re: Testing for GCC-like attributes and compiler switches
  • From: "Andrew W. Nosenko" <andrew.w.nosenko@xxxxxxxxx>
• Re: Testing for GCC-like attributes and compiler switches
  • From: "Andrew W. Nosenko" <andrew.w.nosenko@xxxxxxxxx>
• Re: Testing for GCC-like attributes and compiler switches
  • From: Mike Frysinger <vapier@xxxxxxxxxx>
• Testing for GCC-like attributes and compiler switches
  • From: Václav Haisman <v.haisman@xxxxxxxxxx>
• Re: Macro to obtain kind parameter value in F90?
  • From: Rhys Ulerich <rhys.ulerich@xxxxxxxxx>
• Re: Overriding LN_S
  • From: Peter Rosin <peda@xxxxxxxxxxxxxx>
• Re: could not setup config headers machinery
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: AC_INIT bug-address question
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: AC_INIT bug-address question
  • From: Miles Bader <miles@xxxxxxx>
• Re: AC_INIT bug-address question
  • From: Miles Bader <miles@xxxxxxx>
• Re: AC_INIT bug-address question
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: AC_INIT bug-address question
  • From: Miles Bader <miles@xxxxxxx>
• Re: AC_INIT bug-address question
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: AC_INIT bug-address question
  • From: Eric Blake <eblake@xxxxxxxxxx>
• AC_INIT bug-address question
  • From: Miles Bader <miles@xxxxxxx>
• Re: could not setup config headers machinery
  • From: "Dr. David Kirkby" <david.kirkby@xxxxxxxxxx>
• could not setup config headers machinery
  • From: "Dr. David Kirkby" <david.kirkby@xxxxxxxxxx>
• Re: Macro to obtain kind parameter value in F90?
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: ac_configure_args
  • From: Sam Steingold <sds@xxxxxxx>
• Re: ac_configure_args
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: ac_configure_args
  • From: Sam Steingold <sds@xxxxxxx>
• Macro to obtain kind parameter value in F90?
  • From: Rhys Ulerich <rhys.ulerich@xxxxxxxxx>
• Re: Short Help Macro for configure
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Short Help Macro for configure
  • From: Sergio Belkin <sebelk@xxxxxxxxx>
• Re: [PATCH] Trace macros for aclocal options, deprecate ACLOCAL_AMFLAGS.
  • From: Stefano Lattarini <stefano.lattarini@xxxxxxxxx>
• Re: ac_configure_args
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: ac_configure_args
  • From: Sam Steingold <sds@xxxxxxx>
• Re: [PATCH] Trace macros for aclocal options, deprecate ACLOCAL_AMFLAGS.
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: [PATCH] Trace macros for aclocal options, deprecate ACLOCAL_AMFLAGS.
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: Why doesn't config.log quote invocation command line?
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: Why doesn't config.log quote invocation command line?
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• Re: Why doesn't config.log quote invocation command line?
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Why doesn't config.log quote invocation command line?
  • From: "Daily, Jeff A" <jeff.daily@xxxxxxx>
• Re: Confirmation my method is right.
  • From: Peter Johansson <trojkan@xxxxxxxxx>
• Re: ac_configure_args
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: Confirmation my method is right.
  • From: "Dr. David Kirkby" <david.kirkby@xxxxxxxxxx>
• Re: ac_configure_args
  • From: Sam Steingold <sds@xxxxxxx>
• Re: ac_configure_args
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• ac_configure_args
  • From: Sam Steingold <sds@xxxxxxx>
• Re: About AC_CHECK_HEADERS and different locations
  • From: "Andrew W. Nosenko" <andrew.w.nosenko@xxxxxxxxx>
• Re: About AC_CHECK_HEADERS and different locations
  • From: "Andrew W. Nosenko" <andrew.w.nosenko@xxxxxxxxx>
• Re: About AC_CHECK_HEADERS and different locations
  • From: Ralf Corsepius <rc040203@xxxxxxxxxx>
• Re: About AC_CHECK_HEADERS and different locations
  • From: "Andrew W. Nosenko" <andrew.w.nosenko@xxxxxxxxx>
• Re: Confirmation my method is right.
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Confirmation my method is right.
  • From: "Dr. David Kirkby" <david.kirkby@xxxxxxxxxx>
• Re: About AC_CHECK_HEADERS and different locations
  • From: Peter Breitenlohner <peb@xxxxxxxxxxxx>
• Re: About AC_CHECK_HEADERS and different locations
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: AC_CHECK_LIB: Library is found on build host but is not on a target host
  • From: Luke Mewburn <lukem@xxxxxxxxxx>
• About AC_CHECK_HEADERS and different locations
  • From: Sergio Belkin <sebelk@xxxxxxxxx>
• Re: AC_CHECK_LIB: Library is found on build host but is not on a target host
  • From: Sergio Belkin <sebelk@xxxxxxxxx>
• Re: AC_CHECK_LIB: Library is found on build host but is not on a target host
  • From: Sergio Belkin <sebelk@xxxxxxxxx>
• Re: New warning with Autoconf 2.68
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• Re: New warning with Autoconf 2.68
  • From: Eric Blake <eblake@xxxxxxxxxx>
• New warning with Autoconf 2.68
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• Re: Documentation correction
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Documentation correction
  • From: Josh <jgh.emc@xxxxxxxxx>
• Re: module libposix
  • From: Bruce Korb <bruce.korb@xxxxxxxxx>
• Re: GNU Autoconf 2.68 released [stable]
  • From: Eric Blake <eblake@xxxxxxxxxx>
• GNU Autoconf 2.68 released [stable]
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: conditional use of PKG_CHECK_MODULES, along with platforms that don't have pkg-config
  • From: Pete Batard <pbatard@xxxxxxxxx>
• Re: conditional use of PKG_CHECK_MODULES, along with platforms that don't have pkg-config
  • From: Eric Blake <eblake@xxxxxxxxxx>
• conditional use of PKG_CHECK_MODULES, along with platforms that don't have pkg-config
  • From: Pete Batard <pbatard@xxxxxxxxx>
• Re: module libposix
  • From: Bruce Korb <bkorb@xxxxxxx>
• Re: help with broken autoconf/m4 macro?
  • From: Eric Blake <eblake@xxxxxxxxxx>
• 'checking ... result' configure lines (was: what is $ac_t ?)
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: what is $ac_t ?
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: what is $ac_t ?
  • From: Sam Steingold <sds@xxxxxxx>
• Re: what is $ac_t ?
  • From: Sam Steingold <sds@xxxxxxx>
• Re: what is $ac_t ?
  • From: Bruno Haible <bruno@xxxxxxxxx>
• Re: what is $ac_t ?
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: what is $ac_t ?
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: what is $ac_t ?
  • From: Eric Blake <eblake@xxxxxxxxxx>
• what is $ac_t ?
  • From: Sam Steingold <sds@xxxxxxx>
• Re: autoconf-2.66 with pkg-config-0.25 problem
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: AC_PROG_INSTALL does not trigger install-sh availability
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: AC_PROG_INSTALL does not trigger install-sh availability
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: AC_PROG_INSTALL does not trigger install-sh availability
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: m4 macro that would call AAC_INIT
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: m4 macro that would call AAC_INIT
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: m4 macro that would call AAC_INIT
  • From: Vincent Torri <vtorri@xxxxxxxxxxxx>
• Re: m4 macro that would call AAC_INIT
  • From: Eric Blake <eblake@xxxxxxxxxx>
• m4 macro that would call AAC_INIT
  • From: Vincent Torri <vtorri@xxxxxxxxxxxx>
• Re: AC_PROG_INSTALL does not trigger install-sh availability
  • From: Eric Blake <eblake@xxxxxxxxxx>
• AC_PROG_INSTALL does not trigger install-sh availability
  • From: Jan Engelhardt <jengelh@xxxxxxxxxx>
• Re: autotest and make distcheck
  • From: Steffen Dettmer <steffen.dettmer@xxxxxxxxxxxxxx>
• Re: autotest and make distcheck
  • From: Andrei Kholodnyi <andrei.kholodnyi@xxxxxxxxx>
• Re: autotest and make distcheck
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: autotest and make distcheck
  • From: Andrei Kholodnyi <andrei.kholodnyi@xxxxxxxxx>
• Re: autotest and make distcheck
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: autotest and make distcheck
  • From: Andrei Kholodnyi <andrei.kholodnyi@xxxxxxxxx>
• Re: autotest and make distcheck
  • From: "Andrew W. Nosenko" <andrew.w.nosenko@xxxxxxxxx>
• autotest and make distcheck
  • From: Andrei Kholodnyi <andrei.kholodnyi@xxxxxxxxx>
• Re: configure error
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: configure error
  • From: sysclock <d4e2cfafbb9f@xxxxxxxxxxxxxxxxxxxxxxxx>
• Re: flex/bison rebuilding issue
  • From: Philip Herron <redbrain@xxxxxxxxxxx>
• Re: flex/bison rebuilding issue
  • From: Eric Blake <eblake@xxxxxxxxxx>
• flex/bison rebuilding issue
  • From: Reuben Hawkins <reubenhwk@xxxxxxxxx>
• Re: Bug in solaris 10 /bin/ksh w.r.t. test -z ")"
  • From: Stefano Lattarini <stefano.lattarini@xxxxxxxxx>
• Re: insert macros within AC_PROG_CC before _AC_COMPILER_EXEEEXT
  • From: Eric Blake <eblake@xxxxxxxxxx>
• insert macros within AC_PROG_CC before _AC_COMPILER_EXEEEXT
  • From: "Daily, Jeff A" <jeff.daily@xxxxxxx>
• Re: Overriding LN_S
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: Bug in solaris 10 /bin/ksh w.r.t. test -z ")"
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Bug in solaris 10 /bin/ksh w.r.t. test -z ")"
  • From: Stefano Lattarini <stefano.lattarini@xxxxxxxxx>
• Re: Nesting m4 macros
  • From: Stefano Lattarini <stefano.lattarini@xxxxxxxxx>
• Re: Nesting m4 macros
  • From: Stefano Lattarini <stefano.lattarini@xxxxxxxxx>
• Re: Nesting m4 macros
  • From: Matthias Wichtlhuber <mwichtlh@xxxxxxxxxxxxxxxxxxxxx>
• Re: Nesting m4 macros
  • From: Stefano Lattarini <stefano.lattarini@xxxxxxxxx>
• Nesting m4 macros
  • From: Matthias Wichtlhuber <mwichtlh@xxxxxxxxxxxxxxxxxxxxx>
• Re: Overriding LN_S
  • From: Steffen Dettmer <steffen.dettmer@xxxxxxxxxxxxxx>
• Re: Overriding LN_S
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: AC_CACHE_CHECK
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: AC_CACHE_CHECK
  • From: Thomas Dickey <dickey@xxxxxxx>
• Re: AC_CACHE_CHECK
  • From: Russell Shaw <rjshaw@xxxxxxxxxxxxxxx>
• Re: AC_CACHE_CHECK
  • From: Thomas Dickey <dickey@xxxxxxx>
• AC_CACHE_CHECK
  • From: Russell Shaw <rjshaw@xxxxxxxxxxxxxxx>
• Re: Overriding LN_S
  • From: Peter Rosin <peda@xxxxxxxxxxxxxx>
• Re: Overriding LN_S
  • From: Steffen Dettmer <steffen.dettmer@xxxxxxxxxxxxxx>
• Re: Overriding LN_S
  • From: Steffen Dettmer <steffen.dettmer@xxxxxxxxxxxxxx>
• Re: Overriding LN_S
  • From: Peter Rosin <peda@xxxxxxxxxxxxxx>
• Re: Overriding LN_S
  • From: Peter Rosin <peda@xxxxxxxxxxxxxx>
• Re: Overriding LN_S
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: Overriding LN_S
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: Overriding LN_S
  • From: Steffen Dettmer <steffen.dettmer@xxxxxxxxxxxxxx>
• Re: Overriding LN_S
  • From: Peter Rosin <peda@xxxxxxxxxxxxxx>
• Re: Overriding LN_S
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Overriding LN_S
  • From: Peter Rosin <peda@xxxxxxxxxxxxxx>
• Re: porting with autotools
  • From: Reuben Hawkins <reubenhwk@xxxxxxxxx>
• Re: porting with autotools
  • From: Reuben Hawkins <reubenhwk@xxxxxxxxx>
• Re: porting with autotools
  • From: NightStrike <nightstrike@xxxxxxxxx>
• Re: porting with autotools
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: ${var:+"quo ted"} and similar, inside unquoted here-docs
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: porting with autotools
  • From: Reuben Hawkins <reubenhwk@xxxxxxxxx>
• Re: porting with autotools
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: porting with autotools
  • From: "Gary V. Vaughan" <gary@xxxxxxx>
• Re: porting with autotools
  • From: Reuben Hawkins <reubenhwk@xxxxxxxxx>
• Re: porting with autotools
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: porting with autotools
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• Re: porting with autotools
  • From: Steffen Dettmer <steffen.dettmer@xxxxxxxxxxxxxx>
• Re: porting with autotools
  • From: Reuben Hawkins <reubenhwk@xxxxxxxxx>
• Re: porting with autotools
  • From: "Gary V. Vaughan" <gary@xxxxxxx>
• porting with autotools
  • From: Reuben Hawkins <reubenhwk@xxxxxxxxx>
• Re: VPATH test failure
  • From: Patrick Welche <prlw1@xxxxxxxxx>