Gnu Autoconf

• Thread Index

• Re: autoreconf --clean
  • From: Stepan Kasal <kasal@xxxxxx>
• Re: How do I avoid a specific variable in the Makefile?
  • From: Stepan Kasal <kasal@xxxxxx>
• Re: How do I avoid a specific variable in the Makefile?
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• How do I avoid a specific variable in the Makefile?
  • From: Jules Colding <colding@xxxxxxxxx>
• Re: autoreconf --clean
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: autoreconf --clean
  • From: bob@xxxxxxxxxx (Bob Proulx)
• Re: autoreconf warning message: autom4te: cannotlockautom4te.cache/requests with mode 2: Invalid argument
  • From: bob@xxxxxxxxxx (Bob Proulx)
• RE: autoreconf --clean
  • From: "David Byron" <dbyron@xxxxxxxxxx>
• Re: autoreconf --clean
  • From: bob@xxxxxxxxxx (Bob Proulx)
• RE: autoreconf warning message: autom4te: cannotlockautom4te.cache/requests with mode 2: Invalid argument
  • From: "David Byron" <dbyron@xxxxxxxxxx>
• Re: autoreconf warning message: autom4te: cannot lockautom4te.cache/requests with mode 2: Invalid argument
  • From: bob@xxxxxxxxxx (Bob Proulx)
• autoreconf --clean
  • From: "David Byron" <dbyron@xxxxxxxxxx>
• RE: autoreconf warning message: autom4te: cannot lockautom4te.cache/requests with mode 2: Invalid argument
  • From: "David Byron" <dbyron@xxxxxxxxxx>
• Re: autoreconf warning message: autom4te: cannot lock autom4te.cache/requests with mode 2: Invalid argument
  • From: Andreas Schwab <schwab@xxxxxxx>
• RE: autoreconf warning message: autom4te: cannot lockautom4te.cache/requests with mode 2: Invalid argument
  • From: "David Byron" <dbyron@xxxxxxxxxx>
• Re: How to avoid warning: "PACKAGE_NAME" redefined
  • From: haibin zhang <dragzhb@xxxxxxxxxxxx>
• Re: autoreconf warning message: autom4te: cannot lock autom4te.cache/requests with mode 2: Invalid argument
  • From: Harlan Stenn <stenn@xxxxxxxxxxx>
• autoreconf warning message: autom4te: cannot lock autom4te.cache/requests with mode 2: Invalid argument
  • From: "David Byron" <dbyron@xxxxxxxxxx>
• Re: GNU M4 1.4.8b released (beta release)
  • From: Eric Blake <ebb9@xxxxxxx>
• Re: GNU M4 1.4.8b released (beta release)
  • From: Eric Blake <ebb9@xxxxxxx>
• Re: How to avoid warning: "PACKAGE_NAME" redefined
  • From: Guido Draheim <guidod-2007-@xxxxxx>
• Re: How to avoid warning: "PACKAGE_NAME" redefined
  • From: Stepan Kasal <kasal@xxxxxx>
• Re: How to avoid warning: "PACKAGE_NAME" redefined
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• How to avoid warning: "PACKAGE_NAME" redefined
  • From: haibin zhang <dragzhb@xxxxxxxxxxxx>
• Re: Propagating variables.
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Propagating variables.
  • From: Craig Sanders <cmsan1@xxxxxxxxxxxxxxxxxx>
• Re: Location of declarations in Linux vs FreeBSD, etc.
  • From: Philip Kovacs <kovacsp3@xxxxxxxxxxx>
• Re: ERROR: end of file in string (SOLVED)
  • From: Eric Blake <ebb9@xxxxxxx>
• Re: ERROR: end of file in string (SOLVED)
  • From: "Benjamin Reed" <rangerrick@xxxxxxxxx>
• ERROR: end of file in string
  • From: "Benjamin Reed" <rangerrick@xxxxxxxxx>
• Re: Location of declarations in Linux vs FreeBSD, etc.
  • From: Davide Bolcioni <dblistsub-autoconf@xxxxxxxx>
• Re: Location of declarations in Linux vs FreeBSD, etc.
  • From: Russ Allbery <rra@xxxxxxxxxxxx>
• Re: Location of declarations in Linux vs FreeBSD, etc.
  • From: Russ Allbery <rra@xxxxxxxxxxxx>
• Re: Location of declarations in Linux vs FreeBSD, etc.
  • From: Harlan Stenn <stenn@xxxxxxxxxxx>
• Re: Location of declarations in Linux vs FreeBSD, etc.
  • From: Philip Kovacs <kovacsp3@xxxxxxxxxxx>
• Re: Location of declarations in Linux vs FreeBSD, etc.
  • From: Harlan Stenn <stenn@xxxxxxxxxxx>
• Re: Location of declarations in Linux vs FreeBSD, etc.
  • From: Philip Kovacs <kovacsp3@xxxxxxxxxxx>
• Re: Location of declarations in Linux vs FreeBSD, etc.
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Location of declarations in Linux vs FreeBSD, etc.
  • From: Philip Kovacs <kovacsp3@xxxxxxxxxxx>
• Re: How to substitute variables in script files? (Why is $prefix set to NONE?)
  • From: Stefano Sabatini <stefano.sabatini-lala@xxxxxxxx>
• Re: How to substitute variables in script files? (Why is $prefix set to NONE?)
  • From: Andreas Schwab <schwab@xxxxxxx>
• Re: How to substitute variables in script files? (Why is $prefix set to NONE?)
  • From: Stefano Sabatini <stefano.sabatini-lala@xxxxxxxx>
• Re: How to substitute variables in script files? (Why is $prefix set to NONE?)
  • From: Keith MARSHALL <keith.marshall@xxxxxxxxx>
• How to substitute variables in script files? (Why is $prefix set to NONE?)
  • From: Stefano Sabatini <stefano.sabatini-lala@xxxxxxxx>
• Re: [Fwd: Re: How to cvs checkout SASL]
  • From: Howard Chu <hyc@xxxxxxxxxxxxxxx>
• Re: make after reconfiguring
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: [Fwd: Re: How to cvs checkout SASL]
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: [Fwd: Re: How to cvs checkout SASL]
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• [Fwd: Re: How to cvs checkout SASL]
  • From: Howard Chu <hyc@xxxxxxxxxxxxxxx>
• make after reconfiguring
  • From: Baurzhan Ismagulov <ibr@xxxxxxxxxxx>
• Re: Trying to compile Samba 3 on old OpenStep 4.2 Mach-motorola
  • From: Howard Chu <hyc@xxxxxxxxxxxxxxx>
• Trying to compile Samba 3 on old OpenStep 4.2 Mach-motorola
  • From: "Jennifer Woodward" <jenni.woodward@xxxxxxxxxxxxxx>
• Re: Typo in autoconf.texi
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Typo in autoconf.texi
  • From: Andre Stechert <andre@xxxxxxxxxx>
• Re: Conditional AC_CONFIG_FILES
  • From: Brian <reflection@xxxxxxxxx>
• Re: Conditional AC_CONFIG_FILES
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: Conditional AC_CONFIG_FILES
  • From: Brian <reflection@xxxxxxxxx>
• Re: Conditional AC_CONFIG_FILES
  • From: Brian <reflection@xxxxxxxxx>
• Re: libstdc++ on solaris / rpath / gnulib's havelib macros
  • From: Albert Chin <autoconf@xxxxxxxxxxxxxxxxxxxxxxxxx>
• Re: Conditional AC_CONFIG_FILES
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: Conditional AC_CONFIG_FILES
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• RE: libstdc++ on solaris / rpath / gnulib's havelib macros
  • From: Benoit Sigoure <tsuna@xxxxxxxxxxxxx>
• RE: libstdc++ on solaris / rpath / gnulib's havelib macros
  • From: "David Byron" <dbyron@xxxxxxxxxx>
• Re: libstdc++ on solaris / rpath / gnulib's havelib macros
  • From: Albert Chin <autoconf@xxxxxxxxxxxxxxxxxxxxxxxxx>
