automake  

Messages by Thread

• • Re: How to speed up 'automake' Jim Meyering
  • Re: How to speed up 'automake' Sam James
  • Re: How to speed up 'automake' Karl Berry
  • Re: How to speed up 'automake' Karl Berry
  • Re: How to speed up 'automake' Sam James
  • Re: How to speed up 'automake' Karl Berry
  • Re: How to speed up 'automake' Jim Meyering
  • Re: How to speed up 'automake' Nick Bowler
  • Re: How to speed up 'automake' Jim Meyering
  • Re: How to speed up 'automake' Thomas Jahns
  • Re: How to speed up 'automake' Karl Berry
• Should Autotools integrate with VCS ignore files? Горбешко Богдан
  • Re: Should Autotools integrate with VCS ignore files? Bob Friesenhahn
• Need better release validation documentation/strategy. Bob Friesenhahn
  • Re: Need better release validation documentation/strategy. Carlos O'Donell
  • Re: Need better release validation documentation/strategy. Jim Meyering
  • Re: Need better release validation documentation/strategy. Bob Friesenhahn
  • Re: Need better release validation documentation/strategy. ckeader
  • Re: Need better release validation documentation/strategy. Bob Friesenhahn
• Wrong order of preprocessor and compiler flags Evgeny Grin
  • Re: Wrong order of preprocessor and compiler flags Karl Berry
  • Re: Wrong order of preprocessor and compiler flags Jan Engelhardt
  • Re: Wrong order of preprocessor and compiler flags Bob Friesenhahn
  • Re: Wrong order of preprocessor and compiler flags Alex Ameen
  • Re: Wrong order of preprocessor and compiler flags Evgeny Grin
  • Re: Wrong order of preprocessor and compiler flags Evgeny Grin
• portability of xargs Mike Frysinger
  • Re: portability of xargs Paul Eggert
  • Re: portability of xargs Mike Frysinger
  • Re: portability of xargs Paul Eggert
  • Re: portability of xargs Alex Ameen
  • Re: portability of xargs Bob Friesenhahn
  • Re: portability of xargs Mike Frysinger
  • Re: portability of xargs Roman Neuhauser
  • Re: portability of xargs Daniel Herring
  • Re: portability of xargs Dan Kegel
  • Re: portability of xargs Jacob Bachmeyer
  • Re: portability of xargs Mike Frysinger
  • Re: portability of xargs Dan Kegel
  • Re: portability of xargs Jan Engelhardt
  • Re: portability of xargs Daniel Herring
  • Re: portability of xargs Nick Bowler
  • Re: portability of xargs Bob Friesenhahn
  • Re: portability of xargs Paul Smith
  • Re: portability of xargs Bob Friesenhahn
  • Re: portability of xargs Paul Smith
  • Re: portability of xargs NightStrike
  • type errors, command length limits, and Awk (was: portability of xargs) Jacob Bachmeyer
  • Re: type errors, command length limits, and Awk (was: portability of xargs) Mike Frysinger
  • Re: type errors, command length limits, and Awk (was: portability of xargs) Dan Kegel
  • Re: type errors, command length limits, and Awk Jacob Bachmeyer
• Re: bug#19539: [1.15] AC_CONFIG_AUX_DIR should be called early Zack Weinberg
• community long term x.y release branches Mike Frysinger
  • Re: community long term x.y release branches Karl Berry
• adding a command line option for ACLOCAL_PATH-type search paths Mike Frysinger
  • Re: adding a command line option for ACLOCAL_PATH-type search paths Karl Berry
  • Re: adding a command line option for ACLOCAL_PATH-type search paths Peter Johansson
  • Re: adding a command line option for ACLOCAL_PATH-type search paths Mike Frysinger
  • Re: adding a command line option for ACLOCAL_PATH-type search paths Nick Bowler
• multiple online manual versions Mike Frysinger
  • Re: multiple online manual versions Jim Meyering
  • Re: multiple online manual versions Karl Berry
  • Re: multiple online manual versions Mike Frysinger
  • Re: multiple online manual versions Karl Berry
  • Re: multiple online manual versions Mike Frysinger
  • Re: multiple online manual versions Karl Berry
  • Re: multiple online manual versions Mike Frysinger
  • Re: multiple online manual versions Karl Berry
  • Re: multiple online manual versions Mike Frysinger
  • Re: multiple online manual versions Karl Berry
  • Re: multiple online manual versions Mike Frysinger
  • Re: multiple online manual versions Karl Berry
  • Re: multiple online manual versions Mike Frysinger
  • Re: multiple online manual versions Karl Berry
  • Re: multiple online manual versions Mike Frysinger
