automake  

Messages by Thread

• • Re: Baked-in paths Steffen Dettmer
  • Re: Baked-in paths John Calcote
• appending to BUILT_SOURCES, if appropriate Adam Mercer
  • Re: appending to BUILT_SOURCES, if appropriate Eric Blake
  • Re: appending to BUILT_SOURCES, if appropriate Adam Mercer
• Lex, Yacc, and distcheck Clifford Yapp
  • Re: Lex, Yacc, and distcheck Ralf Wildenhues
• embeding a shared library into another one PICCA Frédéric-Emmanuel
• Sun compiler and /usr/local/include Charles Brown
  • Re: Sun compiler and /usr/local/include Ralf Wildenhues
  • Re: Sun compiler and /usr/local/include Charles Brown
  • Re: Sun compiler and /usr/local/include Ralf Wildenhues
  • Re: Sun compiler and /usr/local/include Dave Hart
  • Re: Sun compiler and /usr/local/include Charles Brown
  • Re: Sun compiler and /usr/local/include NightStrike
  • Re: Sun compiler and /usr/local/include Harlan Stenn
  • Re: Sun compiler and /usr/local/include Dave Hart
  • Re: Sun compiler and /usr/local/include Dave Hart
  • Re: Sun compiler and /usr/local/include Alfred M. Szmidt
  • Re: Sun compiler and /usr/local/include Ralf Wildenhues
  • Re: Sun compiler and /usr/local/include Alfred M. Szmidt
• relinking error Monty Taylor
  • Re: relinking error Monty Taylor
  • Re: relinking error Ralf Wildenhues
• AM_PROG_AS NightStrike
  • Re: AM_PROG_AS Ralf Wildenhues
  • Re: AM_PROG_AS NightStrike
  • Re: AM_PROG_AS Ralf Wildenhues
• Automake and AR NightStrike
  • Re: Automake and AR Ralf Wildenhues
  • Re: Automake and AR NightStrike
  • Re: Automake and AR Ralf Wildenhues
  • Re: Automake and AR NightStrike
  • Re: Automake and AR NightStrike
  • Re: Automake and AR NightStrike
  • Re: Automake and AR NightStrike
  • Re: Automake and AR NightStrike
  • Re: Automake and AR Peter Rosin
  • Re: Automake and AR NightStrike
  • Re: Automake and AR Ralf Wildenhues
  • Re: Automake and AR NightStrike
  • Re: Automake and AR Ralf Corsepius
• unconditional version of EXTRA_DIST Andreas Jellinghaus
  • Re: unconditional version of EXTRA_DIST Ralf Wildenhues
  • Re: unconditional version of EXTRA_DIST Andreas Jellinghaus
  • Re: unconditional version of EXTRA_DIST Ralf Wildenhues
  • Re: unconditional version of EXTRA_DIST Andreas Jellinghaus
  • Re: unconditional version of EXTRA_DIST NightStrike
  • Re: unconditional version of EXTRA_DIST Ralf Wildenhues
• Re: cross-compiling on 64 to 32-bit Linuxlocalhost/ Grégory Pakosz
  • Re: cross-compiling on 64 to 32-bit Linuxlocalhost/ John Calcote
  • Re: cross-compiling on 64 to 32-bit Linuxlocalhost/ Grégory Pakosz
• Multiplatform autotools; all OK on Linux, warning on Windows Joost Kraaijeveld
  • Re: Multiplatform autotools; all OK on Linux, warning on Windows Ralf Wildenhues