• Re: autoheader problem
  • From: Daniel <daniel.rampanelli@xxxxxxxxx>
• Conditional AC_CONFIG_FILES
  • From: Brian <reflection@xxxxxxxxx>
• RE: help linking shared libraries / rpath
  • From: ericblake@xxxxxxxxxxx (Eric Blake)
• Re: OT: cross platform tests? SF compile farm is dead
  • From: Thomas Dickey <dickey@xxxxxxx>
• Re: OT: cross platform tests? SF compile farm is dead
  • From: Guido Draheim <guidod-2007-@xxxxxx>
• Re: OT: cross platform tests? SF compile farm is dead
  • From: Thomas Dickey <dickey@xxxxxxx>
• Re: OT: cross platform tests? SF compile farm is dead
  • From: Dalibor Topic <robilad@xxxxxxxxx>
• Re: OT: cross platform tests? SF compile farm is dead
  • From: Dirk <noisyb@xxxxxxx>
• Re: OT: cross platform tests? SF compile farm is dead
  • From: Guido Draheim <guidod-2007-@xxxxxx>
• Re: OT: cross platform tests? SF compile farm is dead
  • From: Dirk <noisyb@xxxxxxx>
• OT: cross platform tests? SF compile farm is dead
  • From: Guido Draheim <guidod-2007-@xxxxxx>
• RE: help linking shared libraries / rpath
  • From: "David Byron" <dbyron@xxxxxxxxxx>
• Re: autoheader problem
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Trying to add more targets to my make install
  • From: "Luc Gallant" <lucgallant@xxxxxxxxx>
• autoheader problem
  • From: Daniel <daniel.rampanelli@xxxxxxxxx>
• RE: libstdc++ on solaris / rpath / gnulib's havelib macros
  • From: "David Byron" <dbyron@xxxxxxxxxx>
• RE: libstdc++ on solaris / rpath / gnulib's havelib macros
  • From: "David Byron" <dbyron@xxxxxxxxxx>
• libstdc++ on solaris / rpath / gnulib's havelib macros
  • From: "David Byron" <dbyron@xxxxxxxxxx>
• RE: help linking shared libraries / rpath
  • From: "David Byron" <dbyron@xxxxxxxxxx>
• Re: help linking shared libraries / rpath
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• help linking shared libraries / rpath
  • From: "David Byron" <dbyron@xxxxxxxxxx>
• Re: more m4 underquotations
  • From: Bruno Haible <bruno@xxxxxxxxx>
• Re: more m4 underquotations
  • From: ericblake@xxxxxxxxxxx (Eric Blake)
• Re: more m4 underquotations
  • From: Bruno Haible <bruno@xxxxxxxxx>
• Re: [newbie] How to check for an "install" program
  • From: Ben Pfaff <blp@xxxxxxxxxxxxxxx>
• Re: [newbie] How to check for an "install" program
  • From: Stefano Sabatini <stefano.sabatini-lala@xxxxxxxx>
• Re: [newbie] How to check for an "install" program
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: Why "unknown"?
  • From: Ralf Corsepius <rc040203@xxxxxxxxxx>
• Re: Why "unknown"?
  • From: Matthew Woehlke <mw_triad@xxxxxxxxxxxxxxxxxxxxx>
• My autoconf replacement
  • From: Dirk <noisyb@xxxxxxx>
• [newbie] How to check for an "install" program
  • From: Stefano Sabatini <stefano.sabatini-lala@xxxxxxxx>
• Re: Why "unknown"?
  • From: Bob Rossi <bob_rossi@xxxxxxx>
• Re: Why "unknown"?
  • From: Warren Young <warren@xxxxxxxxxxx>
• Re: Why "unknown"?
  • From: Matthew Woehlke <mw_triad@xxxxxxxxxxxxxxxxxxxxx>
• Re: Why "unknown"?
  • From: Andreas Schwab <schwab@xxxxxxx>
• Why "unknown"?
  • From: Mike Sharov <msharov@xxxxxxxxxxxx>
• abs_top_srcdir
  • From: Bob Rossi <bob_rossi@xxxxxxx>
• Re: why not check $PATH for m4?
  • From: Eric Blake <ebb9@xxxxxxx>
• Re: acincludedir -populating an m4/ subdirectory
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: why not check $PATH for m4?
  • From: Chris Pickett <chris.pickett@xxxxxxxxxxxxxx>
• Re: why not check $PATH for m4?
  • From: Eric Blake <ebb9@xxxxxxx>
• macro_to_html + macro_to xml unix manpage
  • From: Guido Draheim <guidod-2007-@xxxxxx>
• acincludedir -populating an m4/ subdirectory
  • From: Guido Draheim <guidod-2007-@xxxxxx>
• Re: how to check type size
  • From: Andreas Schwab <schwab@xxxxxxx>
• Re: why not check $PATH for m4?
  • From: Chris Pickett <chris.pickett@xxxxxxxxxxxxxx>
• why not check $PATH for m4?
  • From: Chris Pickett <chris.pickett@xxxxxxxxxxxxxx>
• Re: how to check type size
  • From: Andrew Makhorin <mao@xxxxxxx>
• Re: how to check type size
  • From: Andreas Schwab <schwab@xxxxxxx>
• how to check type size
  • From: Andrew Makhorin <mao@xxxxxxx>
• Re: m4sugar doc example
  • From: Eric Blake <ebb9@xxxxxxx>
• m4sugar doc example [Was: enforcing the use of string.h related modules]
  • From: Eric Blake <ebb9@xxxxxxx>
• Re: "has changed since the previous run"
  • From: DJ Delorie <dj@xxxxxxxxxx>
• Re: "has changed since the previous run"
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: "has changed since the previous run"
  • From: Ralf Corsepius <ralf.corsepius@xxxxxxxxx>
• Re: "has changed since the previous run"
  • From: Ralf Corsepius <ralf.corsepius@xxxxxxxxx>
• Re: "has changed since the previous run"
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: "has changed since the previous run"
  • From: DJ Delorie <dj@xxxxxxxxxx>
• Re: "has changed since the previous run"
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: "has changed since the previous run"
  • From: DJ Delorie <dj@xxxxxxxxxx>
• Re: "has changed since the previous run"
  • From: DJ Delorie <dj@xxxxxxxxxx>
• Re: "has changed since the previous run"
  • From: DJ Delorie <dj@xxxxxxxxxx>
• Re: any reason not to enforce the build requirement: m4 >= 1.4.4 ?
  • From: Jim Meyering <jim@xxxxxxxxxxxx>
• Re: any reason not to enforce the build requirement: m4 >= 1.4.4 ?
  • From: Eric Blake <ebb9@xxxxxxx>
• Re: "has changed since the previous run"
  • From: DJ Delorie <dj@xxxxxxxxxx>
• Re: "has changed since the previous run"
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: "has changed since the previous run"
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: "has changed since the previous run"
  • From: DJ Delorie <dj@xxxxxxxxxx>
• any reason not to enforce the build requirement: m4 >= 1.4.4 ?
  • From: Jim Meyering <jim@xxxxxxxxxxxx>
• Re: "has changed since the previous run"
  • From: Benoit Sigoure <tsuna@xxxxxxxxxxxxx>
• Re: "has changed since the previous run"
  • From: Andreas Schwab <schwab@xxxxxxx>
• Re: "has changed since the previous run"
  • From: DJ Delorie <dj@xxxxxxxxxx>
• Re: "has changed since the previous run"
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: "has changed since the previous run"
  • From: DJ Delorie <dj@xxxxxxxxxx>
• Re: "has changed since the previous run"
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• "has changed since the previous run"
  • From: DJ Delorie <dj@xxxxxxxxxx>
• Re: read-only $ac_executable_extensions
  • From: Tim Van Holder <tim.van.holder@xxxxxxxxxx>
• Windows / Interix / WGCC
  • From: "Duft Markus" <Markus.Duft@xxxxxxxxxx>
• Re: read-only $ac_executable_extensions
  • From: Paolo Bonzini <paolo.bonzini@xxxxxxxxxxx>