• FYI, updated copyrights Jim Meyering
• rm -f # no more args failure? Karl Berry
  • Re: rm -f # no more args failure? Bob Friesenhahn
  • Re: rm -f # no more args failure? Karl Berry
  • Re: rm -f # no more args failure? Bob Friesenhahn
  • Re: rm -f # no more args failure? Mike Frysinger
• Automake for RISC-V Billa Surendra
  • Re: Automake for RISC-V Nick Bowler
  • Re: Automake for RISC-V Billa Surendra
  • Re: Automake for RISC-V Jacob Bachmeyer
  • Re: Automake for RISC-V Bob Friesenhahn
  • Re: Automake for RISC-V Billa Surendra
  • Re: Automake for RISC-V Nick Bowler
  • Re: Automake for RISC-V Billa Surendra
  • Re: Automake for RISC-V Jacob Bachmeyer
  • Re: Automake for RISC-V Billa Surendra
  • Re: Automake for RISC-V Peter Johansson
  • Re: Automake for RISC-V Billa Surendra
  • Re: Automake for RISC-V Bob Friesenhahn
  • Re: Automake for RISC-V Daniel Herring
  • Re: Automake for RISC-V Billa Surendra
• `make dist` fails with current git Zack Weinberg
  • Re: `make dist` fails with current git Bob Friesenhahn
  • Re: `make dist` fails with current git Zack Weinberg
  • Re: `make dist` fails with current git Nick Bowler
  • Re: `make dist` fails with current git Zack Weinberg
  • Re: `make dist` fails with current git Nick Bowler
  • Re: `make dist` fails with current git Zack Weinberg
• Re: [platform-testers] automake-1.16g snapshot Karl Berry
  • Re: [platform-testers] automake-1.16g snapshot Dagobert Michelsen
• generated lex/yacc sources? Karl Berry
  • Re: generated lex/yacc sources? Jan Engelhardt
  • Re: generated lex/yacc sources? Nick Bowler
  • Re: generated lex/yacc sources? Karl Berry
  • Re: generated lex/yacc sources? Jan Engelhardt
• automake-1.16g snapshot Jim Meyering
  • Re: [platform-testers] automake-1.16g snapshot Dagobert Michelsen
  • Re: [platform-testers] automake-1.16g snapshot Jim Meyering
• install-pkglibLTLIBRARIES target is missing dep on install-libLTLIBRARIES Jan Engelhardt
  • [PATCH] automake: add install dep on install-libLTLIBRARIES to all targets Jan Engelhardt
  • [PATCH v2] automake: add install dep on install-libLTLIBRARIES to all targets Jan Engelhardt
  • Re: [PATCH v2] automake: add install dep on install-libLTLIBRARIES to all targets Karl Berry
  • Re: [PATCH v2] automake: add install dep on install-libLTLIBRARIES to all targets Jan Engelhardt
  • Re: [PATCH v2] automake: add install dep on install-libLTLIBRARIES to all targets Karl Berry
• Project "calf-studio" fails with Warning: Linking the executable calfmakerdf against the loadable module Yuri
  • Re: Project "calf-studio" fails with Warning: Linking the executable calfmakerdf against the loadable module Bob Friesenhahn
• automake 1.16.4 and new PYTHON_PREFIX Víctor López
  • RE: automake 1.16.4 and new PYTHON_PREFIX FOURNIER Yvan via Discussion list for automake
  • RE: automake 1.16.4 and new PYTHON_PREFIX Karl Berry
  • Re: automake 1.16.4 and new PYTHON_PREFIX Joshua Root
  • Re: automake 1.16.4 and new PYTHON_PREFIX FOURNIER Yvan via Discussion list for automake
  • Re: automake 1.16.4 and new PYTHON_PREFIX Karl Berry
  • Re: automake 1.16.4 and new PYTHON_PREFIX Luke Mewburn
  • Re: automake 1.16.4 and new PYTHON_PREFIX Karl Berry
  • Re: automake 1.16.4 and new PYTHON_PREFIX Karl Berry
  • Re: automake 1.16.4 and new PYTHON_PREFIX Karl Berry