• Public header files Jef Driesen
  • Re: Public header files NightStrike
  • Re: Public header files Ralf Wildenhues
  • Re: Public header files Jef Driesen
  • Re: Public header files Ralf Wildenhues
  • Re: Public header files Jef Driesen
  • Re: Public header files Ralf Wildenhues
  • Re: Public header files Jef Driesen
  • Re: Public header files Ralf Wildenhues
  • Re: Public header files Jef Driesen
  • Re: Public header files Peter Johansson
  • Re: Public header files Jef Driesen
  • Re: Public header files Peter Johansson
  • revision control info in generated files (was: Public header files) Ralf Wildenhues
  • Re: revision control info in generated files Jef Driesen
  • Re: revision control info in generated files Ralf Wildenhues
  • Re: revision control info in generated files Jef Driesen
  • Re: revision control info in generated files Ralf Wildenhues
  • Re: revision control info in generated files Jef Driesen
  • Re: revision control info in generated files Ralf Wildenhues
  • Re: revision control info in generated files Jef Driesen
  • Re: revision control info in generated files Peter Johansson
  • Re: revision control info in generated files Jef Driesen
  • Re: revision control info in generated files Peter Johansson
  • Re: revision control info in generated files Jef Driesen
  • Re: revision control info in generated files Peter Johansson
  • Re: revision control info in generated files Jef Driesen
  • Re: revision control info in generated files Steffen Dettmer
  • Re: revision control info in generated files Jef Driesen
  • Re: revision control info in generated files Peter Johansson
  • Re: revision control info in generated files Peter Johansson
  • Re: revision control info in generated files Jef Driesen
  • Re: revision control info in generated files Jef Driesen
  • Re: Public header files Ben Pfaff
  • Re: Public header files John Calcote
  • Re: Public header files John Calcote
  • Re: Public header files Russ Allbery
  • Re: Public header files John Calcote
• distcheck and canonical_* NightStrike
  • Re: distcheck and canonical_* Ralf Wildenhues
  • Re: distcheck and canonical_* NightStrike
  • Re: distcheck and canonical_* Ralf Wildenhues
  • Re: distcheck and canonical_* Steffen Dettmer
  • Re: distcheck and canonical_* Ralf Wildenhues
  • Re: distcheck and canonical_* NightStrike
• detect old Automake Peter Johansson
  • Re: detect old Automake Ralf Wildenhues
  • Re: detect old Automake Peter Johansson
  • Re: detect old Automake Ralf Wildenhues
• cannot specify -o with -c or -S rrlangly
  • Re: cannot specify -o with -c or -S Russ Allbery
  • Re: cannot specify -o with -c or -S Ralf Corsepius
  • Re: cannot specify -o with -c or -S Harlan Stenn
• Automake conditionals in autoconf NightStrike
  • Re: Automake conditionals in autoconf Ralf Wildenhues
  • Re: Automake conditionals in autoconf NightStrike
• create libraries with libtool, but don't install *.la files? Andreas Jellinghaus
  • Re: create libraries with libtool, but don't install *.la files? Peter Johansson
• Proper way to link Fortran with C++ Jö Fahlke
  • Re: Proper way to link Fortran with C++ Ralf Wildenhues
  • Re: Proper way to link Fortran with C++ Steven G. Johnson
  • Re: Proper way to link Fortran with C++ Steven G. Johnson
• Problem of: variable `main_SOURCES' is defined but no program or library has `main' as canonical name (possible typo) 杨觅
  • Re: Problem of: variable `main_SOURCES' is defined but no program or library has `main' as canonical name (possible typo) Ralf Wildenhues
  • Re: Problem of: variable `main_SOURCES' is defined but no program or library has `main' as canonical name (possible typo) 杨觅
  • Re: Problem of: variable `main_SOURCES' is defined but no program or library has `main' as canonical name (possible typo) Ralf Wildenhues
  • Re: Problem of: variable `main_SOURCES' is defined but no program or library has `main' as canonical name (possible typo) 杨觅
  • Re: Problem of: variable `main_SOURCES' is defined but no program or library has `main' as canonical name (possible typo) Steffen Dettmer
• split check target into check and test targets Daily, Jeff A
  • Re: split check target into check and test targets Bob Friesenhahn
  • RE: split check target into check and test targets Daily, Jeff A
  • Re: split check target into check and test targets Ralf Wildenhues
  • RE: split check target into check and test targets Daily, Jeff A
  • Re: split check target into check and test targets Baurzhan Ismagulov
  • Re: split check target into check and test targets John Calcote
  • Re: split check target into check and test targets Ralf Wildenhues
  • Re: split check target into check and test targets Baurzhan Ismagulov
  • parallel-tests use case (was: split check target into check and test targets) Ralf Wildenhues
  • Re: split check target into check and test targets Steffen Dettmer
  • Re: split check target into check and test targets Ralf Wildenhues
  • Re: split check target into check and test targets Daily, Jeff A
