Gnu Autoconf

• Thread Index

• Re: VPATH test failure
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: VPATH test failure
  • From: Patrick Welche <prlw1@xxxxxxxxx>
• Re: VPATH test failure
  • From: Eric Blake <eblake@xxxxxxxxxx>
• VPATH test failure
  • From: Patrick Welche <prlw1@xxxxxxxxx>
• Re: __USE_UNIX98 to enable late pthread features
  • From: Yavor Doganov <yavor@xxxxxxx>
• Re: AC_CHECK_LIB: Library is found on build host but is not on a target host
  • From: Eric Blake <eblake@xxxxxxxxxx>
• 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: Eric Blake <eblake@xxxxxxxxxx>
• Re: AC_CHECK_LIB: Library is found on build host but is not on a target host
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: __USE_UNIX98 to enable late pthread features
  • From: John Calcote <john.calcote@xxxxxxxxx>
• Re: AC_CHECK_LIB: Library is found on build host but is not on a target host
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: __USE_UNIX98 to enable late pthread features
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• AC_CHECK_LIB: Library is found on build host but is not on a target host
  • From: Sergio Belkin <sebelk@xxxxxxxxx>
• Re: __USE_UNIX98 to enable late pthread features
  • From: Eric Blake <eblake@xxxxxxxxxx>
• __USE_UNIX98 to enable late pthread features
  • From: John Calcote <john.calcote@xxxxxxxxx>
• Re: autotools use in commercial projects
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• autotools use in commercial projects
  • From: Reuben Hawkins <reubenhwk@xxxxxxxxx>
• Re: wikipedia
  • From: Stefano Lattarini <stefano.lattarini@xxxxxxxxx>
• Re: AC_SUBST for variables with AS_SET_VAR
  • From: "Jason Curl" <j.m.curl@xxxxxx>
• Re: AC_SUBST for variables with AS_SET_VAR
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• AC_SUBST for variables with AS_SET_VAR
  • From: Jason Curl <j.m.curl@xxxxxx>
• Re: Correct way to check for clock_gettime()
  • From: Thomas Petazzoni <thomas.petazzoni@xxxxxxxxxxxxxxxxxx>
• Re: Correct way to check for clock_gettime()
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: Fix testsuite errors due to shell quoted parameter expansion issue.
  • From: Chet Ramey <chet.ramey@xxxxxxxx>
• Re: How to correctly generate 'foobar.h' from 'foobar.h.in'
  • From: Tao Wang <dancefire@xxxxxxxxx>
• Re: How to correctly generate 'foobar.h' from 'foobar.h.in'
  • From: "Gary V. Vaughan" <gary@xxxxxxx>
• Re: How to correctly generate 'foobar.h' from 'foobar.h.in'
  • From: Mike Frysinger <vapier@xxxxxxxxxx>
• Re: How to correctly generate 'foobar.h' from 'foobar.h.in'
  • From: Tao Wang <dancefire@xxxxxxxxx>
• Re: Need help inserting AS_TR_CPP functionality in macro
  • From: Charlie Zender <zender@xxxxxxx>
• Re: Need help inserting AS_TR_CPP functionality in macro
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Need help inserting AS_TR_CPP functionality in macro
  • From: Charlie Zender <zender@xxxxxxx>
• Re: How to correctly generate 'foobar.h' from 'foobar.h.in'
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• RE: Fix testsuite errors due to shell quoted parameter expansion issue.
  • From: John Lumby <johnlumby@xxxxxxxxxxx>
• Re: Fix testsuite errors due to shell quoted parameter expansion issue.
  • From: Eric Blake <eblake@xxxxxxxxxx>
• RE: Fix testsuite errors due to shell quoted parameter expansion issue.
  • From: John Lumby <johnlumby@xxxxxxxxxxx>
• Re: Fix testsuite errors due to shell quoted parameter expansion issue.
  • From: Mikael Magnusson <mikachu@xxxxxxxxx>
• Re: How to correctly generate 'foobar.h' from 'foobar.h.in'
  • From: Mike Frysinger <vapier@xxxxxxxxxx>
• How to correctly generate 'foobar.h' from 'foobar.h.in'
  • From: Tao Wang <dancefire@xxxxxxxxx>
• Re: Fix testsuite errors due to shell quoted parameter expansion issue.
  • From: Tim Rice <tim@xxxxxxxxxxxxxxxx>
• Re: Fix testsuite errors due to shell quoted parameter expansion issue.
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: Fix testsuite errors due to shell quoted parameter expansion issue.
  • From: Tim Rice <tim@xxxxxxxxxxxxxxxx>
• Re: Fix testsuite errors due to shell quoted parameter expansion issue.
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: Arrays in configure.ac
  • From: Sam Silla <samsilla85@xxxxxxxxx>
• Re: Fix testsuite errors due to shell quoted parameter expansion issue.
  • From: Tim Rice <tim@xxxxxxxxxxxxxxxx>
• Re: Fix testsuite errors due to shell quoted parameter expansion issue.
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: Fix testsuite errors due to shell quoted parameter expansion issue.
  • From: Eric Blake <eblake@xxxxxxxxxx>
• GNU Autoconf 2.67 released [stable]
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: Correct way to check for clock_gettime()
  • From: Thomas Petazzoni <thomas.petazzoni@xxxxxxxxxxxxxxxxxx>
• Re: Correct way to check for clock_gettime()
  • From: Steffen Dettmer <steffen.dettmer@xxxxxxxxxxxxxx>
• Re[10]: infrastructure for suggested/required packages, and better error reporting
  • From: Konstantin Andreev <andreev@xxxxxxxxx>
• Re[9]: The problem with pgk-config
  • From: Konstantin Andreev <andreev@xxxxxxxxx>
• Re: Correct way to check for clock_gettime()
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: Correct way to check for clock_gettime()
  • From: Thomas Petazzoni <thomas.petazzoni@xxxxxxxxxxxxxxxxxx>
• Re: Arrays in configure.ac
  • From: Matěj Týč <matej.tyc@xxxxxxxxx>
• Re: The problem with pgk-config
  • From: "Gary V. Vaughan" <gary@xxxxxxx>
• Re: infrastructure for suggested/required packages, and better error reporting
  • From: Matěj Týč <matej.tyc@xxxxxxxxx>
• Re: The problem with pgk-config
  • From: "Gary V. Vaughan" <gary@xxxxxxx>
• The problem with pgk-config
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• Re: infrastructure for suggested/required packages, and better error reporting
  • From: John Calcote <john.calcote@xxxxxxxxx>
• Re: infrastructure for suggested/required packages, and better error reporting
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: infrastructure for suggested/required packages, and better error reporting
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• infrastructure for suggested/required packages, and better error reporting
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: Correct way to check for clock_gettime()
  • From: Dave Hart <davehart@xxxxxxxxx>
• Re: Splitting tests and sources
  • From: "Ivan \"Rambius\" Ivanov" <rambiusparkisanius@xxxxxxxxx>
• Re: Splitting tests and sources
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Splitting tests and sources
  • From: "Ivan \"Rambius\" Ivanov" <rambiusparkisanius@xxxxxxxxx>
• Re: Correct way to check for clock_gettime()
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• Correct way to check for clock_gettime()
  • From: Thomas Petazzoni <thomas.petazzoni@xxxxxxxxxxxxxxxxxx>
• Re: help with broken autoconf/m4 macro?
  • From: Charlie Zender <zender@xxxxxxx>
• Re: help with broken autoconf/m4 macro?
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: help with broken autoconf/m4 macro?
  • From: Charlie Zender <zender@xxxxxxx>
• Re: help with broken autoconf/m4 macro?
  • From: Eric Blake <eblake@xxxxxxxxxx>
• help with broken autoconf/m4 macro?
  • From: Charlie Zender <zender@xxxxxxx>
• Re: RM: to -f or not to -f
  • From: Eric Blake <eblake@xxxxxxxxxx>
• RM: to -f or not to -f
  • From: Patrick Welche <prlw1@xxxxxxxxx>