• Re: read-only $ac_executable_extensions
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• read-only $ac_executable_extensions
  • From: Paolo Bonzini <paolo.bonzini@xxxxxxxxxxx>
• Re: Problems upgrading
  • From: Thomas Dickey <dickey@xxxxxxx>
• Re: Problems upgrading
  • From: Eric Blake <ebb9@xxxxxxx>
• Re: Problems upgrading
  • From: Thomas Dickey <dickey@xxxxxxx>
• Re: Problems upgrading
  • From: Ralf Corsepius <rc040203@xxxxxxxxxx>
• Re: M4 syntax $11 vs. ${11}
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• question about native MS support -- creating .pdb files during configure
  • From: "David Byron" <dbyron@xxxxxxxxxx>
• Re: Problems upgrading
  • From: Thomas Dickey <dickey@xxxxxxx>
• Re: Problems upgrading
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Problems upgrading
  • From: "Skip Kimpel - Magicgate Software, Inc." <skip@xxxxxxxxxxxxx>
• Re: M4 syntax $11 vs. ${11}
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: how to check for a C++ class library
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: M4 syntax $11 vs. ${11}
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: M4 syntax $11 vs. ${11}
  • From: Eric Blake <ebb9@xxxxxxx>
• how to check for a C++ class library
  • From: Satya <satyakiran@xxxxxxxxx>
• Re: path separator
  • From: Matthew Woehlke <mw_triad@xxxxxxxxxxxxxxxxxxxxx>
• Re: path separator
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: path separator
  • From: Brian Dessent <brian@xxxxxxxxxxx>
• Re: path separator
  • From: Matthew Woehlke <mw_triad@xxxxxxxxxxxxxxxxxxxxx>
• Re: path separator
  • From: Keith MARSHALL <keith.marshall@xxxxxxxxx>
• Re: path separator
  • From: Keith MARSHALL <keith.marshall@xxxxxxxxx>
• Re: path separator
  • From: Keith MARSHALL <keith.marshall@xxxxxxxxx>
• Re: path separator (was: target triplet)
  • From: Brian Dessent <brian@xxxxxxxxxxx>
• Re: path separator (was: target triplet)
  • From: Matthew Woehlke <mw_triad@xxxxxxxxxxxxxxxxxxxxx>
• Re: path separator (was: target triplet)
  • From: Brian Dessent <brian@xxxxxxxxxxx>
• Re: path separator
  • From: Brian Dessent <brian@xxxxxxxxxxx>
• Re: path separator
  • From: Bob Rossi <bob_rossi@xxxxxxx>
• Re: path separator
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: Use "$(MKDIR_P) sys", not race-prone "test -d sys || mkdir sys".
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: path separator
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: path separator (was: target triplet)
  • From: Matthew Woehlke <mw_triad@xxxxxxxxxxxxxxxxxxxxx>
• Re: path separator (was: target triplet)
  • From: Keith MARSHALL <keith.marshall@xxxxxxxxx>
• Re: path separator (was: target triplet)
  • From: Keith MARSHALL <keith.marshall@xxxxxxxxx>
• Re: path separator (was: target triplet)
  • From: Matthew Woehlke <mw_triad@xxxxxxxxxxxxxxxxxxxxx>
• Re: order to run autotools
  • From: Ralf Corsepius <rc040203@xxxxxxxxxx>
• Re: order to run autotools
  • From: Bob Rossi <bob_rossi@xxxxxxx>
• Re: order to run autotools
  • From: Ralf Corsepius <rc040203@xxxxxxxxxx>
• order to run autotools
  • From: Bob Rossi <bob_rossi@xxxxxxx>
• Re: path separator (was: target triplet)
  • From: Keith MARSHALL <keith.marshall@xxxxxxxxx>
• Re: path separator
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: Use "$(MKDIR_P) sys", not race-prone "test -d sys || mkdir sys".
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: path separator (was: target triplet)
  • From: Bob Rossi <bob_rossi@xxxxxxx>
• path separator (was: target triplet)
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: Use "$(MKDIR_P) sys", not race-prone "test -d sys || mkdir sys".
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: Use "$(MKDIR_P) sys", not race-prone "test -d sys || mkdir sys".
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: Use "$(MKDIR_P) sys", not race-prone "test -d sys || mkdir sys".
  • From: Andreas Schwab <schwab@xxxxxxx>
• Re: Use "$(MKDIR_P) sys", not race-prone "test -d sys || mkdir sys".
  • From: Bruno Haible <bruno@xxxxxxxxx>
• Re: Use "$(MKDIR_P) sys", not race-prone "test -d sys || mkdir sys".
  • From: Jim Meyering <jim@xxxxxxxxxxxx>
• Re: How to cancel flags set by AC_LANG_WERROR?
  • From: Keith MARSHALL <keith.marshall@xxxxxxxxx>
• Re: How to cancel flags set by AC_LANG_WERROR?
  • From: Andrey Simonenko <simon@xxxxxxxxxxxxxxxxxxxxxx>
• Re: target triplet
  • From: Keith MARSHALL <keith.marshall@xxxxxxxxx>
• Re: target triplet
  • From: Keith MARSHALL <keith.marshall@xxxxxxxxx>
• RE: multiple inclusion guard for config.h
  • From: David Fang <fang@xxxxxxxxxxxxxxx>
• Re: target triplet
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: target triplet
  • From: Brian Dessent <brian@xxxxxxxxxxx>
• Re: target triplet
  • From: Bob Rossi <bob_rossi@xxxxxxx>
• Re: target triplet
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• target triplet
  • From: Bob Rossi <bob_rossi@xxxxxxx>
• Re: How to cancel flags set by AC_LANG_WERROR?
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• RE: multiple inclusion guard for config.h
  • From: "David Byron" <dbyron@xxxxxxxxxx>
• Re: How to cancel flags set by AC_LANG_WERROR?
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: multiple inclusion guard for config.h
  • From: Russ Allbery <rra@xxxxxxxxxxxx>
• Re: multiple inclusion guard for config.h
  • From: Ed Hartnett <ed@xxxxxxxxxxxxxxxx>
• RE: multiple inclusion guard for config.h
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• RE: multiple inclusion guard for config.h
  • From: "David Byron" <dbyron@xxxxxxxxxx>
• Re: multiple inclusion guard for config.h
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• multiple inclusion guard for config.h
  • From: "David Byron" <dbyron@xxxxxxxxxx>
• Re: linking small programs with AC_LINK_IFELSE
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: M4 syntax $11 vs. ${11}
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: M4 syntax $11 vs. ${11}
  • From: Eric Blake <ebb9@xxxxxxx>
• Re: linking small programs with AC_LINK_IFELSE
  • From: Benoit Sigoure <tsuna@xxxxxxxxxxxxx>
• Re: linking small programs with AC_LINK_IFELSE
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: linking small programs with AC_LINK_IFELSE
  • From: Bob Rossi <bob_rossi@xxxxxxx>
• Re: M4 syntax $11 vs. ${11}
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• M4 syntax $11 vs. ${11}
  • From: Eric Blake <ebb9@xxxxxxx>
• Re: Using --enable-debug and defining a macro from it...?
  • From: Matthew Woehlke <mw_triad@xxxxxxxxxxxxxxxxxxxxx>
• Re: Using --enable-debug and defining a macro from it...?
  • From: Ed Hartnett <ed@xxxxxxxxxxxxxxxx>
• Re: Using --enable-debug and defining a macro from it...?
  • From: Braden McDaniel <braden@xxxxxxxxxxxxx>
• Using --enable-debug and defining a macro from it...?
  • From: Matthew Woehlke <mw_triad@xxxxxxxxxxxxxxxxxxxxx>
• Re: KDE 3.5.5 autoconf errors
  • From: Matthew Woehlke <mw_triad@xxxxxxxxxxxxxxxxxxxxx>
• Re: KDE 3.5.5 autoconf errors
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: what does not belong in a distribution
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• what does not belong in a distribution
  • From: Thomas Porschberg <thomas@xxxxxxxxxxxxxxx>
