autoconf  

Messages by Thread

• Checking failing dlopen when building 32bit software alexandre schenberg
  • Re: Checking failing dlopen when building 32bit software Bob Friesenhahn
  • Re: Checking failing dlopen when building 32bit software alexandre schenberg
• Re: automake-1.16.5 released [stable] Kip Warner
• Re: bug#50469: [bison-3.8] bug or side effect to flex & automake Zack Weinberg
• Description not expanded in a call to AC_DEFINE Sébastien Hinderer
  • Re: Description not expanded in a call to AC_DEFINE Nick Bowler
  • Re: Description not expanded in a call to AC_DEFINE Sébastien Hinderer
  • Re: Description not expanded in a call to AC_DEFINE Nick Bowler
  • Re: Description not expanded in a call to AC_DEFINE Sébastien Hinderer
• m4 macro expansion problem Sébastien Hinderer
  • Re: m4 macro expansion problem Nick Bowler
  • Re: m4 macro expansion problem Nick Bowler
  • Re: m4 macro expansion problem Sébastien Hinderer
  • Re: m4 macro expansion problem Sébastien Hinderer
  • Re: m4 macro expansion problem Zack Weinberg
  • Re: m4 macro expansion problem Sébastien Hinderer
  • Re: m4 macro expansion problem Zack Weinberg
  • Re: m4 macro expansion problem Sébastien Hinderer
  • Re: m4 macro expansion problem Peter Johansson
  • Re: m4 macro expansion problem Sébastien Hinderer
  • Re: m4 macro expansion problem Peter Johansson
  • Re: m4 macro expansion problem Sébastien Hinderer
• Possible regression in AC_FC_WRAPPERS Michael Orlitzky
  • Possible regression in AC_FC_WRAPPERS Sam James
• Running autoconf and autoreconf without autotools in the path Christopher O Cowan
  • Re: Running autoconf and autoreconf without autotools in the path Christopher O Cowan
  • Re: Running autoconf and autoreconf without autotools in the path Nick Bowler
• Autoconf online tutorial Anthony Scemama
  • Re: Autoconf online tutorial David A. Wheeler
  • Re: Autoconf online tutorial Anthony Scemama
• AC_CHECK_FUNC vs. function renaming? (curl on tru64/osf1, threads) Jay K
  • Re: AC_CHECK_FUNC vs. function renaming? (curl on tru64/osf1, threads) Paul Eggert
  • Re: AC_CHECK_FUNC vs. function renaming? (curl on tru64/osf1, threads) Jay K
  • Re: AC_CHECK_FUNC vs. function renaming? (curl on tru64/osf1, threads) Paul Eggert
  • Re: AC_CHECK_FUNC vs. function renaming? (curl on tru64/osf1, threads) Jay K
  • Re: AC_CHECK_FUNC vs. function renaming? (curl on tru64/osf1, threads) Paul Eggert
• about variable ac_link and gcc Changqing Li
  • Re: about variable ac_link and gcc Changqing Li
  • about variable ac_link and gcc Changqing Li
  • Re: about variable ac_link and gcc Thomas Jahns
• automake problem with multiple "-rpath" aotto
  • Re: automake problem with multiple "-rpath" aotto
  • Re: automake problem with multiple "-rpath" Thomas Jahns
  • Re: automake problem with multiple "-rpath" aotto
  • Re: automake problem with multiple "-rpath" Thomas Jahns
  • Re: automake problem with multiple "-rpath" aotto
  • Re: automake problem with multiple "-rpath" Bob Friesenhahn
• Force 32 bit build aotto
  • Re: Force 32 bit build Nick Bowler
  • Re: Force 32 bit build Thomas Jahns
  • Re: Force 32 bit build aotto
  • Re: Force 32 bit build Ismael Luceno
  • RE: Force 32 bit build Jannick
• Latest M4 fails M4 checks Jeffrey Walton
  • Re: Latest M4 fails M4 checks Jeffrey Walton
  • Re: Latest M4 fails M4 checks Nick Bowler
  • Re: Latest M4 fails M4 checks Paul Eggert
  • Re: Latest M4 fails M4 checks Jeffrey Walton
  • Re: Latest M4 fails M4 checks Paul Eggert
• How to autoconf figure out what library need to be linked to? Peng Yu
  • Re: How to autoconf figure out what library need to be linked to? Michael Orlitzky
• libtool wrapper Dan Mahoney (Gushi)
  • Re: libtool wrapper Bob Friesenhahn
• How to "bake in" configure args Dan Mahoney (Gushi)
  • Re: How to "bake in" configure args Gavin Smith
  • Re: How to "bake in" configure args Dan Mahoney
  • Re: How to "bake in" configure args Bob Friesenhahn
  • Re: How to "bake in" configure args Richard Purdie
  • Re: How to "bake in" configure args Dan Mahoney (Gushi)
  • Re: How to "bake in" configure args Bob Friesenhahn