• ${var-$default} vs. ${var=$default} (was: Re: [PATCHES] Bootstrap: Allow user overriding of $AUTOCONF and $PERL.)
  • From: Stefano Lattarini <stefano.lattarini@xxxxxxxxx>
• Re: [PATCHES] Bootstrap: Allow user overriding of $AUTOCONF and $PERL.
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: [PATCHES] Bootstrap: Allow user overriding of $AUTOCONF and $PERL.
  • From: Stefano Lattarini <stefano.lattarini@xxxxxxxxx>
• Re: [PATCHES] Bootstrap: Allow user overriding of $AUTOCONF and $PERL.
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: Autotools book published
  • From: John Calcote <john.calcote@xxxxxxxxx>
• Re: Autotools book published
  • From: "Alfred M. Szmidt" <ams@xxxxxxx>
• Re: Autotools book published
  • From: Matěj Týč <matej.tyc@xxxxxxxxx>
• Re: Diffing the results of conifgure
  • From: "Ralf Wildenhues" <Ralf.Wildenhues@xxxxxx>
• Re: Autotools book published
  • From: Russell Shaw <rjshaw@xxxxxxxxxxxxxxx>
• Autotools book published
  • From: John Calcote <john.calcote@xxxxxxxxx>
• Re: configure cd'ing to home
  • From: "Ralf Wildenhues" <Ralf.Wildenhues@xxxxxx>
• Re: configure cd'ing to home
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: configure cd'ing to home
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: Diffing the results of conifgure
  • From: Stefano Lattarini <stefano.lattarini@xxxxxxxxx>
• Diffing the results of conifgure
  • From: Philip Prindeville <philipp@xxxxxxxxxxxxxxxxxxxxx>
• configure cd'ing to home
  • From: Sam Silla <samsilla85@xxxxxxxxx>
• Re: 'make' vs 'make -j1': Tpo files in different places
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: 'make' vs 'make -j1': Tpo files in different places
  • From: Chris Stankevitz <chrisstankevitz@xxxxxxxxx>
• Re: 'make' vs 'make -j1': Tpo files in different places
  • From: Chris Stankevitz <chrisstankevitz@xxxxxxxxx>
• Re: 'make' vs 'make -j1': Tpo files in different places
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• 'make' vs 'make -j1': Tpo files in different places
  • From: Chris Stankevitz <chrisstankevitz@xxxxxxxxx>
• Re: custom switches
  • From: Wesley Smith <wesley.hoke@xxxxxxxxx>
• Re: custom switches
  • From: Eric Blake <eblake@xxxxxxxxxx>
• custom switches
  • From: Wesley Smith <wesley.hoke@xxxxxxxxx>
• Re: Detecting IP_TOS (and IPPROTO_IP vs. SOL_IP)
  • From: "Philip A. Prindeville" <philipp_subx@xxxxxxxxxxxxxxxxxxxxx>
• Re: Detecting IP_TOS (and IPPROTO_IP vs. SOL_IP)
  • From: Eric Blake <eblake@xxxxxxxxxx>
• RE: how to specify arbitrary macro variable for config.h
  • From: John Lumby <johnlumby@xxxxxxxxxxx>
• Re: how to specify arbitrary macro variable for config.h
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• how to specify arbitrary macro variable for config.h
  • From: John Lumby <johnlumby@xxxxxxxxxxx>
• Re: Please update hyperlinks to the Autoconf Archive on the website
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Please update hyperlinks to the Autoconf Archive on the website
  • From: Peter Simons <simons@xxxxxxx>
• Re: Adding a newline to AS_HELP_STRING
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: autoconf-2.66 with pkg-config-0.25 problem
  • From: Nishio Futoshi <fut_nis@xxxxxxxxxxxxx>
• Adding a newline to AS_HELP_STRING
  • From: Jason Butler <jbutler@xxxxxxxxxxx>
• Re: Problem when a 32-bit library is linked instead of a 64-bit library
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Problem when a 32-bit library is linked instead of a 64-bit library
  • From: "Dr. David Kirkby" <david.kirkby@xxxxxxxxxx>
• Re: autoconf-2.66 with pkg-config-0.25 problem
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: First steps with autoconf and autotools - building an OpenSSL app
  • From: "Ivan \"Rambius\" Ivanov" <rambiusparkisanius@xxxxxxxxx>
• Re: First steps with autoconf and autotools - building an OpenSSL app
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: First steps with autoconf and autotools - building an OpenSSL app
  • From: Peter Johansson <trojkan@xxxxxxxxx>
• First steps with autoconf and autotools - building an OpenSSL app
  • From: "Ivan \"Rambius\" Ivanov" <rambiusparkisanius@xxxxxxxxx>
• Re: $abs_srcdir expansion
  • From: Stefano Sabatini <stefano.sabatini-lala@xxxxxxxx>
• Re: Arrays in configure.ac
  • From: John Calcote <john.calcote@xxxxxxxxx>
• Arrays in configure.ac
  • From: Sam Silla <samsilla85@xxxxxxxxx>
• Re: $abs_srcdir expansion
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: $abs_srcdir expansion
  • From: Peter Breitenlohner <peb@xxxxxxxxxxxx>
• Re: $abs_srcdir expansion
  • From: Stefano Sabatini <stefano.sabatini-lala@xxxxxxxx>
• Re: $abs_srcdir expansion
  • From: Peter Breitenlohner <peb@xxxxxxxxxxxx>
• $abs_srcdir expansion
  • From: Stefano Sabatini <stefano.sabatini-lala@xxxxxxxx>
• Re: AC_CHECK_SIZEOF([int *]) is error in autoconf-2.66
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: AC_CHECK_SIZEOF([int *]) is error in autoconf-2.66
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: GNU autoconf-2.66 released [stable]
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: GNU autoconf-2.66 released [stable]
  • From: Olly Betts <olly@xxxxxxxxxx>
• Re: Detecting IP_TOS (and IPPROTO_IP vs. SOL_IP)
  • From: Philip Prindeville <philipp_subx@xxxxxxxxxxxxxxxxxxxxx>
• Re: powerpc-ibm-os400?
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• powerpc-ibm-os400?
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• autoconf-2.66 with pkg-config-0.25 problem
  • From: Nishio Futoshi <fut_nis@xxxxxxxxxxxxx>
• Re: AC_CHECK_SIZEOF([int *]) is error in autoconf-2.66
  • From: Nishio Futoshi <fut_nis@xxxxxxxxxxxxx>
• Re: AC_CHECK_SIZEOF([int *]) is error in autoconf-2.66
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: AC_CHECK_SIZEOF([int *]) is error in autoconf-2.66
  • From: Nishio Futoshi <fut_nis@xxxxxxxxxxxxx>
• Re: AC_CHECK_SIZEOF([int *]) is error in autoconf-2.66
  • From: Adam Mercer <ramercer@xxxxxxxxx>
• Re: AC_CHECK_SIZEOF([int *]) is error in autoconf-2.66
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: AC_CHECK_SIZEOF([int *]) is error in autoconf-2.66
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• AC_CHECK_SIZEOF([int *]) is error in autoconf-2.66
  • From: Nishio Futoshi <fut_nis@xxxxxxxxxxxxx>
• Re: avoiding undesired macro expansion after AS_TR_CPP
  • From: Bruno Haible <bruno@xxxxxxxxx>
• GNU autoconf-2.66 released [stable]
  • From: Eric Blake <eblake@xxxxxxxxxx>
• [PATCH] Make AS_TR_SH and AS_TR_CPP similar.
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: avoiding undesired macro expansion after AS_TR_CPP
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: determining 32 v. 64 bit compilatio
  • From: "Peter O'Gorman" <peter@xxxxxxxxx>
• Re: determining 32 v. 64 bit compilatio
  • From: Wesley Smith <wesley.hoke@xxxxxxxxx>
• Re: determining 32 v. 64 bit compilatio
  • From: John Calcote <john.calcote@xxxxxxxxx>