• Re: help a newbie?
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: help a newbie?
  • From: "Nick Rizzolo" <rizzolo@xxxxxxxxx>
• Re: help a newbie?
  • From: Eric Blake <ebb9@xxxxxxx>
• Re: help a newbie?
  • From: bob@xxxxxxxxxx (Bob Proulx)
• GNU Mach's usage of the Auto* tools (was: [OT] avoid long ac_user_opts line in configure)
  • From: Thomas Schwinge <tschwinge@xxxxxxx>
• Re: help a newbie?
  • From: Benoit Sigoure <tsuna@xxxxxxxxxxxxx>
• help a newbie?
  • From: "Nick Rizzolo" <rizzolo@xxxxxxxxx>
• RE: Autoconf manual's coverage of signed integer overflow & portability
  • From: "Meissner, Michael" <michael.meissner@xxxxxxx>
• Re: KDE 3.5.5 autoconf errors
  • From: Matthew Woehlke <mw_triad@xxxxxxxxxxxxxxxxxxxxx>
• Re: KDE 3.5.5 autoconf errors
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: Problems with definitions containing and underscore
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: problem with cached values
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• KDE 3.5.5 autoconf errors (was: "Present But Cannot Be Compiled" - anyone want reports?)
  • From: Matthew Woehlke <mw_triad@xxxxxxxxxxxxxxxxxxxxx>
• Re: "Present But Cannot Be Compiled" - anyone want reports?
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: "Present But Cannot Be Compiled" - anyone want reports?
  • From: Matthew Woehlke <mw_triad@xxxxxxxxxxxxxxxxxxxxx>
• Re: "Present But Cannot Be Compiled" - anyone want reports?
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• "Present But Cannot Be Compiled" - anyone want reports?
  • From: Matthew Woehlke <mw_triad@xxxxxxxxxxxxxxxxxxxxx>
• Re: linking small programs with AC_LINK_IFELSE
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: AC_PROG_CC_C89
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: Some doubts
  • From: Stepan Kasal <kasal@xxxxxx>
• Some doubts
  • From: shamju joseph <shamju.joseph@xxxxxxxxx>
• Re: target triplet
  • From: "Steven G. Johnson" <stevenj@xxxxxxxxxxxx>
• Re: AC_PROG_CC_C89
  • From: Harlan Stenn <stenn@xxxxxxxxxxx>
• Re: AC_PROG_CC_C89
  • From: "Steven G. Johnson" <stevenj@xxxxxxxxxxxx>
• Re: Autoconf manual's coverage of signed integer overflow & portability
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: Autoconf manual's coverage of signed integer overflow & portability
  • From: Gabriel Dos Reis <gdr@xxxxxxxxxxxxxxxxxxxxxxxx>
• Re: Autoconf manual's coverage of signed integer overflow & portability
  • From: Gabriel Dos Reis <gdr@xxxxxxxxxxxxxxxxxxxxxxxx>
• Re: Autoconf manual's coverage of signed integer overflow & portability
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: Autoconf manual's coverage of signed integer overflow & portability
  • From: Andrew Pinski <pinskia@xxxxxxxxxxxxxx>
• Re: Autoconf manual's coverage of signed integer overflow & portability
  • From: Russell Shaw <rjshaw@xxxxxxxxxxxxxxx>
• Re: Autoconf manual's coverage of signed integer overflow & portability
  • From: Andrew Pinski <pinskia@xxxxxxxxxxxxxx>
• Re: Autoconf manual's coverage of signed integer overflow & portability
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: Autoconf manual's coverage of signed integer overflow & portability
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: Autoconf manual's coverage of signed integer overflow & portability
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• AC_PROG_CC_C89
  • From: Harlan Stenn <stenn@xxxxxxxxxxx>
• Re: Autoconf manual's coverage of signed integer overflow & portability
  • From: Andrew Pinski <pinskia@xxxxxxxxxxxxxx>
• Re: Autoconf manual's coverage of signed integer overflow & portability
  • From: Russell Shaw <rjshaw@xxxxxxxxxxxxxxx>
• Re: Autoconf manual's coverage of signed integer overflow & portability
  • From: Robert Dewar <dewar@xxxxxxxxxxx>
• Re: Autoconf manual's coverage of signed integer overflow & portability
  • From: kenner@xxxxxxxxxxxxxxxxxxx (Richard Kenner)
• Re: Autoconf manual's coverage of signed integer overflow & portability
  • From: Andrew Pinski <pinskia@xxxxxxxxxxxxxx>
• Re: Autoconf manual's coverage of signed integer overflow & portability
  • From: kenner@xxxxxxxxxxxxxxxxxxx (Richard Kenner)
• Re: Autoconf manual's coverage of signed integer overflow & portability
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Autoconf manual's coverage of signed integer overflow & portability
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: problem with cached values
  • From: Vincent Torri <vtorri@xxxxxxxxxxxx>
• Re: problem with cached values
  • From: Vincent Torri <vtorri@xxxxxxxxxxxx>
• Re: problem with cached values
  • From: Eric Blake <ebb9@xxxxxxx>
• problem with cached values
  • From: Vincent Torri <vtorri@xxxxxxxxxxxx>
• Re: ``install -C'' / unnecessarily updating time stamps
  • From: Akim Demaille <akim.demaille@xxxxxxx>
• Re: ``install -C'' / unnecessarily updating time stamps
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: ``install -C'' / unnecessarily updating time stamps
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: ``install -C'' / unnecessarily updating time stamps
  • From: Thomas Schwinge <tschwinge@xxxxxxx>
• Re: ``install -C'' / unnecessarily updating time stamps
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: ``install -C'' / unnecessarily updating time stamps
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: ``install -C'' / unnecessarily updating time stamps
  • From: Benoit Sigoure <tsuna@xxxxxxxxxxxxx>
• Re: ``install -C'' / unnecessarily updating time stamps
  • From: Benoit Sigoure <tsuna@xxxxxxxxxxxxx>
• Re: ``install -C'' / unnecessarily updating time stamps
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: target triplet
  • From: Harlan Stenn <stenn@xxxxxxxxxxx>
• Re: target triplet
  • From: Brian Dessent <brian@xxxxxxxxxxx>
• target triplet
  • From: Bob Rossi <bob_rossi@xxxxxxx>
• ``install -C'' / unnecessarily updating time stamps
  • From: Thomas Schwinge <tschwinge@xxxxxxx>
• How to cancel flags set by AC_LANG_WERROR?
  • From: Andrey Simonenko <simon@xxxxxxxxxxxxxxxxxxxxxx>
• Problems with definitions containing and underscore
  • From: chinlu chinawa <chinluchinawa@xxxxxxxxxxx>
• linking small programs with AC_LINK_IFELSE
  • From: Bob Rossi <bob_rossi@xxxxxxx>
• Re: disabling -O on gcc platforms
  • From: "Christoph Rupp" <chris@xxxxxxxx>
• Re: disabling -O on gcc platforms
  • From: Robert Schwebel <r.schwebel@xxxxxxxxxxxxxx>
• Re: disabling -O on gcc platforms
  • From: "Christoph Rupp" <chris@xxxxxxxx>
• Re: disabling -O on gcc platforms
  • From: Robert Schwebel <r.schwebel@xxxxxxxxxxxxxx>
• Re: proposal - command-line option checking
  • From: "Steven G. Johnson" <stevenj@xxxxxxxxxxxx>
• disabling -O on gcc platforms
  • From: Christoph Rupp <chris@xxxxxxxx>
• Re: proposal - command-line option checking
  • From: "Steven G. Johnson" <stevenj@xxxxxxxxxxxx>
• do not grep config.status internals
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• GNUAutconf IPV6 Testing Strategy (WAS: [Fwd: [Bacula-devel] GNU autconf macro for HAVE_IPV6 check on NetBSD])
  • From: "Brian A. Seklecki" <bseklecki@xxxxxxxxxxxxxxxxxxxxxxx>