• [Knut Petersen] [PATCH] fix broken building of guile branch "branch_release-1-8" Thien-Thi Nguyen
  • Re: [Knut Petersen] [PATCH] fix broken building of guile branch "branch_release-1-8" Thien-Thi Nguyen
• How to check for a #DEFINE? Dan Mahoney
  • Re: How to check for a #DEFINE? Václav Haisman
• How to properly check for -lresolv and resolv.h Dan Mahoney (Gushi)
  • Re: How to properly check for -lresolv and resolv.h Zack Weinberg
  • Re: How to properly check for -lresolv and resolv.h Dan Mahoney
• Issue with AC 2.69 (FreeBSD) and recent changes to make us more compatible with 2.70 Dan Mahoney (Gushi)
• config.sub/config.guess using nonportable $(...) substitutions Nick Bowler
  • Re: config.sub/config.guess using nonportable $(...) substitutions Dmitry V. Levin
  • Re: config.sub/config.guess using nonportable $(...) substitutions Karl Berry
  • Re: config.sub/config.guess using nonportable $(...) substitutions Paul Eggert
  • Re: config.sub/config.guess using nonportable $(...) substitutions Bob Friesenhahn
  • Re: config.sub/config.guess using nonportable $(...) substitutions Paul Eggert
  • Re: config.sub/config.guess using nonportable $(...) substitutions Karl Berry
  • Re: config.sub/config.guess using nonportable $(...) substitutions Paul Eggert
  • Re: config.sub/config.guess using nonportable $(...) substitutions Paul Eggert
  • Re: config.sub/config.guess using nonportable $(...) substitutions Warren Young
  • Re: config.sub/config.guess using nonportable $(...) substitutions Todd C. Miller
  • Re: config.sub/config.guess using nonportable $(...) substitutions Michael Orlitzky
  • Re: config.sub/config.guess using nonportable $(...) substitutions Warren Young
  • Re: config.sub/config.guess using nonportable $(...) substitutions Russ Allbery
  • Re: config.sub/config.guess using nonportable $(...) substitutions Tim Rice
  • Re: config.sub/config.guess using nonportable $(...) substitutions Zack Weinberg
  • Re: config.sub/config.guess using nonportable $(...) substitutions David A. Wheeler
  • Re: config.sub/config.guess using nonportable $(...) substitutions Nick Bowler
  • Re: config.sub/config.guess using nonportable $(...) substitutions Karl Berry
  • Re: config.sub/config.guess using nonportable $(...) substitutions Bob Friesenhahn
  • Re: config.sub/config.guess using nonportable $(...) substitutions Tim Rice
  • Re: config.sub/config.guess using nonportable $(...) substitutions Nick Bowler
• sys/time.h and time.h Thien-Thi Nguyen
  • Re: sys/time.h and time.h Zack Weinberg
  • Re: sys/time.h and time.h Thien-Thi Nguyen
• Version 2.72a fails with libarchive git version Werner LEMBERG
• Weird behaviour about system types Sébastien Hinderer
  • Re: Weird behaviour about system types Zack Weinberg
  • Re: Weird behaviour about system types Zack Weinberg
  • Re: Weird behaviour about system types Sébastien Hinderer
  • Re: Weird behaviour about system types Nick Bowler
  • Re: Weird behaviour about system types Sébastien Hinderer
  • Re: Weird behaviour about system types Nick Bowler
  • Re: Weird behaviour about system types Sébastien Hinderer
  • AC_PROG_CC: how to distinguish clnag from gcc? Sébastien Hinderer
  • Re: AC_PROG_CC: how to distinguish clnag from gcc? Todd C. Miller
  • Re: AC_PROG_CC: how to distinguish clnag from gcc? Sébastien Hinderer
  • Re: AC_PROG_CC: how to distinguish clnag from gcc? David A . Wheeler
  • Re: AC_PROG_CC: how to distinguish clang from gcc? David A. Wheeler
  • Re: AC_PROG_CC: how to distinguish clang from gcc? Russ Allbery
  • Re: AC_PROG_CC: how to distinguish clang from gcc? Sébastien Hinderer
  • Re: AC_PROG_CC: how to distinguish clnag from gcc? Russ Allbery
  • Re: AC_PROG_CC: how to distinguish clnag from gcc? Sébastien Hinderer
  • Re: AC_PROG_CC: how to distinguish clnag from gcc? Russ Allbery
  • Re: AC_PROG_CC: how to distinguish clnag from gcc? Sébastien Hinderer
  • Re: AC_PROG_CC: how to distinguish clnag from gcc? Paul Eggert