• Re: determining 32 v. 64 bit compilatio
  • From: "Andrew W. Nosenko" <andrew.w.nosenko@xxxxxxxxx>
• Re: determining 32 v. 64 bit compilatio
  • From: Wesley Smith <wesley.hoke@xxxxxxxxx>
• Re: determining 32 v. 64 bit compilatio
  • From: Mike Frysinger <vapier@xxxxxxxxxx>
• Re: determining 32 v. 64 bit compilatio
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• Re: determining 32 v. 64 bit compilatio
  • From: Russ Allbery <rra@xxxxxxxxxxxx>
• Re: determining 32 v. 64 bit compilatio
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• Re: determining 32 v. 64 bit compilatio
  • From: "Raphael 'kena' Poss" <autoconf@xxxxxxxxxxxxxxxxx>
• Re: determining 32 v. 64 bit compilatio
  • From: Wesley Smith <wesley.hoke@xxxxxxxxx>
• Re: determining 32 v. 64 bit compilatio
  • From: Mike Frysinger <vapier@xxxxxxxxxx>
• Re: determining 32 v. 64 bit compilatio
  • From: Wesley Smith <wesley.hoke@xxxxxxxxx>
• Re: determining 32 v. 64 bit compilatio
  • From: Mike Frysinger <vapier@xxxxxxxxxx>
• Re: determining 32 v. 64 bit compilatio
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• determining 32 v. 64 bit compilatio
  • From: Wesley Smith <wesley.hoke@xxxxxxxxx>
• Re: checking for header/library mismatch, rpath problem?
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: checking for header/library mismatch, rpath problem?
  • From: Adam Mercer <ramercer@xxxxxxxxx>
• Re: checking for header/library mismatch, rpath problem?
  • From: Peter Breitenlohner <peb@xxxxxxxxxxxx>
• testsuite --recheck
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: checking for header/library mismatch, rpath problem?
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: checking for header/library mismatch, rpath problem?
  • From: Adam Mercer <ramercer@xxxxxxxxx>
• Re: checking for header/library mismatch, rpath problem?
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: Factoring out common code from 2 programs into new library
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Factoring out common code from 2 programs into new library
  • From: David Bruce <davidstuartbruce@xxxxxxxxx>
• Re: Defining dependencies in Automake
  • From: "Gary V. Vaughan" <gary@xxxxxxx>
• Re: checking for header/library mismatch, rpath problem?
  • From: Adam Mercer <ramercer@xxxxxxxxx>
• Defining dependencies in Automake
  • From: Sam Silla <samsilla85@xxxxxxxxx>
• Re: Probable m4 quoting problem
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Probable m4 quoting problem
  • From: David Bruce <davidstuartbruce@xxxxxxxxx>
• Re: sed --posix does not catch incomplete arguments
  • From: Jim Meyering <jim@xxxxxxxxxxxx>
• Re: sed --posix does not catch incomplete arguments
  • From: Paul Smith <psmith@xxxxxxx>
• Re: sed --posix does not catch incomplete arguments
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: sed --posix does not catch incomplete arguments
  • From: Bruno Haible <bruno@xxxxxxxxx>
• Re: sed --posix does not catch incomplete arguments
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: Problem Autoconf2.59 vs 2.65
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: checking for header/library mismatch, rpath problem?
  • From: Adam Mercer <ramercer@xxxxxxxxx>
• Problem Autoconf2.59 vs 2.65
  • From: pellegrini <pellegrini@xxxxxx>
• Re: checking for header/library mismatch, rpath problem?
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: checking for header/library mismatch, rpath problem?
  • From: Adam Mercer <ramercer@xxxxxxxxx>
• Re: checking for header/library mismatch, rpath problem?
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• checking for header/library mismatch, rpath problem?
  • From: Adam Mercer <ramercer@xxxxxxxxx>
• Re: nodist_BUILT_SOURCES?
  • From: Monty Taylor <mordred@xxxxxxxxxxxx>
• Re: nodist_BUILT_SOURCES?
  • From: John Calcote <john.calcote@xxxxxxxxx>
• Re: nodist_BUILT_SOURCES?
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• nodist_BUILT_SOURCES?
  • From: Monty Taylor <mordred@xxxxxxxxxxxx>
• Re: conditional use of gettext
  • From: Vincent Torri <vtorri@xxxxxxxxxxxx>
• Re: conditional use of gettext
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: conditional use of gettext
  • From: Vincent Torri <vtorri@xxxxxxxxxxxx>
• Re: conditional use of gettext
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: conditional use of gettext
  • From: Vincent Torri <vtorri@xxxxxxxxxxxx>
• Re: conditional use of gettext
  • From: Vincent Torri <vtorri@xxxxxxxxxxxx>
• Re: conditional use of gettext
  • From: Eric Blake <eblake@xxxxxxxxxx>
• conditional use of gettext
  • From: Vincent Torri <vtorri@xxxxxxxxxxxx>
• Re: [SCM] GNU Libtool branch, master, updated. v2.2.7b-4-gaa75582
  • From: "Gary V. Vaughan" <gary@xxxxxxx>
• Re: [SCM] GNU Libtool branch, master, updated. v2.2.7b-4-gaa75582
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: avoiding undesired macro expansion after AS_TR_CPP
  • From: Bruno Haible <bruno@xxxxxxxxx>
• Re: avoiding undesired macro expansion after AS_TR_CPP
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: avoiding undesired macro expansion after AS_TR_CPP
  • From: Bruno Haible <bruno@xxxxxxxxx>
• Re: avoiding undesired macro expansion after AS_TR_CPP
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: avoiding undesired macro expansion after AS_TR_CPP
  • From: Bruno Haible <bruno@xxxxxxxxx>
• Re: avoiding undesired macro expansion after AS_TR_CPP
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: avoiding undesired macro expansion after AS_TR_CPP
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: avoiding undesired macro expansion after AS_TR_CPP
  • From: "Raphael 'kena' Poss" <autoconf@xxxxxxxxxxxxxxxxx>
• avoiding undesired macro expansion after AS_TR_CPP
  • From: Bruno Haible <bruno@xxxxxxxxx>
• Re: Passing an argument to configure script of subproject
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: m4 and autoconf problem on mac os x
  • From: Stefano Lattarini <stefano.lattarini@xxxxxxxxx>
• Re: m4 and autoconf problem on mac os x
  • From: Vincent Torri <vtorri@xxxxxxxxxxxx>
• Re: m4 and autoconf problem on mac os x
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: m4 and autoconf problem on mac os x
  • From: Stefano Lattarini <stefano.lattarini@xxxxxxxxx>
• Re: m4 and autoconf problem on mac os x
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: m4 and autoconf problem on mac os x
  • From: Stefano Lattarini <stefano.lattarini@xxxxxxxxx>
• Re: m4 and autoconf problem on mac os x
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: m4 and autoconf problem on mac os x
  • From: "Raphael 'kena' Poss" <autoconf@xxxxxxxxxxxxxxxxx>
• Re: m4 and autoconf problem on mac os x
  • From: Eric Blake <eblake@xxxxxxxxxx>
• m4 and autoconf problem on mac os x
  • From: Vincent Torri <vtorri@xxxxxxxxxxxx>
• Re: AC_CHECK_DECLS(basename) (Was: Re: Ping: patches required for --enable-build-with-cxx)
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: AC_CHECK_DECLS(basename) (Was: Re: Ping: patches required for --enable-build-with-cxx)
  • From: Richard Guenther <richard.guenther@xxxxxxxxx>
• Re: Passing an argument to configure script of subproject
  • From: Richard Ash <richard@xxxxxxxxxxxxxxxx>
• Re: AC_CHECK_DECLS(basename) (Was: Re: Ping: patches required for --enable-build-with-cxx)
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: AC_CHECK_DECLS(basename) (Was: Re: Ping: patches required for --enable-build-with-cxx)
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: AC_CHECK_DECLS(basename) (Was: Re: Ping: patches required for --enable-build-with-cxx)
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: libtool relinking conditions
  • From: Eric Blake <eblake@xxxxxxxxxx>