• Re: proposal - command-line option checking
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• Re: proposal - command-line option checking
  • From: Matthew Woehlke <mw_triad@xxxxxxxxxxxxxxxxxxxxx>
• Re: proposal - command-line option checking
  • From: "Steven G. Johnson" <stevenj@xxxxxxxxxxxx>
• Re: proposal - command-line option checking
  • From: "Steven G. Johnson" <stevenj@xxxxxxxxxxxx>
• Re: proposal - command-line option checking
  • From: "Steven G. Johnson" <stevenj@xxxxxxxxxxxx>
• Re: proposal - command-line option checking
  • From: Matthew Woehlke <mw_triad@xxxxxxxxxxxxxxxxxxxxx>
• Re: proposal - command-line option checking
  • From: Matthew Woehlke <mw_triad@xxxxxxxxxxxxxxxxxxxxx>
• Re: proposal - command-line option checking
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: proposal - command-line option checking
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• Re: proposal - command-line option checking
  • From: Matthew Woehlke <mw_triad@xxxxxxxxxxxxxxxxxxxxx>
• note of thanks to Ralf in the netCDF RELEASE notes...
  • From: Ed Hartnett <ed@xxxxxxxxxxxxxxxx>
• Re: proposal - command-line option checking
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: proposal - command-line option checking
  • From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
• Re: proposal - command-line option checking
  • From: Ed Hartnett <ed@xxxxxxxxxxxxxxxx>
• Re: proposal - command-line option checking
  • From: Benoit Sigoure <tsuna@xxxxxxxxxxxxx>
• Re: proposal - command-line option checking
  • From: Harlan Stenn <stenn@xxxxxxxxxxx>
• Re: proposal - command-line option checking
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• proposal - command-line option checking
  • From: "Steven G. Johnson" <stevenj@xxxxxxxxxxxx>
• Re: Stack direction check fails with optimizations
  • From: Matthew Woehlke <mw_triad@xxxxxxxxxxxxxxxxxxxxx>
• Re: Stack direction check fails with optimizations
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: Stack direction check fails with optimizations
  • From: Roger While <simrw@xxxxxxxxxxxx>
• Re: Stack direction check fails with optimizations
  • From: Harlan Stenn <stenn@xxxxxxxxxxx>
• Re: Stack direction check fails with optimizations
  • From: Matthew Woehlke <mw_triad@xxxxxxxxxxxxxxxxxxxxx>
• Re: Stack direction check fails with optimizations
  • From: "Peter O'Gorman" <peter@xxxxxxxxx>
• Re: Stack direction check fails with optimizations
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: Stack direction check fails with optimizations
  • From: Andreas Schwab <schwab@xxxxxxx>
• Re: Stack direction check fails with optimizations
  • From: Roger While <simrw@xxxxxxxxxxxx>
• Re: config.sub...
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• config.sub...
  • From: "Ben Bergen" <ben.bergen@xxxxxxxxx>
• Stack direction check fails with optimizations
  • From: "Peter O'Gorman" <peter@xxxxxxxxx>
• Re: AC_C_CONST with C++
  • From: Lorenzo Bettini <bettini@xxxxxxxxxxxx>
• Autoconf test version 2.61a released
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: Mac OS X.4.8 build problem -- new macro for Autoconf
  • From: "Peter O'Gorman" <peter@xxxxxxxxx>
• Re: AC_C_CONST with C++
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: AC_C_CONST with C++
  • From: Harlan Stenn <stenn@xxxxxxxxxxx>
• Re: AC_C_CONST with C++
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• AC_C_CONST with C++
  • From: Lorenzo Bettini <bettini@xxxxxxxxxxxx>
• Re: Mac OS X.4.8 build problem -- new macro for Autoconf
  • From: Bruce Korb <bkorb@xxxxxxx>
• Re: Usage of AS_FOR_TARGET
  • From: Stepan Kasal <kasal@xxxxxx>
• Re: Usage of AS_FOR_TARGET
  • From: Eric Blake <ebb9@xxxxxxx>
• Re: Usage of AS_FOR_TARGET
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Usage of AS_FOR_TARGET
  • From: Eric Blake <ebb9@xxxxxxx>
• Re: Version defines in config.h
  • From: Stepan Kasal <kasal@xxxxxx>
• Version defines in config.h
  • From: Jerker Bäck <jerker.back@xxxxxxxxx>
• Re: After upgrade autoconf from 1.13 to 2.57, I experienced some problems - HELP
  • From: Thomas Dickey <dickey@xxxxxxx>
• Re: After upgrade autoconf from 1.13 to 2.57, I experienced some problems - HELP
  • From: Andreas Schwab <schwab@xxxxxxx>
• Re: After upgrade autoconf from 1.13 to 2.57, I experienced some problems - HELP
  • From: Thomas Dickey <dickey@xxxxxxx>
• Re: After upgrade autoconf from 1.13 to 2.57, I experienced some problems - HELP
  • From: Andreas Schwab <schwab@xxxxxxx>
• Re: AC_CONFIG_SUBDIRS
  • From: Bob Rossi <bob_rossi@xxxxxxx>
• Re: After upgrade autoconf from 1.13 to 2.57, I experienced some problems - HELP
  • From: Thomas Dickey <dickey@xxxxxxx>
• RE: After upgrade autoconf from 1.13 to 2.57, I experienced some problems - HELP
  • From: "J.R. Yang \(jryang\)" <jryang@xxxxxxxxx>
• Re: After upgrade autoconf from 1.13 to 2.57, I experienced some problems - HELP
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: After upgrade autoconf from 1.13 to 2.57, I experienced some problems - HELP
  • From: Thomas Dickey <dickey@xxxxxxx>
• Re: After upgrade autoconf from 1.13 to 2.57, I experienced some problems - HELP
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: AC_CONFIG_SUBDIRS
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• After upgrade autoconf from 1.13 to 2.57, I experienced some problems - HELP
  • From: "J.R. Yang \(jryang\)" <jryang@xxxxxxxxx>
• AC_CONFIG_SUBDIRS
  • From: Bob Rossi <bob_rossi@xxxxxxx>
• Re: AC_CONFIG_HEADERS and autoheader
  • From: Stepan Kasal <kasal@xxxxxx>
• Re: AC_CONFIG_HEADERS and autoheader
  • From: Patrick Welche <prlw1@xxxxxxxxxxxxxx>
• Re: AC_CONFIG_HEADERS and autoheader
  • From: Stepan Kasal <kasal@xxxxxx>
• Re: AC_CONFIG_HEADERS and autoheader
  • From: Patrick Welche <prlw1@xxxxxxxxxxxxxx>
• Re: AC_CONFIG_HEADERS and autoheader
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: AC_CONFIG_HEADERS and autoheader
  • From: Stepan Kasal <kasal@xxxxxx>
• Re: AC_CONFIG_HEADERS and autoheader
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• AC_CONFIG_HEADERS and autoheader
  • From: Patrick Welche <prlw1@xxxxxxxxxxxxxx>
• Re: Problem using autoreconf
  • From: Stepan Kasal <kasal@xxxxxx>
• Re: Help with rewriting compile rules.
  • From: Stepan Kasal <kasal@xxxxxx>
• Re: Help with rewriting compile rules.
  • From: Charles Zhang <czhang@xxxxxxxxxxxxxxxx>
• Re: cross compiling AC_CHECK_SIZEOF
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• cross compiling AC_CHECK_SIZEOF
  • From: Bob Rossi <bob_rossi@xxxxxxx>
• Re: cygwin -mno-cygwin AC_CHECK_SIZEOF
  • From: Eric Blake <ebb9@xxxxxxx>
• Re: cygwin -mno-cygwin AC_CHECK_SIZEOF
  • From: Keith MARSHALL <keith.marshall@xxxxxxxxx>
• Re: cygwin -mno-cygwin AC_CHECK_SIZEOF
  • From: Bob Rossi <bob_rossi@xxxxxxx>
• Re: Problem using autoreconf
  • From: Eric Blake <ebb9@xxxxxxx>
