automake  

Messages by Thread

• • Re: What happened to test folder instspc.dir ? -- Please ignore, I have worked it out. Kevin Youren
• compile .c files as C++? Jay K
  • Re: compile .c files as C++? Thomas Jahns
• Why doesn't install-strip strip shared libraries sometimes Yuri
  • Re: Why doesn't install-strip strip shared libraries sometimes Mathieu Lirzin
• _SOURCES files in sub-directories lead to make distdir failure netfab
  • Re: _SOURCES files in sub-directories lead to make distdir failure Nick Bowler
  • Re: _SOURCES files in sub-directories lead to make distdir failure netfab
  • Re: _SOURCES files in sub-directories lead to make distdir failure Václav Haisman
  • Re: _SOURCES files in sub-directories lead to make distdir failure netfab
  • Re: _SOURCES files in sub-directories lead to make distdir failure netfab
  • Re: _SOURCES files in sub-directories lead to make distdir failure Bob Friesenhahn
  • Re: _SOURCES files in sub-directories lead to make distdir failure netfab
  • Re: _SOURCES files in sub-directories lead to make distdir failure Bob Friesenhahn
  • Re: _SOURCES files in sub-directories lead to make distdir failure Václav Haisman
  • Re: _SOURCES files in sub-directories lead to make distdir failure netfab
  • Re: _SOURCES files in sub-directories lead to make distdir failure Václav Haisman
  • Re: _SOURCES files in sub-directories lead to make distdir failure netfab
  • Re: _SOURCES files in sub-directories lead to make distdir failure netfab
• Ideas for Summer of Code 2018 Mathieu Lirzin
  • Re: Ideas for Summer of Code 2018 Mathieu Lirzin
• Which component controls automake.info ? Jeffrey Walton
  • Re: Which component controls automake.info ? Václav Haisman
  • Re: Which component controls automake.info ? Mathieu Lirzin
  • Re: Which component controls automake.info ? Jeffrey Walton
  • Re: Which component controls automake.info ? Mathieu Lirzin
  • Re: Which component controls automake.info ? Jeffrey Walton
  • Re: Which component controls automake.info ? Mathieu Lirzin
• [PATCH] "make dist" did not depend on $(BUILT_SOURCES) Jim Meyering
  • Re: [PATCH] "make dist" did not depend on $(BUILT_SOURCES) Mathieu Lirzin
  • Re: [PATCH] "make dist" did not depend on $(BUILT_SOURCES) Jim Meyering
  • Re: [PATCH] "make dist" did not depend on $(BUILT_SOURCES) Nick Bowler
  • Re: [PATCH] "make dist" did not depend on $(BUILT_SOURCES) Jim Meyering
  • Re: [PATCH] "make dist" did not depend on $(BUILT_SOURCES) Nick Bowler
  • Re: [PATCH] "make dist" did not depend on $(BUILT_SOURCES) Jim Meyering
• Target dependent on dynamically generated dependency list Kip Warner
• [PATCH] port elisp-compilation support to emacs-23.1 and newer Jim Meyering
  • Re: [PATCH] port elisp-compilation support to emacs-23.1 and newer Jim Meyering
  • Re: [PATCH] port elisp-compilation support to emacs-23.1 and newer Mathieu Lirzin
  • Re: [PATCH] port elisp-compilation support to emacs-23.1 and newer Jim Meyering
  • Re: [PATCH] port elisp-compilation support to emacs-23.1 and newer Mathieu Lirzin
  • Update HACKING (was: [PATCH] port elisp-compilation support to emacs-23.1 and newer) Mathieu Lirzin
  • Re: Update HACKING (was: [PATCH] port elisp-compilation support to emacs-23.1 and newer) Jim Meyering
  • Re: [PATCH] port elisp-compilation support to emacs-23.1 and newer Glenn Morris
  • Re: [PATCH] port elisp-compilation support to emacs-23.1 and newer Jim Meyering
  • Re: [PATCH] port elisp-compilation support to emacs-23.1 and newer Jim Meyering
  • Re: [PATCH] port elisp-compilation support to emacs-23.1 and newer Jim Meyering
  • Re: [PATCH] port elisp-compilation support to emacs-23.1 and newer Mathieu Lirzin
  • Re: [PATCH] port elisp-compilation support to emacs-23.1 and newer Glenn Morris
  • Re: [PATCH] port elisp-compilation support to emacs-23.1 and newer Jim Meyering
  • Re: [PATCH] port elisp-compilation support to emacs-23.1 and newer Glenn Morris
  • Re: [PATCH] port elisp-compilation support to emacs-23.1 and newer Jim Meyering
  • Re: [PATCH] port elisp-compilation support to emacs-23.1 and newer Glenn Morris
  • Re: [PATCH] port elisp-compilation support to emacs-23.1 and newer Jim Meyering
  • Re: [PATCH] port elisp-compilation support to emacs-23.1 and newer Jim Meyering