• RE: exec 0</dev/null vs. nohup?
  • From: Jay K <jay.krell@xxxxxxxxxxx>
• Re: exec 0</dev/null vs. nohup?
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• libtool relinking conditions
  • From: Alex Farber <alexf.aconf@xxxxxxxxx>
• Passing an argument to configure script of subproject
  • From: ithilgore <ithilgore.ryu.l@xxxxxxxxx>
• exec 0</dev/null vs. nohup?
  • From: Jay K <jay.krell@xxxxxxxxxxx>
• Re: Conditional change of C++ compiler flags
  • From: Alex Farber <alexf.aconf@xxxxxxxxx>
• sub-package
  • From: Paul Dugas <paul@xxxxxxxxxxxxxxxxxxxx>
• Re: Most appropriate location for installing example programs?
  • From: "Joel J. Adamson" <adamsonj@xxxxxxxxxxxxx>
• Re: Conditional change of C++ compiler flags
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Conditional change of C++ compiler flags
  • From: Alex Farber <alexf.aconf@xxxxxxxxx>
• Re: Most appropriate location for installing example programs?
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: Most appropriate location for installing example programs?
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: Most appropriate location for installing example programs?
  • From: "Raphael 'kena' Poss" <autoconf@xxxxxxxxxxxxxxxxx>
• Re: Most appropriate location for installing example programs?
  • From: Sam Shin <samsilla85@xxxxxxxxx>
• Re: Generating testsuite at maintainer not build time
  • From: Luke Mewburn <lukem@xxxxxxxxxx>
• Most appropriate location for installing example programs?
  • From: Sam Shin <samsilla85@xxxxxxxxx>
• Re: configure.ac parameter
  • From: Alex Farber <alexf.aconf@xxxxxxxxx>
• Re: Reusing the product of AC_LANG_PROGRAM().
  • From: Stefano Lattarini <stefano.lattarini@xxxxxxxxx>
• Re: Reusing the product of AC_LANG_PROGRAM().
  • From: Stefano Lattarini <stefano.lattarini@xxxxxxxxx>
• Reusing the product of AC_LANG_PROGRAM().
  • From: Václav Haisman <v.haisman@xxxxxxxxxx>
• Re: configure.ac parameter
  • From: Stefano Lattarini <stefano.lattarini@xxxxxxxxx>
• configure.ac parameter
  • From: Alex Farber <alexf.aconf@xxxxxxxxx>
• Re: Properly handling conditional functions in header
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: Printing configure arguments
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: Printing configure arguments
  • From: Adam Mercer <ramercer@xxxxxxxxx>
• Printing configure arguments
  • From: Sam Shin <samsilla85@xxxxxxxxx>
• Properly handling conditional functions in header
  • From: Evan Klinger <eklinger@xxxxxxxxx>
• Re: AC_CONFIG_SUBDIRS Question
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: C++ program incorrectly linked as C?
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: C++ program incorrectly linked as C?
  • From: Natalie Tasman <natalie.tasman@xxxxxxxxxxxxx>
• C++ program incorrectly linked as C?
  • From: Natalie Tasman <natalie.tasman@xxxxxxxxxxxxx>
• Re: how to add this function to the aclole.m4
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: how to add this function to the aclole.m4
  • From: "Steffen DETTMER" <Steffen.DETTMER@xxxxxxxxxxxx>
• Re: how to add this function to the aclole.m4
  • From: Ralph Blach <chipperb@xxxxxxxxx>
• Re: how to add this function to the aclole.m4
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: how to add this function to the aclole.m4
  • From: Ralph Blach <chipperb@xxxxxxxxx>
• Re: modification of CFLAGS
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: modification of CFLAGS
  • From: Jason Curl <jcurlnews@xxxxxxxx>
• Re: modification of CFLAGS
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: how to add this function to the aclole.m4
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• modification of CFLAGS
  • From: Jason Curl <jcurlnews@xxxxxxxx>
• Re: Generating testsuite at maintainer not build time
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: how to add this function to the aclole.m4
  • From: Ralph Blach <chipperb@xxxxxxxxx>
• Generating testsuite at maintainer not build time
  • From: Luke Mewburn <lukem@xxxxxxxxxx>
• Re: how to add this function to the aclole.m4
  • From: Eric Blake <eblake@xxxxxxxxxx>
• how to add this function to the aclole.m4
  • From: Ralph Blach <chipperb@xxxxxxxxx>
• Re: m4 quoting and autoheader
  • From: Adam Mercer <ramercer@xxxxxxxxx>
• Re: m4 quoting and autoheader
  • From: Eric Blake <eblake@xxxxxxxxxx>
• m4 quoting and autoheader
  • From: Adam Mercer <ramercer@xxxxxxxxx>
• Re: Iterating over variable using AC_DEFINE to get HAVE_FOO_varitem (similar to AC_CHECK_HEADERS)
  • From: Keith Marshall <keith.d.marshall@xxxxxxxxxxxx>
• Re: Iterating over variable using AC_DEFINE to get HAVE_FOO_varitem (similar to AC_CHECK_HEADERS)
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: cross-compiling but keeping one target native
  • From: Keith Marshall <keith.d.marshall@xxxxxxxxxxxx>
• Re: Iterating over variable using AC_DEFINE to get HAVE_FOO_varitem (similar to AC_CHECK_HEADERS)
  • From: Keith Marshall <keith.d.marshall@xxxxxxxxxxxx>
• Re[4]: Iterating over variable using AC_DEFINE to get HAVE_FOO_varitem (similar to AC_CHECK_HEADERS)
  • From: Konstantin Andreev <andreev@xxxxxxxxx>
• Re: Iterating over variable using AC_DEFINE to get HAVE_FOO_varitem (similar to AC_CHECK_HEADERS)
  • From: Steffen Dettmer <steffen.dettmer@xxxxxxxxxxxxxx>
• Re: cross-compiling but keeping one target native
  • From: Christian Rössel <christian.roessel@xxxxxx>
• Re: cross-compiling but keeping one target native
  • From: Ben Pfaff <blp@xxxxxxxxxxxxxxx>
• Re: SMP configuration
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• Re: SMP configuration
  • From: Warren Young <warren@xxxxxxxxxxx>
• Re: Iterating over variable using AC_DEFINE to get HAVE_FOO_varitem (similar to AC_CHECK_HEADERS)
  • From: Daniel Leidert <daniel.leidert.spam@xxxxxxx>
• Re: SMP configuration
  • From: "Raphael 'kena' Poss" <autoconf@xxxxxxxxxxxxxxxxx>
• Re: SMP configuration
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: SMP configuration
  • From: Warren Young <warren@xxxxxxxxxxx>
• Re: Iterating over variable using AC_DEFINE to get HAVE_FOO_varitem (similar to AC_CHECK_HEADERS)
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: SMP configuration
  • From: Michael Menegakis <arxeio@xxxxxxxxx>
• Re: Iterating over variable using AC_DEFINE to get HAVE_FOO_varitem (similar to AC_CHECK_HEADERS)
  • From: Daniel Leidert <daniel.leidert.spam@xxxxxxx>
• Re: SMP configuration
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: SMP configuration
  • From: NightStrike <nightstrike@xxxxxxxxx>
• Re: SMP configuration
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: Iterating over variable using AC_DEFINE to get HAVE_FOO_varitem (similar to AC_CHECK_HEADERS)
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: Strange build error on Mac OS X (10.6.3)
  • From: Adam Mercer <ramercer@xxxxxxxxx>
• SMP configuration
  • From: Michael Menegakis <arxeio@xxxxxxxxx>
• Re: cross-compiling but keeping one target native
  • From: NightStrike <nightstrike@xxxxxxxxx>
• Re: cross-compiling but keeping one target native
  • From: Keith Marshall <keith.d.marshall@xxxxxxxxxxxx>
