automake  

Messages by Date

• 2025/02/18 Re: State and plans for C++20 module support? Paul Smith
• 2025/02/18 Re: State and plans for C++20 module support? Paul Eggert
• 2025/02/18 Re: State and plans for C++20 module support? Zack Weinberg
• 2025/02/09 Re: automake-1.17 fails with latest Perl (5.41.8) - Possible precedence problem between ! and numeric eq (==) Karl Berry
• 2025/02/06 Re: automake-1.17 fails with latest Perl (5.41.8) - Possible precedence problem between ! and numeric eq (==) Jacob Bachmeyer
• 2025/02/06 Re: automake-1.17 fails with latest Perl (5.41.8) - Possible precedence problem between ! and numeric eq (==) Karl Berry
• 2025/02/05 Re: automake-1.17 fails with latest Perl (5.41.8) - Possible precedence problem between ! and numeric eq (==) Jacob Bachmeyer
• 2025/02/05 Re: automake-1.17 fails with latest Perl (5.41.8) - Possible precedence problem between ! and numeric eq (==) Karl Berry
• 2025/02/05 Re: "make dist" bug with "EXTRA_DIST += dirname" and built-in rule for "dirname.c" Karl Berry
• 2025/02/05 Re: "make dist" bug with "EXTRA_DIST += dirname" and built-in rule for "dirname.c" R. Diez
• 2025/02/05 Re: "make dist" bug with "EXTRA_DIST += dirname" and built-in rule for "dirname.c" Karl Berry
• 2025/02/04 Re: automake-1.17 fails with latest Perl (5.41.8) - Possible precedence problem between ! and numeric eq (==) Jacob Bachmeyer
• 2025/02/04 Re: automake-1.17 fails with latest Perl (5.41.8) - Possible precedence problem between ! and numeric eq (==) Karl Berry
• 2025/02/03 Re: version numbers and new features Andrew W. Nosenko
• 2025/02/02 Re: version numbers and new features Jan Engelhardt
• 2025/02/02 Re: version numbers and new features Jim Meyering
• 2025/02/02 version numbers and new features Karl Berry
• 2025/02/01 Re: automake-1.17 fails with latest Perl (5.41.8) - Possible precedence problem between ! and numeric eq (==) Jacob Bachmeyer
• 2025/02/01 Re: automake-1.17 fails with latest Perl (5.41.8) - Possible precedence problem between ! and numeric eq (==) Karl Berry
• 2025/01/31 Re: automake-1.17 fails with latest Perl (5.41.8) - Possible precedence problem between ! and numeric eq (==) Jacob Bachmeyer
• 2025/01/31 Re: automake-1.17 fails with latest Perl (5.41.8) - Possible precedence problem between ! and numeric eq (==) Jacob Bachmeyer
• 2025/01/31 Re: automake-1.17 fails with latest Perl (5.41.8) - Possible precedence problem between ! and numeric eq (==) Zack Weinberg
• 2025/01/31 Re: automake-1.17 fails with latest Perl (5.41.8) - Possible precedence problem between ! and numeric eq (==) Karl Berry
• 2025/01/30 Re: automake-1.17 fails with latest Perl (5.41.8) - Possible precedence problem between ! and numeric eq (==) Jacob Bachmeyer
• 2025/01/30 RE: automake-1.17 fails with latest Perl (5.41.8) - Possible precedence problem between ! and numeric eq (==) Karl Berry
• 2025/01/29 Re: automake-1.17 fails with latest Perl (5.41.8) - Possible precedence problem between ! and numeric eq (==) Collin Funk
• 2025/01/29 RE: automake-1.17 fails with latest Perl (5.41.8) - Possible precedence problem between ! and numeric eq (==) Igor Todorovski
• 2025/01/29 Re: automake-1.17 fails with latest Perl (5.41.8) - Possible precedence problem between ! and numeric eq (==) Igor Todorovski
• 2025/01/29 automake-1.17 fails with latest Perl (5.41.8) - Possible precedence problem between ! and numeric eq (==) Igor Todorovski
• 2024/12/17 Re: aclocal's past and future home (was Re: Best practise for aclocal paths in cross builds) Ross Burton
• 2024/12/17 aclocal's past and future home (was Re: Best practise for aclocal paths in cross builds) Zack Weinberg
• 2024/12/17 Re: Best practise for aclocal paths in cross builds Ross Burton
• 2024/12/17 Re: Best practise for aclocal paths in cross builds Nick Bowler
• 2024/11/25 Re: "make dist" bug with "EXTRA_DIST += dirname" and built-in rule for "dirname.c" Karl Berry
• 2024/11/25 "make dist" bug with "EXTRA_DIST += dirname" and built-in rule for "dirname.c" R. Diez
• 2024/10/21 Re: Do not require ABOUT-NLS in source directory Gavin Smith
• 2024/10/20 Re: Do not require ABOUT-NLS in source directory Karl Berry
• 2024/10/20 Re: Do not require ABOUT-NLS in source directory Bruno Haible via Discussion list for automake
• 2024/10/20 Re: Do not require ABOUT-NLS in source directory Gavin Smith
• 2024/10/20 Re: Do not require ABOUT-NLS in source directory Bruno Haible via Discussion list for automake
• 2024/10/20 Do not require ABOUT-NLS in source directory Gavin Smith
• 2024/10/16 libtool wrapper and haskell executable PICCA Frederic-Emmanuel
• 2024/10/15 Re: "make dist" and conditional build of autotool-enabled subpackage. suzuki toshiya
• 2024/10/15 Re: "make dist" and conditional build of autotool-enabled subpackage. Zack Weinberg
• 2024/10/15 "make dist" and conditional build of autotool-enabled subpackage. suzuki toshiya
• 2024/09/11 Re: Bug Resilience Program of German Sovereign Tech Fund Karl Berry
• 2024/09/11 Re: Bug Resilience Program of German Sovereign Tech Fund Christoph Grüninger
• 2024/07/31 Re: First draft of application to Sovereign Tech Fund Karl Berry
• 2024/07/31 Re: First draft of application to Sovereign Tech Fund Zack Weinberg
• 2024/07/31 Re: First draft of application to Sovereign Tech Fund Detlef Riekenberg
• 2024/07/20 Re: \# within quotes Nick Bowler
• 2024/07/18 Re: \# within quotes Zack Weinberg
• 2024/07/18 Re: \# within quotes Zack Weinberg
• 2024/07/18 Re: \# within quotes Jan Engelhardt
• 2024/07/18 Re: \# within quotes Zack Weinberg
• 2024/07/18 \# within quotes Tijl Coosemans
• 2024/07/14 Re: First draft of application to Sovereign Tech Fund Karl Berry
• 2024/07/14 Re: First draft of application to Sovereign Tech Fund Christoph Grüninger
• 2024/07/11 automake-1.17 released [stable] Jim Meyering
• 2024/07/10 Re: First draft of application to Sovereign Tech Fund Karl Berry
• 2024/07/07 Re: First draft of application to Sovereign Tech Fund Christoph Grüninger
• 2024/07/06 Re: Possible typo in config.sub Shiro Kawai
• 2024/07/06 Re: Possible typo in config.sub Zack Weinberg
• 2024/07/06 Possible typo in config.sub Shiro Kawai
• 2024/07/03 Re: improve display of filesystem timestamp resolution Karl Berry
• 2024/07/03 Re: improve display of whether sleep supports fractional seconds Karl Berry
• 2024/07/03 Re: [platform-testers] automake-1.16.92 released Nick Bowler
• 2024/07/01 improve display of whether sleep supports fractional seconds Bruno Haible
• 2024/07/01 improve display of filesystem timestamp resolution Bruno Haible
• 2024/07/01 Re: [platform-testers] automake-1.16.92 released Zack Weinberg
• 2024/07/01 Re: [platform-testers] automake-1.16.92 released Frederic Berat
• 2024/06/30 Re: [platform-testers] automake-1.16.92 released Karl Berry
• 2024/06/30 Re: bug#71487: automake-1.16.92 released Stefan Kangas
• 2024/06/30 Re: automake-1.16.92 released Dave Hart
• 2024/06/29 Re: automake-1.16.92 released Nick Bowler
• 2024/06/29 Re: automake-1.16.92 released Dave Hart
• 2024/06/29 Re: First draft of application to Sovereign Tech Fund Karl Berry
• 2024/06/29 Re: automake-1.16.92 released Karl Berry
• 2024/06/29 Fwd: Automake 1.16.90 regression mistakenly "not using Libtool" Dave Hart
• 2024/06/29 Re: automake-1.16.92 released Dave Hart
• 2024/06/26 Re: RFC: Add public macros AC_LOG_CMD and AC_LOG_FILE. Zack Weinberg
• 2024/06/26 Re: RFC: Add public macros AC_LOG_CMD and AC_LOG_FILE. Karl Berry
• 2024/06/25 Re: [platform-testers] automake-1.16.92 released Karl Berry
• 2024/06/25 Re: [platform-testers] automake-1.16.92 released Frederic Berat
• 2024/06/24 Re: RFC: Add public macros AC_LOG_CMD and AC_LOG_FILE. Nick Bowler
• 2024/06/24 Re: RFC: Add public macros AC_LOG_CMD and AC_LOG_FILE. Zack Weinberg
• 2024/06/23 Re: RFC: Add public macros AC_LOG_CMD and AC_LOG_FILE. Nick Bowler
• 2024/06/23 RFC: Add public macros AC_LOG_CMD and AC_LOG_FILE. Zack Weinberg
• 2024/06/22 Re: [platform-testers] automake-1.16.92 released Bruno Haible
• 2024/06/22 Re: [platform-testers] automake-1.16.92 released Jim Meyering
• 2024/06/21 Re: [platform-testers] automake-1.16.92 released Bruno Haible
• 2024/06/20 automake-1.16.92 released Jim Meyering
• 2024/06/20 Re: branch master updated: lib scripts: add "(GNU Automake)" to --version output, etc. Karl Berry
• 2024/06/20 Re: branch master updated: lib scripts: add "(GNU Automake)" to --version output, etc. Bruno Haible
• 2024/06/19 Re: 1.16.90 regression: configure now takes 7 seconds to start Karl Berry
• 2024/06/18 Re: 1.16.90 regression: configure now takes 7 seconds to start Jacob Bachmeyer
• 2024/06/18 Re: 1.16.90 regression: configure now takes 7 seconds to start Jacob Bachmeyer
• 2024/06/18 Re: 1.16.90 regression: configure now takes 7 seconds to start Zack Weinberg
• 2024/06/18 Re: 1.16.90 regression: configure now takes 7 seconds to start Bruno Haible
• 2024/06/18 Re: 1.16.90 regression: configure now takes 7 seconds to start Zack Weinberg
• 2024/06/18 Re: Bug Resilience Program of German Sovereign Tech Fund Christoph Grüninger
• 2024/06/17 Re: 1.16.90 regression: configure now takes 7 seconds to start Bruno Haible
• 2024/06/17 Re: 1.16.90 regression: configure now takes 7 seconds to start Jacob Bachmeyer
• 2024/06/17 Re: 1.16.90 regression: configure now takes 7 seconds to start Zack Weinberg
• 2024/06/17 Re: 1.16.90 regression: configure now takes 7 seconds to start Jacob Bachmeyer
• 2024/06/17 Re: 1.16.90 regression: configure now takes 7 seconds to start Bruno Haible
• 2024/06/17 Re: 1.16.90 regression: configure now takes 7 seconds to start Bruno Haible
• 2024/06/17 Re: 1.16.90 regression: configure now takes 7 seconds to start Karl Berry
• 2024/06/17 Re: 1.16.90 regression: configure now takes 7 seconds to start Karl Berry
• 2024/06/17 Re: Bug Resilience Program of German Sovereign Tech Fund Karl Berry
• 2024/06/16 Re: 1.16.90 regression: configure now takes 7 seconds to start Nick Bowler
• 2024/06/16 Re: use of make in AM_SANITY_CHECK Jacob Bachmeyer
• 2024/06/16 Re: 1.16.90 regression: configure now takes 7 seconds to start Jacob Bachmeyer
• 2024/06/16 Re: 1.16.90 regression: configure now takes 7 seconds to start Bruno Haible
• 2024/06/16 Re: 1.16.90 regression: configure now takes 7 seconds to start Bruno Haible
• 2024/06/16 Re: use of make in AM_SANITY_CHECK (was: improved timestamp resolution test) Karl Berry
• 2024/06/16 Re: 1.16.90 regression: configure now takes 7 seconds to start Karl Berry
• 2024/06/15 Re: use of make in AM_SANITY_CHECK (was: improved timestamp resolution test) Jacob Bachmeyer
• 2024/06/15 Re: Bug Resilience Program of German Sovereign Tech Fund Karl Berry
• 2024/06/15 Re: Bug Resilience Program of German Sovereign Tech Fund Christoph Grüninger
• 2024/06/14 Re: End of life dates vs regression test matrix Nick Bowler
• 2024/06/14 Re: End of life dates vs regression test matrix Dan Kegel
• 2024/06/14 Re: End of life dates vs regression test matrix Bob Friesenhahn
• 2024/06/13 Re: End of life dates vs regression test matrix Jacob Bachmeyer
• 2024/06/13 End of life dates vs regression test matrix Dan Kegel
• 2024/06/13 Re: 1.16.90 regression: configure now takes 7 seconds to start Bruno Haible
• 2024/06/13 Re: Bug Resilience Program of German Sovereign Tech Fund Karl Berry
• 2024/06/13 Re: improved timestamp resolution test (was: 1.16.90 regression: configure now takes 7 seconds to start) Karl Berry
• 2024/06/13 Re: 1.16.90 regression: configure now takes 7 seconds to start Karl Berry
• 2024/06/13 Re: 1.16.90 regression: configure now takes 7 seconds to start Bruno Haible
• 2024/06/12 Re: 1.16.90 regression: configure now takes 7 seconds to start Simon Richter
• 2024/06/12 Re: improved timestamp resolution test (was: 1.16.90 regression: configure now takes 7 seconds to start) Jacob Bachmeyer
• 2024/06/12 Re: 1.16.90 regression: configure now takes 7 seconds to start Jacob Bachmeyer
• 2024/06/12 Re: Bug Resilience Program of German Sovereign Tech Fund Jacob Bachmeyer
• 2024/06/12 Re: 1.16.90 regression: configure now takes 7 seconds to start Karl Berry
• 2024/06/12 Re: 1.16.90 regression: configure now takes 7 seconds to start Karl Berry
• 2024/06/12 Re: 1.16.90 regression: configure now takes 7 seconds to start Karl Berry
• 2024/06/12 Re: Bug Resilience Program of German Sovereign Tech Fund Christoph Grüninger
• 2024/06/12 Re: Bug Resilience Program of German Sovereign Tech Fund Christoph Grüninger
• 2024/06/12 Re: 1.16.90 regression: configure now takes 7 seconds to start Zack Weinberg
• 2024/06/11 Re: 1.16.90 regression: configure now takes 7 seconds to start Simon Richter
• 2024/06/11 Re: 1.16.90 regression: configure now takes 7 seconds to start dherring
• 2024/06/11 Re: 1.16.90 regression: configure now takes 7 seconds to start Jacob Bachmeyer
• 2024/06/11 Re: 1.16.90 regression: configure now takes 7 seconds to start Bruno Haible
• 2024/06/11 Re: 1.16.90 regression: configure now takes 7 seconds to start Karl Berry
• 2024/06/11 Re: 1.16.90 regression: configure now takes 7 seconds to start Karl Berry
• 2024/06/11 Re: 1.16.90 regression: configure now takes 7 seconds to start Karl Berry
• 2024/06/11 Re: Bug Resilience Program of German Sovereign Tech Fund Karl Berry
• 2024/06/08 Re: 1.16.90 regression: configure now takes 7 seconds to start Nick Bowler
• 2024/06/07 Re: 1.16.90 regression: configure now takes 7 seconds to start Jacob Bachmeyer
• 2024/06/07 Re: 1.16.90 regression: configure now takes 7 seconds to start Simon Richter
• 2024/06/07 system info in test-suite.log Bruno Haible
• 2024/06/07 Re: 1.16.90 regression: configure now takes 7 seconds to start Bruno Haible
• 2024/06/07 First draft of application to Sovereign Tech Fund Christoph Grüninger
• 2024/06/07 Re: 1.16.90 regression: configure now takes 7 seconds to start Jacob Bachmeyer
• 2024/06/07 no easy way to generate a test-suite.log without skipped tests Bruno Haible
• 2024/06/07 Re: Bug Resilience Program of German Sovereign Tech Fund Paul Eggert
• 2024/06/06 Re: Bug Resilience Program of German Sovereign Tech Fund Christoph Grüninger
• 2024/06/06 Re: Bug Resilience Program of German Sovereign Tech Fund Paul Eggert
• 2024/06/06 Re: Bug Resilience Program of German Sovereign Tech Fund Christoph Grüninger
• 2024/06/06 Re: Bug Resilience Program of German Sovereign Tech Fund Christoph Grüninger
• 2024/06/06 Re: Bug Resilience Program of German Sovereign Tech Fund Paul Eggert
• 2024/06/06 Re: Bug Resilience Program of German Sovereign Tech Fund Zack Weinberg
• 2024/06/06 automake-1.16.90 released Jim Meyering
• 2024/06/06 Re: Bug Resilience Program of German Sovereign Tech Fund Dan Kegel
• 2024/06/06 Bug Resilience Program of German Sovereign Tech Fund Christoph Grüninger
• 2024/06/02 Re: small patch to make a test work with upcoming autoconf Jim Meyering
• 2024/06/02 small patch to make a test work with upcoming autoconf Jim Meyering
• 2024/05/15 Re: automake 1.17 release plan? Will Estes
• 2024/05/14 Re: automake 1.17 release plan? Christoph Grüninger
• 2024/05/14 Re: automake 1.17 release plan? Karl Berry
• 2024/05/14 automake 1.17 release plan? Christoph Grüninger
• 2024/05/13 Re: How to force libtool to use CXX mode? Karl Berry
• 2024/05/13 Re: How to force libtool to use CXX mode? Bob Friesenhahn
• 2024/05/13 Re: How to force libtool to use CXX mode? Karl Berry
• 2024/05/12 How to force libtool to use CXX mode? Bob Friesenhahn
• 2024/04/26 Re: follow-up on backdoor CPU usage (was: libsystemd dependencies) Jacob Bachmeyer
• 2024/04/12 Re: GCC reporting piped input as a security feature Jacob Bachmeyer
• 2024/04/11 Re: GCC reporting piped input as a security feature Zack Weinberg
• 2024/04/09 Re: GCC reporting piped input as a security feature Jacob Bachmeyer
• 2024/04/09 Re: GCC reporting piped input as a security feature Jacob Bachmeyer
• 2024/04/09 Re: GCC reporting piped input as a security feature Alan D. Salewski
• 2024/04/08 Re: GCC reporting piped input as a security feature Jan Engelhardt
• 2024/04/08 Re: GCC reporting piped input as a security feature Jacob Bachmeyer
• 2024/04/08 Re: GNU Coding Standards, automake, and the recent xz-utils backdoor Richard Stallman
• 2024/04/08 Re: GCC reporting piped input as a security feature (was: GNU Coding Standards, automake, and the recent xz-utils backdoor) Richard Stallman
• 2024/04/08 Re: GCC reporting piped input as a security feature (was: GNU Coding Standards, automake, and the recent xz-utils backdoor) Richard Stallman
• 2024/04/07 Re: detecting modified m4 files (was: GNU Coding Standards, automake, and the recent xz-utils backdoor) Jacob Bachmeyer
• 2024/04/05 Re: GCC reporting piped input as a security feature (was: GNU Coding Standards, automake, and the recent xz-utils backdoor) Jacob Bachmeyer
• 2024/04/05 Re: GNU Coding Standards, automake, and the recent xz-utils backdoor Richard Stallman
• 2024/04/05 Re: GNU Coding Standards, automake, and the recent xz-utils backdoor Sam James
• 2024/04/04 Re: GNU Coding Standards, automake, and the recent xz-utils backdoor Bruno Haible
• 2024/04/04 Re: GNU Coding Standards, automake, and the recent xz-utils backdoor Richard Stallman
• 2024/04/04 Re: GNU Coding Standards, automake, and the recent xz-utils backdoor Richard Stallman
• 2024/04/04 Re: GNU Coding Standards, automake, and the recent xz-utils backdoor Richard Stallman
• 2024/04/03 Re: libsystemd dependencies Richard Stallman
• 2024/04/02 Re: GNU Coding Standards, automake, and the recent xz-utils backdoor Alfred M. Szmidt
• 2024/04/02 Re: compressed release distribution formats (was: GNU Coding Standards, automake, and the recent xz-utils backdoor) Jacob Bachmeyer
• 2024/04/02 Re: GNU Coding Standards, automake, and the recent xz-utils backdoor Jacob Bachmeyer
• 2024/04/02 Re: checking aclocal m4 files (was: GNU Coding Standards, automake, and the recent xz-utils backdoor) Jacob Bachmeyer

• Earlier messages