• Finding #includes from a yacc .y. Ralph Corderoy
  • Re: Finding #includes from a yacc .y. Ralph Corderoy
  • Re: Finding #includes from a yacc .y. Ralph Corderoy
  • Re: Finding #includes from a yacc .y. Nick Bowler
• warning: TEST_LDFLAGS' is defined but no program or library has 'TEST' as canonical name Thomas Martitz
  • Re: warning: TEST_LDFLAGS' is defined but no program or library has 'TEST' as canonical name Nick Bowler
  • Re: warning: TEST_LDFLAGS' is defined but no program or library has 'TEST' as canonical name Thomas Martitz
• MinGW and "warning: implicit declaration of function _spawnv" Jeffrey Walton
  • Re: MinGW and "warning: implicit declaration of function _spawnv" Jeffrey Walton
  • Re: MinGW and "warning: implicit declaration of function _spawnv" Bob Friesenhahn
  • Re: MinGW and "warning: implicit declaration of function _spawnv" Jeffrey Walton
  • Re: MinGW and "warning: implicit declaration of function _spawnv" Bob Friesenhahn
• Mapfile missing from shared object artifact? Jeffrey Walton
  • Re: Mapfile missing from shared object artifact? Jeffrey Walton
  • Re: Mapfile missing from shared object artifact? Jeffrey Walton
  • Re: Mapfile missing from shared object artifact? Thomas Jahns
  • Re: Mapfile missing from shared object artifact? Jeffrey Walton
• How to set AR and ARFLAGS for Apple platforms? Jeffrey Walton
• How to _not_ install a program built with Automake? Jeffrey Walton
  • Re: How to _not_ install a program built with Automake? Victor Porton
• libcpu_a_CXXFLAGS must be set with '=' before using '+=' Jeffrey Walton
  • Re: libcpu_a_CXXFLAGS must be set with '=' before using '+=' Mathieu Lirzin
• Per-Object Flags for Autotool C++ library? Jeffrey Walton
  • Re: Per-Object Flags for Autotool C++ library? Nick Bowler
  • Re: Per-Object Flags for Autotool C++ library? Mathieu Lirzin
  • Re: Per-Object Flags for Autotool C++ library? Jeffrey Walton
  • Re: Per-Object Flags for Autotool C++ library? Jeffrey Walton
  • Re: Per-Object Flags for Autotool C++ library? Jeffrey Walton
  • Re: Per-Object Flags for Autotool C++ library? Nick Bowler
  • Re: Per-Object Flags for Autotool C++ library? Jeffrey Walton
  • Re: Per-Object Flags for Autotool C++ library? Jeffrey Walton
  • Re: Per-Object Flags for Autotool C++ library? Jeffrey Walton
  • Re: Per-Object Flags for Autotool C++ library? Nick Bowler
  • Re: Per-Object Flags for Autotool C++ library? Jeffrey Walton
  • Re: Per-Object Flags for Autotool C++ library? Nick Bowler
  • Re: Per-Object Flags for Autotool C++ library? Jeffrey Walton
  • github: Release distribution, Was: Re: Per-Object Flags for Autotool C++ library? Mike Mestnik
  • Re: Per-Object Flags for Autotool C++ library? Mathieu Lirzin