• Re: cross-compiling but keeping one target native
  • From: NightStrike <nightstrike@xxxxxxxxx>
• Re: cross-compiling but keeping one target native
  • From: Keith Marshall <keith.d.marshall@xxxxxxxxxxxx>
• cross-compiling but keeping one target native
  • From: Natalie Tasman <natalie.tasman@xxxxxxxxxxxxx>
• Iterating over variable using AC_DEFINE to get HAVE_FOO_varitem (similar to AC_CHECK_HEADERS)
  • From: Daniel Leidert <daniel.leidert.spam@xxxxxxx>
• Re: Strange build error on Mac OS X (10.6.3)
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: Strange build error on Mac OS X (10.6.3)
  • From: Adam Mercer <ramercer@xxxxxxxxx>
• Re: Strange build error on Mac OS X (10.6.3)
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: Strange build error on Mac OS X (10.6.3)
  • From: Adam Mercer <ramercer@xxxxxxxxx>
• Re: Strange build error on Mac OS X (10.6.3)
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Strange build error on Mac OS X (10.6.3)
  • From: Adam Mercer <ramercer@xxxxxxxxx>
• Re: Best practices for autotools
  • From: Lukas Kaser <lukas.kaser@xxxxxxxxxxxxxx>
• Re: AC_PROG_LD manual?
  • From: Lukas Kaser <lukas.kaser@xxxxxxxxxxxxxx>
• AC_CONFIG_SUBDIRS Question
  • From: Paul Dugas <paul@xxxxxxxxxxxxxxxxxxxx>
• Re: AC_PROG_CC_C99 and AC_OPENMP
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• Re: AC_PROG_CC_C99 and AC_OPENMP
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: AC_PROG_CC_C99 and AC_OPENMP
  • From: "Alfred M. Szmidt" <ams@xxxxxxx>
• Re: AC_PROG_CC_C99 and AC_OPENMP
  • From: "Stephen P. Schaefer" <sschaefer@xxxxxxx>
• Re: AC_PROG_CC_C99 and AC_OPENMP
  • From: William Pursell <bill.pursell@xxxxxxxxx>
• Re: AC_PROG_CC_C99 and AC_OPENMP
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: AC_PROG_CC_C99 and AC_OPENMP
  • From: "Joel J. Adamson" <adamsonj@xxxxxxxxxxxxx>
• Re: AC_PROG_CC_C99 and AC_OPENMP
  • From: "Joel J. Adamson" <adamsonj@xxxxxxxxxxxxx>
• Re: AC_PROG_CC_C99 and AC_OPENMP
  • From: "Joel J. Adamson" <adamsonj@xxxxxxxxxxxxx>
• Re: AC_PROG_CC_C99 and AC_OPENMP
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• Re: AC_PROG_CC_C99 and AC_OPENMP
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: AC_PROG_LD manual?
  • From: "Alfred M. Szmidt" <ams@xxxxxxx>
• Re: AC_PROG_LD manual?
  • From: Eric Blake <eblake@xxxxxxxxxx>
• AC_PROG_CC_C99 and AC_OPENMP
  • From: "Joel J. Adamson" <adamsonj@xxxxxxxxxxxxx>
• Re: AC_PROG_LD manual?
  • From: Lukas Kaser <lukas.kaser@xxxxxxxxxxxxxx>
• AC_PROG_LD manual?
  • From: Lukas Kaser <lukas.kaser@xxxxxxxxxxxxxx>
• Re: Best practices for autotools
  • From: "Gary V. Vaughan" <gary@xxxxxxx>
• Re: Best practices for autotools
  • From: Warren Young <warren@xxxxxxxxxxx>
• Re: Best practices for autotools
  • From: "Gary V. Vaughan" <gary@xxxxxxx>
• Re: Best practices for autotools
  • From: Diego Saravia <diego.saravia@xxxxxxxxx>
• Re: Best practices for autotools
  • From: Matěj Týč <matej.tyc@xxxxxxxxx>
• Re: Best practices for autotools
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• Re: Best practices for autotools
  • From: Stefano Lattarini <stefano.lattarini@xxxxxxxxx>
• Re: Best practices for autotools
  • From: "Joel J. Adamson" <adamsonj@xxxxxxxxxxxxx>
• Best practices for autotools
  • From: Lukas Kaser <lukas.kaser@xxxxxxxxxxxxxx>
• Re: If-statement influencing syntax/content in config.h? Naming convention for preprocessor variables.
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: If-statement influencing syntax/content in config.h? Naming convention for preprocessor variables.
  • From: Lukas Kaser <lukas.kaser@xxxxxxxxxxxxxx>
• Re: Infos for Unix/Windows portable library making?
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: If-statement influencing syntax/content in config.h? Naming convention for preprocessor variables.
  • From: Eric Blake <eblake@xxxxxxxxxx>
• If-statement influencing syntax/content in config.h? Naming convention for preprocessor variables.
  • From: Lukas Kaser <lukas.kaser@xxxxxxxxxxxxxx>
• Re: Infos for Unix/Windows portable library making?
  • From: Jason Curl <jcurlnews@xxxxxxxx>
• Re: GNU autogen code generation
  • From: Bruce Korb <bkorb@xxxxxxx>
• Re: GNU autogen code generation
  • From: Matěj Týč <matej.tyc@xxxxxxxxx>
• Re: git-version-gen not EBCDIC compatible
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: git-version-gen not EBCDIC compatible
  • From: Eric Blake <eblake@xxxxxxxxxx>
• git-version-gen not EBCDIC compatible
  • From: Steve Goetze <goetze@xxxxxxxxxxxx>
• Re: Prefix for file in source directory used in ./configure?
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: Prefix for file in source directory used in ./configure?
  • From: Jason Sewall <sewall@xxxxxxxxxx>
• Re: Prefix for file in source directory used in ./configure?
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: Prefix for file in source directory used in ./configure?
  • From: Jason Sewall <sewall@xxxxxxxxxx>
• Re: Infos for Unix/Windows portable library making?
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: Infos for Unix/Windows portable library making?
  • From: Thomas Dickey <dickey@xxxxxxx>
• Re: Infos for Unix/Windows portable library making?
  • From: Kārlis Repsons <k@xxxxx>
• Re: Infos for Unix/Windows portable library making?
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: Infos for Unix/Windows portable library making?
  • From: Mike Frysinger <vapier@xxxxxxxxxx>
• Re: Prefix for file in source directory used in ./configure?
  • From: Russ Allbery <rra@xxxxxxxxxxxx>
• Prefix for file in source directory used in ./configure?
  • From: Jason Sewall <sewall@xxxxxxxxxx>
• Re: Infos for Unix/Windows portable library making?
  • From: Thomas Dickey <dickey@xxxxxxx>
• Re: Infos for Unix/Windows portable library making?
  • From: "Dr. David Kirkby" <david.kirkby@xxxxxxxxxx>
• Infos for Unix/Windows portable library making?
  • From: Kārlis Repsons <k@xxxxx>
• Re: use of shrext_cmds on mac os x
  • From: Eric Blake <eblake@xxxxxxxxxx>
• use of shrext_cmds on mac os x
  • From: Vincent Torri <vtorri@xxxxxxxxxxxx>
• Re: AC_CHECK_HEADER fails
  • From: "Joel J. Adamson" <adamsonj@xxxxxxxxxxxxx>
• AC_CHECK_HEADER fails
  • From: Lukas Kaser <lukas.kaser@xxxxxxxxxxxxxx>
• Re: AC_CHECK_LIB not finding my library
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: AC_CHECK_LIB not finding my library
  • From: Jim Meyering <jim@xxxxxxxxxxxx>
• Re: AC_CHECK_LIB not finding my library
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: AC_CHECK_LIB not finding my library
  • From: "Joel J. Adamson" <adamsonj@xxxxxxxxxxxxx>
• Re: Issue with gl_WCHAR_H on z/OS
  • From: Steve Goetze <goetze@xxxxxxxxxxxx>