• Re: cygwin -mno-cygwin AC_CHECK_SIZEOF
  • From: Igor Peshansky <pechtcha@xxxxxxxxxx>
• Problem using autoreconf
  • From: gaurav khanna <khannag@xxxxxxxxxxxxxxxxxx>
• Help with rewriting compile rules.
  • From: Charles Zhang <zhangcharles@xxxxxxxxx>
• Re: cygwin -mno-cygwin AC_CHECK_SIZEOF
  • From: Eric Blake <ebb9@xxxxxxx>
• Re: cygwin -mno-cygwin AC_CHECK_SIZEOF
  • From: Bob Rossi <bob_rossi@xxxxxxx>
• Re: Help with rewriting compile rules.
  • From: Charles Zhang <czhang@xxxxxxxxxxxxxxxx>
• Re: cygwin -mno-cygwin AC_CHECK_SIZEOF
  • From: Howard Chu <hyc@xxxxxxxxxxxxxxx>
• Re: cygwin -mno-cygwin AC_CHECK_SIZEOF
  • From: Eric Blake <ebb9@xxxxxxx>
• Re: Help with rewriting compile rules.
  • From: Eric Blake <ebb9@xxxxxxx>
• cygwin -mno-cygwin AC_CHECK_SIZEOF
  • From: Bob Rossi <bob_rossi@xxxxxxx>
• Help with rewriting compile rules.
  • From: Charles Zhang <czhang@xxxxxxxxxxxxxxxx>
• buildconf has error with autoconf version 2.57...
  • From: "J.R. Yang \(jryang\)" <jryang@xxxxxxxxx>
• Re: [Autogen-users] autogen 5.8.7 / Mac OS X.4.8 build problem
  • From: "Bruce Korb" <bruce.korb@xxxxxxxxx>
• Re: [Autogen-users] autogen 5.8.7 / Mac OS X.4.8 build problem
  • From: Stepan Kasal <kasal@xxxxxx>
• Removing AC_FUNC_SETVBUF_REVERSED from Autoconf
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• AC_FUNC_SETVBUF_REVERSED - shouldn't it be the other way around?
  • From: Jerker Bäck <jerker.back@xxxxxxx>
• Re: [Autogen-users] autogen 5.8.7 / Mac OS X.4.8 build problem
  • From: "Bruce Korb" <bruce.korb@xxxxxxxxx>
• Re: [Autogen-users] autogen 5.8.7 / Mac OS X.4.8 build problem
  • From: Stepan Kasal <kasal@xxxxxx>
• Re: managing ocaml dependencies
  • From: Guillaume Rousse <Guillaume.Rousse@xxxxxxxx>
• Re: [Autogen-users] autogen 5.8.7 / Mac OS X.4.8 build problem
  • From: "Bruce Korb" <bruce.korb@xxxxxxxxx>
• Re: using builddir/srcdir at configure time
  • From: David Fang <fang@xxxxxxxxxxxxxxx>
• Re: [Autogen-users] autogen 5.8.7 / Mac OS X.4.8 build problem
  • From: Bruce Korb <Bruce.Korb@xxxxxxxxx>
• Re: using builddir/srcdir at configure time
  • From: Andreas Schwab <schwab@xxxxxxx>
• using builddir/srcdir at configure time
  • From: karl@xxxxxxxxxxxxxxx (Karl Berry)
• Re: [Autogen-users] autogen 5.8.7 / Mac OS X.4.8 build problem
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: [Autogen-users] autogen 5.8.7 / Mac OS X.4.8 build problem
  • From: Bruce Korb <Bruce.Korb@xxxxxxxxx>
• Re: managing ocaml dependencies
  • From: Guillaume Rousse <Guillaume.Rousse@xxxxxxxx>
• GNU M4 1.4.8 released
  • From: Eric Blake <ebb9@xxxxxxx>
• Getting the value of a user-defined configure variable into config.h
  • From: Brian <reflection@xxxxxxxxx>
• Re: patch to invalidate Autom4te cache upon upgrade
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: patch to invalidate Autom4te cache upon upgrade
  • From: Ben Pfaff <blp@xxxxxxxxxxxxxxx>
• Autoconf 2.61 released
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: managing ocaml dependencies
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: patch to invalidate Autom4te cache upon upgrade
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: autoconf, pkg-config and cross-compiling
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• autoconf, pkg-config and cross-compiling
  • From: Chris Ross <chris.ross@xxxxxxxxxxxx>
• Re: [Caml-list] managing ocaml dependencies
  • From: skaller <skaller@xxxxxxxxxxxxxxxxxxxxx>
• Re: [Caml-list] managing ocaml dependencies
  • From: "Nicolas Pouillard" <nicolas.pouillard@xxxxxxxx>
• Re: [Caml-list] managing ocaml dependencies
  • From: Jean-Christophe Filliatre <filliatr@xxxxxx>
• Re: [Caml-list] managing ocaml dependencies
  • From: skaller <skaller@xxxxxxxxxxxxxxxxxxxxx>
• managing ocaml dependencies
  • From: Guillaume Rousse <Guillaume.Rousse@xxxxxxxx>
• autoconf within GCC
  • From: Basile STARYNKEVITCH <basile@xxxxxxxxxxxxxxxxx>
• Re: Install Autoconf's .m4f files into /var?
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Install Autoconf's .m4f files into /var?
  • From: Ben Pfaff <blp@xxxxxxxxxxxxxxx>
• Re: systems requiring exit?
  • From: Thomas Dickey <dickey@xxxxxxx>
• Re: systems requiring exit?
  • From: Matthew Woehlke <mw_triad@xxxxxxxxxxxxxxxxxxxxx>
• Integrating Code Generator
  • From: "Paulo J. Matos" <pocm@xxxxxxxxxxx>
• Re: systems requiring exit?
  • From: Thomas Dickey <dickey@xxxxxxx>
• Re: systems requiring exit?
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: systems requiring exit?
  • From: Howard Chu <hyc@xxxxxxxxxxxxxxx>
• Re: systems requiring exit?
  • From: Howard Chu <hyc@xxxxxxxxxxxxxxx>
• Re: systems requiring exit?
  • From: "Ilya N. Golubev" <gin@xxxxxxxxx>
• Re: systems requiring exit?
  • From: Thomas Dickey <dickey@xxxxxxx>
• Re: systems requiring exit?
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: systems requiring exit?
  • From: "Ilya N. Golubev" <gin@xxxxxxxxx>
• Re: FW: automake/511: ./config.status in generated makefile conflicts with AM_MAKEFLAGS=-f alternativemakefilename
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: netbsd sed and test 76
  • From: Patrick Welche <prlw1@xxxxxxxxxxxxxx>
• AC_CONFIG_SUBDIR_TARGET?
  • From: Simon Richter <Simon.Richter@xxxxxxxxxx>
• Re: netbsd sed and test 76
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: netbsd sed and test 76
  • From: Patrick Welche <prlw1@xxxxxxxxxxxxxx>
• Re: netbsd sed and test 76
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• netbsd sed and test 76
  • From: Patrick Welche <prlw1@xxxxxxxxxxxxxx>
• Re: AC_DEFINE_UNQUOTED with unresolved shell variables
  • From: Roland Illig <roland.illig@xxxxxx>
• Re: AC_DEFINE_UNQUOTED with unresolved shell variables
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• AC_DEFINE_UNQUOTED with unresolved shell variables
  • From: Roland Illig <roland.illig@xxxxxx>
• Re: Finding dlopen and friends on Tandem NSK/OSS
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• What is an unquoted macro call?
  • From: "Jian Wang" <dearvoid@xxxxxxxxx>
• Re: What is an unquoted macro call?
  • From: Harlan Stenn <stenn@xxxxxxxxxxx>
• Re: What is an unquoted macro call?
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: What is an unquoted macro call?
  • From: "Jian Wang" <dearvoid@xxxxxxxxx>
• Re: What is an unquoted macro call?
  • From: Harlan Stenn <stenn@xxxxxxxxxxx>