• Should Automake still support Java? Mathieu Lirzin
  • Re: Should Automake still support Java? Bob Friesenhahn
  • Re: Should Automake still support Java? Russ Allbery
  • Re: Should Automake still support Java? NightStrike
  • Re: Should Automake still support Java? Mathieu Lirzin
• Like config.h.in but in Ada Victor Porton
  • Re: Like config.h.in but in Ada Mathieu Lirzin
• Dealing with uninstalled data Victor Porton
  • Re: Dealing with uninstalled data Mathieu Lirzin
• TAP colors Daniel Herring
• make check stderr? Mike Mestnik
  • Re: make check stderr? Ralph Corderoy
  • Re: make check stderr? Mike Mestnik
  • List Administrivia. (Was: make check stderr?) Ralph Corderoy
• automake: tap-driver.sh: cleanup and revival. Mike Mestnik
  • Re: automake: tap-driver.sh: cleanup and revival. Bob Friesenhahn
  • Re: automake: tap-driver.sh: cleanup and revival. Warren Young
  • Re: automake: tap-driver.sh: cleanup and revival. Mathieu Lirzin
  • Re: automake: tap-driver.sh: cleanup and revival. Warren Young
  • Re: automake: tap-driver.sh: cleanup and revival. Mathieu Lirzin
  • Re: automake: tap-driver.sh: cleanup and revival. Bob Friesenhahn
  • Re: automake: tap-driver.sh: cleanup and revival. Bob Friesenhahn
  • Re: automake: tap-driver.sh: cleanup and revival. Russ Allbery
  • Re: automake: tap-driver.sh: cleanup and revival. Warren Young
  • Re: automake: tap-driver.sh: cleanup and revival. Bob Friesenhahn
  • Re: automake: tap-driver.sh: cleanup and revival. Warren Young
  • Re: automake: tap-driver.sh: cleanup and revival. Bob Friesenhahn
  • Re: automake: tap-driver.sh: cleanup and revival. Russ Allbery
  • Re: automake: tap-driver.sh: cleanup and revival. Mathieu Lirzin
  • Re: automake: tap-driver.sh: cleanup and revival. Mathieu Lirzin
  • Re: automake: tap-driver.sh: cleanup and revival. Mike Mestnik
• Best practice for recognizing cross-compilation and adjusting Makefile.am Simon Sobisch
  • Re: Best practice for recognizing cross-compilation and adjusting Makefile.am Simon Richter
• Parallel build sometimes resulting in "fatal error: config.h: No such file or directory" Simon Sobisch
  • Re: Parallel build sometimes resulting in "fatal error: config.h: No such file or directory" Nick Bowler
  • Re: Parallel build sometimes resulting in "fatal error: config.h: No such file or directory" Simon Sobisch
• Creating POT file from make Sascha Manns
• No rule to make target 'bzr.mk', needed by 'all-am' Sascha Manns
  • Re: No rule to make target 'bzr.mk', needed by 'all-am' Sascha Manns
  • Re: No rule to make target 'bzr.mk', needed by 'all-am' Nick Bowler
  • Re: No rule to make target 'bzr.mk', needed by 'all-am' Sascha Manns
  • Re: No rule to make target 'bzr.mk', needed by 'all-am' Mathieu Lirzin
• Get the directory of the Makefile Victor Porton
  • Re: Get the directory of the Makefile Mathieu Lirzin
  • Re: Get the directory of the Makefile Victor Porton
• Automake 1.16 Thomas Martitz
  • Re: Automake 1.16 Bob Friesenhahn
  • Re: Automake 1.16 Mathieu Lirzin
  • Re: automake 1.16 Bob Friesenhahn