• Re: Issue with gl_WCHAR_H on z/OS
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: PACKAGE_URL
  • From: Patrick Welche <prlw1@xxxxxxxxx>
• Issue with gl_WCHAR_H on z/OS
  • From: Steve Goetze <goetze@xxxxxxxxxxxx>
• Re: AC_CHECK_LIB not finding my library
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: AC_CHECK_LIB not finding my library
  • From: "Joel J. Adamson" <adamsonj@xxxxxxxxxxxxx>
• Re: AC_CHECK_LIB not finding my library
  • From: Eric Blake <eblake@xxxxxxxxxx>
• AC_CHECK_LIB not finding my library
  • From: "Joel J. Adamson" <adamsonj@xxxxxxxxxxxxx>
• Re: Using AC_PACKAGE_NAME in option names?
  • From: Steffen Dettmer <steffen.dettmer@xxxxxxxxxxxxxx>
• Re: Using AC_PACKAGE_NAME in option names?
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Using AC_PACKAGE_NAME in option names?
  • From: Steffen Dettmer <steffen.dettmer@xxxxxxxxxxxxxx>
• Re: portability of 'printf' command
  • From: karl@xxxxxxxxxxxxxxx (Karl Berry)
• Re: PACKAGE_URL
  • From: Peter Johansson <trojkan@xxxxxxxxx>
• PACKAGE_URL
  • From: Patrick Welche <prlw1@xxxxxxxxx>
• Re: portability of 'printf' command
  • From: Harlan Stenn <stenn@xxxxxxxxxxxx>
• Re: portability of 'printf' command
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• Re: portability of 'printf' command
  • From: Bruno Haible <bruno@xxxxxxxxx>
• Re: portability of 'printf' command
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: portability of 'printf' command
  • From: karl@xxxxxxxxxxxxxxx (Karl Berry)
• Re: portability of 'printf' command
  • From: karl@xxxxxxxxxxxxxxx (Karl Berry)
• Re: portability of 'printf' command
  • From: Jim Meyering <jim@xxxxxxxxxxxx>
• Re: portability of 'printf' command
  • From: Jim Meyering <jim@xxxxxxxxxxxx>
• Re: portability of 'printf' command
  • From: "Dr. David Kirkby" <david.kirkby@xxxxxxxxxx>
• Re: portability of 'printf' command
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• Re: portability of 'printf' command
  • From: karl@xxxxxxxxxxxxxxx (Karl Berry)
• Re: Issue with AS_TR_CPP, m4_cr_all and EBCDIC codeset
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: Issue with AS_TR_CPP, m4_cr_all and EBCDIC codeset
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: portability of 'printf' command
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: portability of 'printf' command
  • From: "Dr. David Kirkby" <david.kirkby@xxxxxxxxxx>
• Re: portability of 'printf' command
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• Re: portability of 'printf' command
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: Issue with AS_TR_CPP, m4_cr_all and EBCDIC codeset
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: Issue with AS_TR_CPP, m4_cr_all and EBCDIC codeset
  • From: Steve Goetze <goetze@xxxxxxxxxxxx>
• Re: Issue with AS_TR_CPP, m4_cr_all and EBCDIC codeset
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re[8]: Best practices to detect autoconf version in macro.
  • From: Konstantin Andreev <andreev@xxxxxxxxx>
• Re: Best practices to detect autoconf version in macro.
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: Best practices to detect autoconf version in macro.
  • From: Ralf Corsepius <rc040203@xxxxxxxxxx>
• Re: Best practices to detect autoconf version in macro.
  • From: Richard Ash <richard@xxxxxxxxxxxxxxxx>
• Re: Best practices to detect autoconf version in macro.
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: Best practices to detect autoconf version in macro.
  • From: Ralf Corsepius <rc040203@xxxxxxxxxx>
• Re[2]: Best practices to detect autoconf version in macro.
  • From: Konstantin Andreev <andreev@xxxxxxxxx>
• Re: Best practices to detect autoconf version in macro.
  • From: Ralf Corsepius <rc040203@xxxxxxxxxx>
• Best practices to detect autoconf version in macro.
  • From: Konstantin Andreev <andreev@xxxxxxxxx>
• Re: Detecting IP_TOS (and IPPROTO_IP vs. SOL_IP)
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: Issue with AS_TR_CPP, m4_cr_all and EBCDIC codeset
  • From: Steve Goetze <goetze@xxxxxxxxxxxx>
• Re: C++, assert and NDEBUG
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: Issue with AS_TR_CPP, m4_cr_all and EBCDIC codeset
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: C++, assert and NDEBUG
  • From: William Pursell <bill.pursell@xxxxxxxxx>
• Re: C++, assert and NDEBUG
  • From: Braden McDaniel <braden@xxxxxxxxxxxxx>
• Re: Detecting IP_TOS (and IPPROTO_IP vs. SOL_IP)
  • From: Philip Prindeville <philipp_subx@xxxxxxxxxxxxxxxxxxxxx>
• Re: C++, assert and NDEBUG
  • From: Rhys Ulerich <rhys.ulerich@xxxxxxxxx>
• Issue with AS_TR_CPP, m4_cr_all and EBCDIC codeset
  • From: Steve Goetze <goetze@xxxxxxxxxxxx>
• Re: C++, assert and NDEBUG
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• C++, assert and NDEBUG
  • From: Steve Searle <steve@xxxxxxxxxxxxxxx>
• Re: Detecting IP_TOS (and IPPROTO_IP vs. SOL_IP)
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: How to retrieve an absolute path in this case?
  • From: Eric Blake <eblake@xxxxxxxxxx>
• How to retrieve an absolute path in this case?
  • From: ant1scene <cyberparser@xxxxxxxxx>
• Re: what happened to DIST_SOURCES:
  • From: Eric Blake <eblake@xxxxxxxxxx>
• what happened to DIST_SOURCES:
  • From: "Brian J. Murrell" <brian@xxxxxxx>
• how to check third parameter of socket(2)?
  • From: Steffen Dettmer <steffen.dettmer@xxxxxxxxxxxxxx>
• Detecting IP_TOS (and IPPROTO_IP vs. SOL_IP)
  • From: "Philip A. Prindeville" <philipp_subx@xxxxxxxxxxxxxxxxxxxxx>
• Re: autoscan
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• autoscan
  • From: Russell Shaw <rjshaw@xxxxxxxxxxxxxxx>
• Re: Why PACKAGE_URL is not set ?
  • From: John Calcote <john.calcote@xxxxxxxxx>
• Why PACKAGE_URL is not set ?
  • From: TJ Yang <tjyang2001@xxxxxxxxx>
• Re: Configure script not at the root of src directory
  • From: Ralf Corsepius <rc040203@xxxxxxxxxx>
• Re: Configure script not at the root of src directory
  • From: Tim Post <echo@xxxxxxxxxxxx>
• Re: Configure script not at the root of src directory
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Configure script not at the root of src directory
  • From: scleung <shaochiliang@xxxxxxxxx>
• Re: custom config processing
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• custom config processing
  • From: Sam Steingold <sds@xxxxxxx>
• Re: source name limitations
  • From: NightStrike <nightstrike@xxxxxxxxx>
• Re: How to enable configure.ac to generate configure to must take arguments ?
  • From: "Dr. David Kirkby" <david.kirkby@xxxxxxxxxx>
• Re: How to enable configure.ac to generate configure to must take arguments ?
  • From: John Calcote <john.calcote@xxxxxxxxx>
• Re: How to enable configure.ac to generate configure to must take arguments ?
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: How to enable configure.ac to generate configure to must take arguments ?
  • From: TJ Yang <tjyang2001@xxxxxxxxx>
• Re: How to enable configure.ac to generate configure to must take arguments ?
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: How to enable configure.ac to generate configure to must take arguments ?
  • From: TJ Yang <tjyang2001@xxxxxxxxx>
• Re: How to enable configure.ac to generate configure to must take arguments ?
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: How to enable configure.ac to generate configure to must take arguments ?
  • From: NightStrike <nightstrike@xxxxxxxxx>