• Re: Finding dlopen and friends on Tandem NSK/OSS
  • From: Matthew Woehlke <mw_triad@xxxxxxxxxxxxxxxxxxxxx>
• Re: What is an unquoted macro call?
  • From: "Jian Wang" <dearvoid@xxxxxxxxx>
• Re: autoconf config issue: what does ``|#_!!_#|'' mean?
  • From: Sergei Steshenko <sergstesh@xxxxxxxxx>
• Re: autoconf config issue: what does ``|#_!!_#|'' mean?
  • From: Sergei Steshenko <sergstesh@xxxxxxxxx>
• Re: systems requiring exit?
  • From: Matthew Woehlke <mw_triad@xxxxxxxxxxxxxxxxxxxxx>
• Re: systems requiring exit?
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: systems requiring exit?
  • From: Howard Chu <hyc@xxxxxxxxxxxxxxx>
• Re: systems requiring exit?
  • From: Matthew Woehlke <mw_triad@xxxxxxxxxxxxxxxxxxxxx>
• Finding dlopen and friends on Tandem NSK/OSS
  • From: Matthew Woehlke <mw_triad@xxxxxxxxxxxxxxxxxxxxx>
• Re: systems requiring exit?
  • From: Harlan Stenn <stenn@xxxxxxxxxxx>
• Re: systems requiring exit?
  • From: Howard Chu <hyc@xxxxxxxxxxxxxxx>
• Re: systems requiring exit?
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• systems requiring exit?
  • From: "Ilya N. Golubev" <gin@xxxxxxxxx>
• Re: autoconf config issue: what does ``|#_!!_#|'' mean?
  • From: "Bruce Korb" <bruce.korb@xxxxxxxxx>
• Re: autoconf config issue: what does ``|#_!!_#|'' mean?
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: autoconf config issue: what does ``|#_!!_#|'' mean?
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: Error while running autogen
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: How to specify linker
  • From: Keith MARSHALL <keith.marshall@xxxxxxxxx>
• Re: How to specify linker
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• How to specify linker
  • From: shamju joseph <shamju.joseph@xxxxxxxxx>
• Re: m4_for bug?
  • From: Stepan Kasal <kasal@xxxxxx>
• Re: Error while running autogen
  • From: shamju joseph <shamju.joseph@xxxxxxxxx>
• Re: Error while running autogen
  • From: "Jian Wang" <dearvoid@xxxxxxxxx>
• Error while running autogen
  • From: shamju joseph <shamju.joseph@xxxxxxxxx>
• Re: A doubt
  • From: shamju joseph <shamju.joseph@xxxxxxxxx>
• Re: A doubt
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• A doubt
  • From: shamju joseph <shamju.joseph@xxxxxxxxx>
• Re: autoconf config issue: what does ``|#_!!_#|'' mean?
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: autoconf config issue: what does ``|#_!!_#|'' mean?
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: Portable IPC
  • From: Brian Dessent <brian@xxxxxxxxxxx>
• Portable IPC
  • From: Bill Moseley <moseley@xxxxxxxx>
• Re: how to add a library if it exists
  • From: Eric Blake <ebb9@xxxxxxx>
• Re: autoconf config issue: what does ``|#_!!_#|'' mean?
  • From: Bruce Korb <bkorb@xxxxxxx>
• Re: autoconf config issue: what does ``|#_!!_#|'' mean?
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• autoconf config issue: what does ``|#_!!_#|'' mean?
  • From: Bruce Korb <bkorb@xxxxxxx>
• Re: 2.60 and AC_FUNC_GETGROUPS
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: configure and gcc
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: 2.60 and AC_FUNC_GETGROUPS
  • From: Bill Moseley <moseley@xxxxxxxx>
• Re: 2.60 and AC_FUNC_GETGROUPS
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: 2.60 and AC_FUNC_GETGROUPS
  • From: Andreas Schwab <schwab@xxxxxxx>
• 2.60 and AC_FUNC_GETGROUPS
  • From: Bill Moseley <moseley@xxxxxxxx>
• how to add a library if it exists
  • From: Andrew Makhorin <mao@xxxxxxx>
• how to check and add a library if it exists
  • From: Andrew Makhorin <mao@xxxxxxx>
• configure and gcc
  • From: david@xxxxxxxxxxxxxxxxxxxxx
• Re: adding libraries and header file directories
  • From: mick <mickhowe@xxxxxxxxxxxxxx>
• adding libraries and header file directories
  • From: "Jim Rainville" <jim.rainville@xxxxxxxx>
• Re: m4_for bug?
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: m4_for bug?
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• m4_for bug?
  • From: Eric Blake <ebb9@xxxxxxx>
• Re: pure ansi/iso or posix environments
  • From: "Paul Edwards" <kerravon@xxxxx>
• Re: pure ansi/iso or posix environments
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: pure ansi/iso or posix environments
  • From: "Paul Edwards" <kerravon@xxxxx>
• Re: pure ansi/iso or posix environments
  • From: Harlan Stenn <stenn@xxxxxxxxxxx>
• Re: pure ansi/iso or posix environments
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• pure ansi/iso or posix environments
  • From: "Paul Edwards" <kerravon@xxxxx>
• Re: Bison configuration is incorrect
  • From: "Paulo J. Matos" <pocm@xxxxxxxxxxx>
• Re: How to cross compile?
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• How to cross compile?
  • From: shamju joseph <shamju.joseph@xxxxxxxxx>
• FW: automake/511: ./config.status in generated makefile conflicts with AM_MAKEFLAGS=-f alternativemakefilename
  • From: Claudio Fontana <sick_soul@xxxxxxxx>
• Re: Bug#395466: AM_PATH_CHECK causes "possibly undefined macro" errors
  • From: Josh Triplett <josh@xxxxxxxxxxxxxxx>
• Re: Bug#395466: AM_PATH_CHECK causes "possibly undefined macro" errors
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: Bug#395466: AM_PATH_CHECK causes "possibly undefined macro" errors
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Bug#395466: AM_PATH_CHECK causes "possibly undefined macro" errors
  • From: Josh Triplett <josh@xxxxxxxxxxxxxxx>
• Re: stdint.h on IRIX 6.5
  • From: Thomas Dickey <dickey@xxxxxxx>
• Re: stdint.h on IRIX 6.5
  • From: Eric Blake <ebb9@xxxxxxx>
• Re: stdint.h on IRIX 6.5
  • From: Thomas Dickey <dickey@xxxxxxx>
• Re: stdint.h on IRIX 6.5
  • From: Eric Blake <ebb9@xxxxxxx>
• Re: stdint.h on IRIX 6.5
  • From: Thomas Dickey <dickey@xxxxxxx>
• Re: stdint.h on IRIX 6.5
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• stdint.h on IRIX 6.5
  • From: Olly Betts <olly@xxxxxxxxxx>
• Bison configuration is incorrect
  • From: "Paulo J. Matos" <pocm@xxxxxxxxxxx>
• Autoconf test version 2.60b available
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: build/host libs for cross compiling
  • From: Brian Dessent <brian@xxxxxxxxxxx>
• build/host libs for cross compiling
  • From: Robert Schwebel <r.schwebel@xxxxxxxxxxxxxx>
• Re: preventing defines in config.h
  • From: Stepan Kasal <kasal@xxxxxx>
• Re: preventing defines in config.h
  • From: Eric Blake <ebb9@xxxxxxx>
• preventing defines in config.h
  • From: Andy Howell <AndyHowell@xxxxxxxxxxxxxxxxx>
• Finding external programs relocatably
  • From: nash <nashef@xxxxxxxxx>
• Re: correct check for -rdynamic
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• correct check for -rdynamic
  • From: Dan McMahill <mcmahill@xxxxxxxxxxx>
• Re: ac-archive-macros-2006.0927.tar.bz2
  • From: Peter Simons <simons@xxxxxxx>
• Re: Cross compilation
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: Checking dependency style
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Cross compilation
  • From: "Akim Demaille" <akim.demaille@xxxxxxxxx>
• Checking dependency style
  • From: "Rohit Arul Raj" <rohitarulraj@xxxxxxxxx>