• Procedure for adding new target connor horman
  • Re: Procedure for adding new target Paul Eggert
  • Re: Procedure for adding new target connor horman
• version string comparison Thien-Thi Nguyen
  • Re: version string comparison Nick Bowler
  • Re: version string comparison Thien-Thi Nguyen
• RFC: Bump minimum Perl to 5.18.0 for next major release of both Autoconf and Automake Zack Weinberg
  • Re: RFC: Bump minimum Perl to 5.18.0 for next major release of both Autoconf and Automake Paul Eggert
  • Re: RFC: Bump minimum Perl to 5.18.0 for next major release of both Autoconf and Automake Karl Berry
  • Re: RFC: Bump minimum Perl to 5.18.0 for next major release of both Autoconf and Automake Zack Weinberg
  • Re: RFC: Bump minimum Perl to 5.18.0 for next major release of both Autoconf and Automake Zack Weinberg
  • Re: RFC: Bump minimum Perl to 5.18.0 for next major release of both Autoconf and Automake Nick Bowler
  • Re: RFC: Bump minimum Perl to 5.18.0 for next major release of both Autoconf and Automake alexandre schenberg
  • Re: RFC: Bump minimum Perl to 5.18.0 for next major release of both Autoconf and Automake Karl Berry
  • Re: RFC: Bump minimum Perl to 5.18.0 for next major release of both Autoconf and Automake Nick Bowler
• couple notes about post-2.71 branch management Zack Weinberg
  • Re: couple notes about post-2.71 branch management Nick Bowler
  • Re: couple notes about post-2.71 branch management Zack Weinberg
• autoconf-2.71 released [stable] Zack Weinberg
  • Re: autoconf-2.71 released [stable] Eric Blake
• M4 stock macros DUDZIAK Krzysztof
  • Re: M4 stock macros Zack Weinberg
  • RE: M4 stock macros DUDZIAK Krzysztof
• Parallel configure Zack Weinberg
  • Re: Parallel configure Gavin Smith
  • Re: Parallel configure Gavin Smith
  • Re: Parallel configure Paul Eggert
  • Re: Parallel configure Bob Friesenhahn
• Future plans for Autotools Zack Weinberg
  • Re: Future plans for Autotools Dan Kegel
  • Re: Future plans for Autotools Gavin Smith
  • Re: Future plans for Autotools Bob Friesenhahn
  • Re: Future plans for Autotools Andy Tai
  • Re: Future plans for Autotools Dan Kegel
  • Re: Future plans for Autotools Nate Bargmann
  • Re: Future plans for Autotools Kip Warner
  • Re: Future plans for Autotools Nate Bargmann
  • Re: Future plans for Autotools Bob Friesenhahn
  • Re: Future plans for Autotools Zack Weinberg
  • Re: Future plans for Autotools Gavin Smith
  • Re: Future plans for Autotools John Calcote
  • Re: Future plans for Autotools Andy Tai
  • Re: Future plans for Autotools pluto--- via Discussion list for the autoconf build system
  • Re: Future plans for Autotools Paul Eggert
  • Re: Future plans for Autotools Andy Tai
  • Re: Future plans for Autotools Paul Smith
  • Re: Future plans for Autotools Tom Tromey
  • Re: Future plans for Autotools John Calcote
  • Re: Future plans for Autotools Tom Tromey
  • Re: Future plans for Autotools Paul Smith
  • Re: Future plans for Autotools Zack Weinberg
  • Re: Future plans for Autotools Paul Smith
  • Re: Future plans for Autotools Nick Bowler
  • Re: Future plans for Autotools John Calcote
  • Re: Future plans for Autotools Paul Smith
  • Re: Future plans for Autotools Bob Friesenhahn
  • Re: Future plans for Autotools Nick Bowler
  • Re: Future plans for Autotools Paul Smith
  • Re: Future plans for Autotools Bob Friesenhahn
  • Re: Future plans for Autotools David A. Wheeler
  • Re: Future plans for Autotools Paul Eggert
  • Re: Future plans for Autotools Bob Friesenhahn
  • Re: Future plans for Autotools Gavin Smith
  • Re: Future plans for Autotools Gavin Smith
  • Re: Future plans for Autotools Paul Eggert
  • Re: Future plans for Autotools Gavin Smith
  • Re: Future plans for Autotools Gavin Smith
  • Re: Future plans for Autotools Nick Bowler
  • Re: Future plans for Autotools Eli Schwartz
  • Re: Future plans for Autotools Richard Purdie
  • Re: Future plans for Autotools Joseph Myers
  • Re: Future plans for Autotools Richard Purdie
  • Re: Future plans for Autotools Joseph Myers
  • Re: Future plans for Autotools Richard Purdie
  • Re: Future plans for Autotools Karl Berry

• Earlier messages
• Later messages