• How to enable configure.ac to generate configure to must take arguments ?
  • From: TJ Yang <tjyang2001@xxxxxxxxx>
• Re: [autoconf] Program & Library, dev in parallel?
  • From: mpsuzuki@xxxxxxxxxxxxxxxxx
• Re: Program & Library, dev in parallel?
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: [autoconf] Program & Library, dev in parallel?
  • From: "Patrick M. Rutkowski" <rutski89@xxxxxxxxx>
• Re: [autoconf] Program & Library, dev in parallel?
  • From: mpsuzuki@xxxxxxxxxxxxxxxxx
• Program & Library, dev in parallel?
  • From: "Patrick M. Rutkowski" <rutski89@xxxxxxxxx>
• Re: autoconf/automake/libtool cuda support
  • From: Eric Blake <eblake@xxxxxxxxxx>
• autoconf/automake/libtool cuda support
  • From: Andrey Asadchev <asadchev@xxxxxxxxx>
• Re: Motivation for renaming configure.in to configure.ac and its effect?
  • From: Steffen Dettmer <steffen.dettmer@xxxxxxxxxxxxxx>
• Re: Motivation for renaming configure.in to configure.ac and its effect?
  • From: Steffen Dettmer <steffen.dettmer@xxxxxxxxxxxxxx>
• Re: Motivation for renaming configure.in to configure.ac and its effect?
  • From: Peter Breitenlohner <peb@xxxxxxxxxxxx>
• Re: Motivation for renaming configure.in to configure.ac and its effect?
  • From: Ralf Corsepius <rc040203@xxxxxxxxxx>
• Re: Motivation for renaming configure.in to configure.ac and its effect?
  • From: Peter Breitenlohner <peb@xxxxxxxxxxxx>
• Re: Motivation for renaming configure.in to configure.ac and its effect?
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• Re: reasons for having no inclusion guards in config.h
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• Re: reasons for having no inclusion guards in config.h
  • From: Steffen Dettmer <steffen.dettmer@xxxxxxxxxxxxxx>
• Re: reasons for having no inclusion guards in config.h
  • From: Steffen Dettmer <steffen.dettmer@xxxxxxxxxxxxxx>
• Re: Motivation for renaming configure.in to configure.ac and its effect?
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: Motivation for renaming configure.in to configure.ac and its effect?
  • From: Ralf Corsepius <rc040203@xxxxxxxxxx>
• Re: Motivation for renaming configure.in to configure.ac and its effect?
  • From: Steffen Dettmer <steffen.dettmer@xxxxxxxxxxxxxx>
• Re: Motivation for renaming configure.in to configure.ac and its effect?
  • From: Ralf Corsepius <rc040203@xxxxxxxxxx>
• Motivation for renaming configure.in to configure.ac and its effect?
  • From: Steffen Dettmer <steffen.dettmer@xxxxxxxxxxxxxx>
• Re: reasons for having no inclusion guards in config.h
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: reasons for having no inclusion guards in config.h
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• Re: reasons for having no inclusion guards in config.h
  • From: Tim Rice <tim@xxxxxxxxxxxxxxxx>
• Re: reasons for having no inclusion guards in config.h
  • From: John Calcote <john.calcote@xxxxxxxxx>
• Re: reasons for having no inclusion guards in config.h
  • From: Carsten Heinrici <carsten@xxxxxxxxxxxx>
• Re: reasons for having no inclusion guards in config.h
  • From: John Calcote <john.calcote@xxxxxxxxx>
• Re: reasons for having no inclusion guards in config.h
  • From: Harlan Stenn <stenn@xxxxxxxxxxxx>
• Re: reasons for having no inclusion guards in config.h
  • From: Tim Rice <tim@xxxxxxxxxxxxxxxx>
• Re: reasons for having no inclusion guards in config.h
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• Re: reasons for having no inclusion guards in config.h
  • From: John Calcote <john.calcote@xxxxxxxxx>
• Re: reasons for having no inclusion guards in config.h
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• Re: reasons for having no inclusion guards in config.h
  • From: Carsten Heinrici <carsten@xxxxxxxxxxxx>
• Re: reasons for having no inclusion guards in config.h
  • From: Hartmut Holzgraefe <hartmut@xxxxxxx>
• reasons for having no inclusion guards in config.h
  • From: Carsten Heinrici <carsten@xxxxxxxxxxxx>
• Re: source name limitations
  • From: "Raphael 'kena' Poss" <autoconf@xxxxxxxxxxxxxxxxx>
• source name limitations
  • From: Akos Rajna <akimaki@xxxxxxxxx>
• Re: Trying to be fancy with feature testing
  • From: NightStrike <nightstrike@xxxxxxxxx>
• Re: Trying to be fancy with feature testing
  • From: Eric Blake <ebb9@xxxxxxx>
• Trying to be fancy with feature testing
  • From: NightStrike <nightstrike@xxxxxxxxx>
• Re: AC_CHECK_FUNCS and gcc with -Werror
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: AC_CHECK_FUNCS and gcc with -Werror
  • From: NightStrike <nightstrike@xxxxxxxxx>
• Re: release is imminent
  • From: Vincent Torri <vtorri@xxxxxxxxxxxx>
• Re: AC_CHECK_FUNCS and gcc with -Werror
  • From: Russ Allbery <rra@xxxxxxxxxxxx>
• Re: AC_CHECK_FUNCS and gcc with -Werror
  • From: Steffen Dettmer <steffen.dettmer@xxxxxxxxxxxxxx>
• Re: AC_CHECK_FUNCS and gcc with -Werror
  • From: Steffen Dettmer <steffen.dettmer@xxxxxxxxxxxxxx>
• Re: AC_CHECK_FUNCS and gcc with -Werror
  • From: Steffen Dettmer <steffen.dettmer@xxxxxxxxxxxxxx>
• Re: how to handle new subdirectories?
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: how to handle new subdirectories?
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: AC_CHECK_FUNCS and gcc with -Werror
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: AC_CHECK_FUNCS and gcc with -Werror
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: AC_CHECK_FUNCS and gcc with -Werror
  • From: Russ Allbery <rra@xxxxxxxxxxxx>
• Re: AC_CHECK_FUNCS and gcc with -Werror
  • From: Steffen Dettmer <steffen.dettmer@xxxxxxxxxxxxxx>
• Re: AC_CHECK_FUNCS and gcc with -Werror
  • From: Steffen Dettmer <steffen.dettmer@xxxxxxxxxxxxxx>
• Re: AC_CHECK_FUNCS and gcc with -Werror
  • From: Steffen Dettmer <steffen.dettmer@xxxxxxxxxxxxxx>
• Re: AS assembler variable
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: AC_CHECK_FUNCS and gcc with -Werror
  • From: Russ Allbery <rra@xxxxxxxxxxxx>
• Re: AS assembler variable
  • From: NightStrike <nightstrike@xxxxxxxxx>
• Re: Autoupdate and AC_ERROR
  • From: NightStrike <nightstrike@xxxxxxxxx>
• Autoupdate and AC_ERROR
  • From: NightStrike <nightstrike@xxxxxxxxx>
• Re: AS assembler variable
  • From: Eric Blake <eblake@xxxxxxxxxx>
• AS assembler variable
  • From: NightStrike <nightstrike@xxxxxxxxx>
• Re: AC_CHECK_FUNCS and gcc with -Werror
  • From: Peter Breitenlohner <peb@xxxxxxxxxxxx>
• Re: AC_CHECK_FUNCS and gcc with -Werror
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: AC_CHECK_FUNCS and gcc with -Werror
  • From: Ralf Corsepius <rc040203@xxxxxxxxxx>
• Re: AC_CHECK_FUNCS and gcc with -Werror
  • From: Steffen Dettmer <steffen.dettmer@xxxxxxxxxxxxxx>