• installing documentation one level higher Werner LEMBERG
  • Re: installing documentation one level higher Peter Johansson
  • Re: installing documentation one level higher Werner LEMBERG
  • Re: installing documentation one level higher Peter Johansson
  • Re: installing documentation one level higher Werner LEMBERG
  • Re: installing documentation one level higher Peter Johansson
• automake-1.16d snapshot Jim Meyering
  • Re: automake-1.16d snapshot Jim Meyering
• ninja-style feature for make Andy Tai
• Automake testsuite misuses DejaGnu Jacob Bachmeyer
  • Re: Automake testsuite misuses DejaGnu Jim Meyering
  • Re: Automake testsuite misuses DejaGnu Jacob Bachmeyer
  • Re: Automake testsuite misuses DejaGnu [PATCH v0] Jacob Bachmeyer
  • Re: Automake testsuite misuses DejaGnu Karl Berry
  • Re: Automake testsuite misuses DejaGnu Jacob Bachmeyer
  • Re: Automake testsuite misuses DejaGnu Daniel Herring
  • Re: Automake testsuite misuses DejaGnu Jacob Bachmeyer
• snapshot imminent Jim Meyering
• How to prevent distribution of `texinfo.tex` Werner LEMBERG
  • Re: How to prevent distribution of `texinfo.tex` Nick Bowler
  • Re: How to prevent distribution of `texinfo.tex` Werner LEMBERG
  • Re: How to prevent distribution of `texinfo.tex` Peter Johansson
  • Re: How to prevent distribution of `texinfo.tex` Nick Bowler
  • Re: How to prevent distribution of `texinfo.tex` Werner LEMBERG
  • Re: How to prevent distribution of `texinfo.tex` Nick Bowler
  • Re: How to prevent distribution of `texinfo.tex` Werner LEMBERG
  • Re: How to prevent distribution of `texinfo.tex` Karl Berry
  • Re: How to prevent distribution of `texinfo.tex` Gavin Smith
  • Re: How to prevent distribution of `texinfo.tex` Karl Berry
• parallel build issues Werner LEMBERG
  • Re: parallel build issues Warren Young
  • Re: parallel build issues Werner LEMBERG
  • Re: parallel build issues Nick Bowler
  • Re: parallel build issues Nick Bowler
  • Re: parallel build issues Werner LEMBERG
  • Re: parallel build issues Werner LEMBERG
  • Re: parallel build issues Nick Bowler
  • Re: parallel build issues Werner LEMBERG
  • Re: parallel build issues Bob Friesenhahn
  • Re: parallel build issues Jacob Bachmeyer
• Behaviour when using both "--dry-run" and "--always-make" together Johan Persson
  • Re: Behaviour when using both "--dry-run" and "--always-make" together Karl Berry
  • Re: Behaviour when using both "--dry-run" and "--always-make" together Johan Persson
  • Re: Behaviour when using both "--dry-run" and "--always-make" together Karl Berry
• RE: Automake Digest, Vol 216, Issue 1 FOURNIER Yvan
• Constantly changing libtool Laurence Marks
  • Re: Constantly changing libtool Karl Berry
  • Re: Constantly changing libtool Bob Friesenhahn
  • Re: Constantly changing libtool Laurence Marks
  • Re: Constantly changing libtool Bob Friesenhahn
  • Re: Constantly changing libtool Laurence Marks
  • Re: Constantly changing libtool Bob Friesenhahn
  • Re: Constantly changing libtool Paul Smith
  • Re: Constantly changing libtool Warren Young
  • Re: Constantly changing libtool Peter Johansson
  • Re: Constantly changing libtool Laurence Marks
  • Re: Constantly changing libtool Thomas Jahns
• How to autotools figure what library need to be linked to? Peng Yu
  • Re: ***UNCHECKED*** How to autotools figure what library need to be linked to? Simon Richter
  • Re: How to autotools figure what library need to be linked to? Bob Friesenhahn
  • Re: How to autotools figure what library need to be linked to? Peng Yu
  • Re: How to autotools figure what library need to be linked to? Bob Friesenhahn
• automake bug fixers/developers needed Karl Berry
• 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

• Earlier messages
• Later messages