• Re: Automake Digest, Vol 175, Issue 3 Kip Warner
  • Re: Automake Digest, Vol 175, Issue 3 Nick Bowler
  • Re: Automake Digest, Vol 175, Issue 3 Thomas Jahns
  • Re: Automake Digest, Vol 175, Issue 3 Kip Warner
  • Re: Automake Digest, Vol 175, Issue 3 Václav Haisman
  • Re: Automake Digest, Vol 175, Issue 3 Kip Warner
  • Re: Automake Digest, Vol 175, Issue 3 Kip Warner
• Portable $addprefix Kip Warner
  • Re: Portable $addprefix Nick Bowler
  • Re: Portable $addprefix Kip Warner
  • Re: Portable $addprefix Mathieu Lirzin
  • Re: Portable $addprefix Kip Warner
  • Re: Portable $addprefix Mathieu Lirzin
  • Re: Portable $addprefix Kip Warner
  • Re: Portable $addprefix Quinn Grier
  • Re: Portable $addprefix Kip Warner
  • Re: Portable $addprefix Quinn Grier
  • Re: Portable $addprefix Peter Johansson
  • Re: Portable $addprefix Kip Warner
  • Re: Portable $addprefix Thomas Jahns
• Not installing to hard-coded locations vs polkit's fixed location Mike Fleetwood
  • Re: Not installing to hard-coded locations vs polkit's fixed location Nick Bowler
  • Re: Not installing to hard-coded locations vs polkit's fixed location Mike Fleetwood
• "Commit Solution Changes" affects unrelated projects and branches Anton Shepelev
  • Re: "Commit Solution Changes" affects unrelated projects and branches Mathieu Lirzin
  • Re: "Commit Solution Changes" affects unrelated projects and branches Anton Shepelev
• How to avoid stopping the recursive `check` target? Philippe Proulx
  • Re: How to avoid stopping the recursive `check` target? Mathieu Lirzin
  • Re: How to avoid stopping the recursive `check` target? Philippe Proulx
  • Re: How to avoid stopping the recursive `check` target? Mathieu Lirzin
• Warning - non-POSIX variable name Dharmil Shah
  • Re: Warning - non-POSIX variable name Warren Young
  • Re: Warning - non-POSIX variable name Dharmil Shah
  • Re: Warning - non-POSIX variable name Warren Young
  • Re: Warning - non-POSIX variable name Bob Friesenhahn
  • Re: Warning - non-POSIX variable name Warren Young
  • Re: Warning - non-POSIX variable name Eric Blake
  • Re: Warning - non-POSIX variable name Warren Young
• Integrating flexc++(1) and bisonc++(1) into Makefile.am Kip Warner
  • Re: Integrating flexc++(1) and bisonc++(1) into Makefile.am Nick Bowler
  • Re: Integrating flexc++(1) and bisonc++(1) into Makefile.am Will Estes
  • Re: Integrating flexc++(1) and bisonc++(1) into Makefile.am Kip Warner
  • Re: Integrating flexc++(1) and bisonc++(1) into Makefile.am Kip Warner
  • Fwd: Integrating flexc++(1) and bisonc++(1) into Makefile.am Diab Jerius
  • Re: Fwd: Integrating flexc++(1) and bisonc++(1) into Makefile.am Kip Warner
• Overriding installation path in shared libraries built with automake/libtool during build for testing when DYLD_LIBRARY_PATH cannot be used Diab Jerius
• How to add my own rules? Victor Porton
  • Re: How to add my own rules? Victor Porton
  • Re: How to add my own rules? Bob Friesenhahn
• Creation of compatible build directory hierarchy from source information SF Markus Elfring
• Distcheck and multiple development builds Hans Åberg
• Distcheck: wrong TeX Hans Åberg
  • Re: Distcheck: wrong TeX Gavin Smith
  • Re: Distcheck: wrong TeX Hans Åberg
• Makefile.am and patch orthogonality Anton Shepelev
  • Re: Makefile.am and patch orthogonality Nick Bowler
  • Re: Makefile.am and patch orthogonality Anton Shepelev
• GNU Automake 1.15.1 released Mathieu Lirzin

• Earlier messages
• Later messages