• Re: AC_CHECK_FUNCS and gcc with -Werror
  • From: Steffen Dettmer <steffen.dettmer@xxxxxxxxxxxxxx>
• Re: AC_CHECK_FUNCS and gcc with -Werror
  • From: Ralf Corsepius <rc040203@xxxxxxxxxx>
• Re: AC_CHECK_FUNCS and gcc with -Werror
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: AC_CHECK_FUNCS and gcc with -Werror
  • From: Steffen Dettmer <steffen.dettmer@xxxxxxxxxxxxxx>
• Re: how to handle new subdirectories?
  • From: Steffen Dettmer <steffen.dettmer@xxxxxxxxxxxxxx>
• Re: how to handle new subdirectories?
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: AC_CHECK_FUNCS and gcc with -Werror
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: how to handle new subdirectories?
  • From: Steffen Dettmer <steffen.dettmer@xxxxxxxxxxxxxx>
• Re: AC_CHECK_FUNCS and gcc with -Werror
  • From: Ralf Corsepius <rc040203@xxxxxxxxxx>
• AC_CHECK_FUNCS and gcc with -Werror
  • From: Steffen Dettmer <steffen.dettmer@xxxxxxxxxxxxxx>
• Re: how to handle new subdirectories?
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: confdefs.h not being included by AC_LANG_SOURCE()
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: confdefs.h not being included by AC_LANG_SOURCE()
  • From: "Brian J. Murrell" <brian@xxxxxxx>
• Re: confdefs.h not being included by AC_LANG_SOURCE()
  • From: Eric Blake <ebb9@xxxxxxx>
• Re: confdefs.h not being included by AC_LANG_SOURCE()
  • From: "Brian J. Murrell" <brian@xxxxxxx>
• Re: confdefs.h not being included by AC_LANG_SOURCE()
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: confdefs.h not being included by AC_LANG_SOURCE()
  • From: "Brian J. Murrell" <brian@xxxxxxx>
• Re: configure checks -R and returns errors
  • From: Eric Blake <eblake@xxxxxxxxxx>
• how to handle new subdirectories?
  • From: Steffen Dettmer <steffen.dettmer@xxxxxxxxxxxxxx>
• Re: confdefs.h not being included by AC_LANG_SOURCE()
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: confdefs.h not being included by AC_LANG_SOURCE()
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: confdefs.h not being included by AC_LANG_SOURCE()
  • From: "Brian J. Murrell" <brian@xxxxxxx>
• Re: confdefs.h not being included by AC_LANG_SOURCE()
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: Forcing FC instead of F77
  • From: "Steven G. Johnson" <stevenj@xxxxxxxxxxxx>
• Re: release is imminent
  • From: Tim Rice <tim@xxxxxxxxxxxxxxxx>
• Re: flag issue in AC_PROG_CXX for Sun Studio
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• Re: release is imminent
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: release is imminent
  • From: Vincent Torri <vtorri@xxxxxxxxxxxx>
• Re: flag issue in AC_PROG_CXX for Sun Studio
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: release is imminent
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: Autoupdate and AC 2.65
  • From: NightStrike <nightstrike@xxxxxxxxx>
• Re: flag issue in AC_PROG_CXX for Sun Studio
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: flag issue in AC_PROG_CXX for Sun Studio
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• Re: Autoupdate and AC 2.65
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: release is imminent
  • From: Vincent Torri <vtorri@xxxxxxxxxxxx>
• Re: Explanation in autoconf manual
  • From: Eric Blake <ebb9@xxxxxxx>
• Re: AC_INIT seems to be setting CXXFLAGS
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: flag issue in AC_PROG_CXX for Sun Studio
  • From: Monty Taylor <mordred@xxxxxxxxxxxx>
• Re: flag issue in AC_PROG_CXX for Sun Studio
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: release is imminent
  • From: "Brian J. Murrell" <brian@xxxxxxx>
• Re: release is imminent
  • From: NightStrike <nightstrike@xxxxxxxxx>
• release is imminent
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: Autoupdate and AC 2.65
  • From: NightStrike <nightstrike@xxxxxxxxx>
• Re: Automake conditionals in autoconf
  • From: NightStrike <nightstrike@xxxxxxxxx>
• Re: Automake conditionals in autoconf
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: Invoking AM_GNU_GETTEXT conditionally in configure.ac
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: required version for AS_IF
  • From: Peter Johansson <peterandrejohansson@xxxxxxxxx>
• Re: required version for AS_IF
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Automake conditionals in autoconf
  • From: NightStrike <nightstrike@xxxxxxxxx>
• required version for AS_IF
  • From: Peter Johansson <peterandrejohansson@xxxxxxxxx>
• Re: Autoupdate and AC 2.65
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: Autoupdate and AC 2.65
  • From: NightStrike <nightstrike@xxxxxxxxx>
• Re: Autoscan and automake
  • From: NightStrike <nightstrike@xxxxxxxxx>
• Re: Autoscan and automake
  • From: NightStrike <nightstrike@xxxxxxxxx>
• Autoupdate and AC 2.65
  • From: NightStrike <nightstrike@xxxxxxxxx>
• Re: Autoscan and automake
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Autoscan and automake
  • From: NightStrike <nightstrike@xxxxxxxxx>
• Re: Invoking AM_GNU_GETTEXT conditionally in configure.ac
  • From: David Bruce <davidstuartbruce@xxxxxxxxx>
• Re: Adding LM32 processor support
  • From: Eric Blake <eblake@xxxxxxxxxx>
• Re: How can I check if C++ and Fortran compiler works ?
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Adding LM32 processor support
  • From: Sébastien Bourdeauducq <sebastien.bourdeauducq@xxxxxxxxxxxx>
• Re: How can I check if C++ and Fortran compiler works ?
  • From: "Dr. David Kirkby" <david.kirkby@xxxxxxxxxx>
• Re: How can I check if C++ and Fortran compiler works ?
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• How can I check if C++ and Fortran compiler works ?
  • From: "Dr. David Kirkby" <david.kirkby@xxxxxxxxxx>
• Re: portability of 'printf' command
  • From: Ben Pfaff <blp@xxxxxxxxxxxxxxx>
• Re: portability of 'printf' command
  • From: Thomas Dickey <dickey@xxxxxxx>
• Re: portability of 'printf' command
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• Re: portability of 'printf' command
  • From: Thomas Dickey <dickey@xxxxxxx>
• Re: portability of 'printf' command
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• Re: checking Mac OS X headers
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• portability of 'printf' command
  • From: Bruno Haible <bruno@xxxxxxxxx>
• Re: Invoking AM_GNU_GETTEXT conditionally in configure.ac
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: confdefs.h not being included by AC_LANG_SOURCE()
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: checking Mac OS X headers
  • From: Vincent Torri <vtorri@xxxxxxxxxxxx>
• confdefs.h not being included by AC_LANG_SOURCE()
  • From: "Brian J. Murrell" <brian@xxxxxxx>
• Re: Tips to modernize autotools configuration
  • From: Javier Jardón <javierjc1982@xxxxxxxxx>
• Re: AC_CHECK_DECLS(basename) (Was: Re: Ping: patches required for --enable-build-with-cxx)
  • From: Joern Rennecke <joern.rennecke@xxxxxxxxxxxx>
• Re: AC_CHECK_DECLS(basename) (Was: Re: Ping: patches required for --enable-build-with-cxx)
  • From: Paolo Bonzini <bonzini@xxxxxxx>
• Re: autoconf/automake on multiple platforms/versions
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• autoconf/automake on multiple platforms/versions
  • From: Joris Dobbelsteen <joris@xxxxxxxxxxxxxxxxxxxxx>
• Re: AC_CHECK_DECLS(basename) (Was: Re: Ping: patches required for --enable-build-with-cxx)
  • From: Joern Rennecke <joern.rennecke@xxxxxxxxxxxx>
• Re: AC_CHECK_DECLS(basename) (Was: Re: Ping: patches required for --enable-build-with-cxx)
  • From: Paolo Bonzini <bonzini@xxxxxxx>