• Re: ac-archive-macros-2006.0927.tar.bz2
  • From: Guido Draheim <guidod-2007-@xxxxxx>
• ac-archive-macros-2006.0927.tar.bz2
  • From: Peter Simons <simons@xxxxxxx>
• GNU Automake 1.10 released
  • From: Alexandre Duret-Lutz <adl@xxxxxxxxxxx>
• Re: unexpected editing of argument to AH_BOTTOM
  • From: Stepan Kasal <kasal@xxxxxx>
• Re: unexpected editing of argument to AH_BOTTOM
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: unexpected editing of argument to AH_BOTTOM
  • From: "John W. Eaton" <jwe@xxxxxxxxxxxxxxxxx>
• Re: unexpected editing of argument to AH_BOTTOM
  • From: Stepan Kasal <kasal@xxxxxx>
• Re: unexpected editing of argument to AH_BOTTOM
  • From: Andreas Schwab <schwab@xxxxxxx>
• Re: unexpected editing of argument to AH_BOTTOM
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• unexpected editing of argument to AH_BOTTOM
  • From: "John W. Eaton" <jwe@xxxxxxxxxxxxxxxxx>
• GCC support for STDC constructs
  • From: "Prabhjeet Singh Grover" <Prabhjeet_Grover@xxxxxxxxxxx>
• Re: GCC support for STDC constructs
  • From: Brian Dessent <brian@xxxxxxxxxxx>
• Re: GCC support for STDC constructs
  • From: Brian Dessent <brian@xxxxxxxxxxx>
• Re: GCC support for STDC constructs
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: GCC support for STDC constructs
  • From: Brian Dessent <brian@xxxxxxxxxxx>
• Re: Inconsistency w.r.t. defining the same symbol more than once
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: Inconsistency w.r.t. defining the same symbol more than once
  • From: Thomas Schwinge <tschwinge@xxxxxxx>
• Re: Inconsistency w.r.t. defining the same symbol more than once
  • From: Thomas Schwinge <tschwinge@xxxxxxx>
• Re: Inconsistency w.r.t. defining the same symbol more than once
  • From: Eric Blake <ebb9@xxxxxxx>
• Re: Inconsistency w.r.t. defining the same symbol more than once
  • From: Thomas Dickey <dickey@xxxxxxx>
• Re: Inconsistency w.r.t. defining the same symbol more than once
  • From: Stepan Kasal <kasal@xxxxxx>
• Re: Inconsistency w.r.t. defining the same symbol more than once
  • From: Thomas Dickey <dickey@xxxxxxx>
• Re: Inconsistency w.r.t. defining the same symbol more than once
  • From: Stepan Kasal <kasal@xxxxxx>
• Re: Inconsistency w.r.t. defining the same symbol more than once
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Inconsistency w.r.t. defining the same symbol more than once
  • From: Thomas Schwinge <tschwinge@xxxxxxx>
• aclocal does not support --include
  • From: Stepan Kasal <kasal@xxxxxx>
• Re: autoreconf not passing -I option to aclocal
  • From: Stepan Kasal <kasal@xxxxxx>
• autoreconf improvement suggestion
  • From: Guillaume Rousse <Guillaume.Rousse@xxxxxxxx>
• Re: autoreconf not passing -I option to aclocal
  • From: Guillaume Rousse <Guillaume.Rousse@xxxxxxxx>
• Re: autoreconf not passing -I option to aclocal
  • From: Guillaume Rousse <Guillaume.Rousse@xxxxxxxx>
• Re: autoreconf not passing -I option to aclocal
  • From: Stepan Kasal <kasal@xxxxxx>
• Re: autoreconf not passing -I option to aclocal
  • From: Keith MARSHALL <keith.marshall@xxxxxxxxx>
• Re: autoreconf not passing -I option to aclocal
  • From: Guillaume Rousse <Guillaume.Rousse@xxxxxxxx>
• Re: autoreconf not passing -I option to aclocal
  • From: Eric Blake <ebb9@xxxxxxx>
• Re: autoreconf not passing -I option to aclocal
  • From: Guillaume Rousse <Guillaume.Rousse@xxxxxxxx>
• Re: autoreconf not passing -I option to aclocal
  • From: Eric Blake <ebb9@xxxxxxx>
• autoreconf not passing -I option to aclocal
  • From: Guillaume Rousse <Guillaume.Rousse@xxxxxxxx>
• Re: defining configure options...
  • From: Eric Blake <ebb9@xxxxxxx>
• defining configure options...
  • From: "Ben Bergen" <ben.bergen@xxxxxxxxx>
• Re: AC_CONFIG_SUBDIRS
  • From: Stepan Kasal <kasal@xxxxxx>
• AC_CONFIG_SUBDIRS
  • From: Sanjaya Ratnaweera <sanjayar@xxxxxxxxx>
• Re: Noobie question
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Noobie question
  • From: Douglas Phillipson <phillipd@xxxxxxxxxxx>
• Re: both native and cross in the same build directory
  • From: Stepan Kasal <kasal@xxxxxx>
• Re: both native and cross in the same build directory
  • From: Eric Blake <ebb9@xxxxxxx>
• both native and cross in the same build directory
  • From: "David Byron" <dbyron@xxxxxxxxx>
• Re: Optimizing ./configure
  • From: "Debarshi 'Rishi' Ray" <debarshi.ray@xxxxxxxxx>
• Re: "./configure --help" doesn't mention LIBS
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: "./configure --help" doesn't mention LIBS
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: Optimizing ./configure
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: making part of package optional at ./configure time
  • From: Stepan Kasal <kasal@xxxxxx>
• Re: making part of package optional at ./configure time
  • From: Keith Marshall <keith.d.marshall@xxxxxxxxxxxx>
• Optimizing ./configure
  • From: "Debarshi 'Rishi' Ray" <debarshi.ray@xxxxxxxxx>
• Re: Question regarding sscanf() vs. off_t and similar
  • From: Paul Eggert <eggert@xxxxxxxxxxx>
• Re: Question regarding sscanf() vs. off_t and similar
  • From: Philipp Marek <philipp@xxxxxxxxxxxxx>
• Re: Question regarding sscanf() vs. off_t and similar
  • From: Stepan Kasal <kasal@xxxxxx>
• Re: making part of package optional at ./configure time
  • From: Stepan Kasal <kasal@xxxxxx>
• Re: making part of package optional at ./configure time
  • From: Keith MARSHALL <keith.marshall@xxxxxxxxx>
• Re: making part of package optional at ./configure time
  • From: mick <mickhowe@xxxxxxxxxxxxxx>
• Re: RFC: rename symbols to m4symbols
  • From: Eric Blake <ebb9@xxxxxxx>
• "./configure --help" doesn't mention LIBS
  • From: Olly Betts <olly@xxxxxxxxxx>
• Re: RFC: rename symbols to m4symbols
  • From: "Gary V. Vaughan" <gary@xxxxxxx>
• RFC: rename symbols to m4symbols
  • From: Eric Blake <ebb9@xxxxxxx>
• Re: how to check linked libarys?
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: making part of package optional at ./configure time
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• making part of package optional at ./configure time
  • From: mick <mickhowe@xxxxxxxxxxxxxx>
• Re: Question regarding sscanf() vs. off_t and similar
  • From: Eric Blake <ebb9@xxxxxxx>
• Re: Question regarding sscanf() vs. off_t and similar
  • From: Ben Pfaff <blp@xxxxxxxxxxxxxxx>
• Re: Newbee : back on trak -> Thank you!
  • From: Karl Schmitt <karl.schmitt@xxxxxxxxxx>
• Re: Question regarding sscanf() vs. off_t and similar
  • From: Philipp Marek <philipp@xxxxxxxxxxxxx>
• Re: Question regarding sscanf() vs. off_t and similar
  • From: Andreas Schwab <schwab@xxxxxxx>
• Re: questions about AC_CONFIG_MACRO_DIR
  • From: Stepan Kasal <kasal@xxxxxx>