• Reported location of test-suite.log Bob Friesenhahn
  • Re: Reported location of test-suite.log Ralf Wildenhues
  • Re: Reported location of test-suite.log Bob Friesenhahn
  • Re: Reported location of test-suite.log Ralf Wildenhues
  • Re: Reported location of test-suite.log Bob Friesenhahn
• cannot create directory `.am2128': Permission denied Bruce Korb
  • Re: cannot create directory `.am2128': Permission denied Ralf Wildenhues
  • Re: cannot create directory `.am2128': Permission denied Dave Hart
• pthread + SUN Compiler spam . me
  • Re: pthread + SUN Compiler Bob Friesenhahn
  • Re: pthread + SUN Compiler Mathias Hoffmann
  • Re: pthread + SUN Compiler Ralf Wildenhues
  • Re: pthread + SUN Compiler spam . me
  • Re: pthread + SUN Compiler Bob Friesenhahn
  • Re: pthread + SUN Compiler Ralf Wildenhues
  • Re: pthread + SUN Compiler Bob Friesenhahn
  • Re: pthread + SUN Compiler Bob Friesenhahn
• Subpackage distclean removed parent package dep files BVK Chaitanya
  • Re: Subpackage distclean removed parent package dep files BVK Chaitanya
  • Re: Subpackage distclean removed parent package dep files Ralf Wildenhues
  • Fwd: Subpackage distclean removed parent package dep files BVK Chaitanya
• Using automake for websites? Tim Landscheidt
  • Re: Using automake for websites? Bob Friesenhahn
  • Re: Using automake for websites? Tim Landscheidt
• advice for pre-generating documentation Andreas Jellinghaus
  • Re: advice for pre-generating documentation Gaetan Nadon
  • Re: advice for pre-generating documentation Andreas Jellinghaus
  • Re: advice for pre-generating documentation Gaetan Nadon
  • Re: advice for pre-generating documentation Peter Johansson
  • Re: advice for pre-generating documentation Steffen Dettmer
  • Re: advice for pre-generating documentation Steffen Dettmer
  • Re: advice for pre-generating documentation Gaetan Nadon
  • Re: advice for pre-generating documentation Stefano Lattarini
  • Re: advice for pre-generating documentation Braden McDaniel
  • Re: advice for pre-generating documentation Stefano Lattarini
  • Re: advice for pre-generating documentation Braden McDaniel
  • Re: advice for pre-generating documentation Ralf Wildenhues
  • Re: advice for pre-generating documentation Stefano Lattarini
• How to handle data/script files in a VPATH build ? Sylvestre Ledru
  • Re: How to handle data/script files in a VPATH build ? Peter Johansson
  • Re: How to handle data/script files in a VPATH build ? Sylvestre Ledru
  • Re: How to handle data/script files in a VPATH build ? Ralf Wildenhues
  • Re: How to handle data/script files in a VPATH build ? Steffen Dettmer
  • Re: How to handle data/script files in a VPATH build ? Ralf Wildenhues
  • Re: How to handle data/script files in a VPATH build ? Sylvestre Ledru
  • Re: How to handle data/script files in a VPATH build ? Ralf Wildenhues
  • Re: How to handle data/script files in a VPATH build ? Steffen Dettmer
  • Re: How to handle data/script files in a VPATH build ? Ralf Wildenhues
  • Re: How to handle data/script files in a VPATH build ? Steffen Dettmer
  • Re: How to handle data/script files in a VPATH build ? Dr. David Kirkby
  • portability testing (was: How to handle data/script files in a VPATH build ?) Ralf Wildenhues
• Creating a partial library Justin Seyster
  • Re: Creating a partial library John Calcote
  • Re: Creating a partial library Steffen Dettmer
  • Re: Creating a partial library John Calcote
  • Re: Creating a partial library Ralf Wildenhues
  • Re: Creating a partial library John Calcote
  • Re: Creating a partial library Andrew W. Nosenko
  • Re: Creating a partial library Bob Friesenhahn
  • Re: Creating a partial library Justin Seyster
  • Re: Creating a partial library Bob Friesenhahn
  • Re: Creating a partial library Justin Seyster
• Installing Perl modules in @INC Youssef Eldakar
  • Re: Installing Perl modules in @INC Ralf Wildenhues
  • Installing Perl modules in @INC Youssef Eldakar

• Earlier messages
• Later messages