On Sun, Dec 12, 2021 at 7:14 AM Zack Weinberg wrote:
>
> On Sun, Dec 12, 2021, at 1:10 AM, Mike Frysinger wrote:
> > On 07 Dec 2021 21:58, Zack Weinberg wrote:
> >> On Tue, Dec 7, 2021, at 9:49 PM, Mike Frysinger wrote:
> >> > This has been available since automake 1.11 released over a decade
>
On Sun, Dec 12, 2021, at 1:10 AM, Mike Frysinger wrote:
> On 07 Dec 2021 21:58, Zack Weinberg wrote:
>> On Tue, Dec 7, 2021, at 9:49 PM, Mike Frysinger wrote:
>> > This has been available since automake 1.11 released over a decade
>> > ago. Let's flip the default to enable silent builds by
On 07 Dec 2021 21:58, Zack Weinberg wrote:
> On Tue, Dec 7, 2021, at 9:49 PM, Mike Frysinger wrote:
> > This has been available since automake 1.11 released over a decade
> > ago. Let's flip the default to enable silent builds by default.
>
> Please don't *ever* make this change. It is
This has been available since automake 1.11 released over a decade
ago. Let's flip the default to enable silent builds by default.
NB: The "1.20" version is a placeholder. With the warning for devs
in 1.17, we can wait a while before rolling this out.
---
NEWS | 9 +
On 08 Dec 2021 15:02, Karl Berry wrote:
> Please don't *ever* make this change.
>
> I agree with Zack, and just for CI purposes; it is simply too big of an
> incompatibility to inflict at this late date.
there's nothing incompatible about it. the inputs to the system (how
configure & make
Please don't *ever* make this change.
I agree with Zack, and just for CI purposes; it is simply too big of an
incompatibility to inflict at this late date.
Mike, thanks for the suggestion, but let's skip this one. --karl
P.S. Personally, I am no fan of silent builds. I find that inevitably
On Tue, Dec 7, 2021, at 9:49 PM, Mike Frysinger wrote:
> This has been available since automake 1.11 released over a decade
> ago. Let's flip the default to enable silent builds by default.
Please don't *ever* make this change. It is absolutely essential that the
default build output be
This has been available since automake 1.11 released over a decade
ago. Let's flip the default to enable silent builds by default.
---
NEWS | 9 +
m4/silent.m4 | 2 +-
2 files changed, 10 insertions(+), 1 deletion(-)
diff --git a/NEWS b/NEWS
index fb05ee219708..866ace951fd5
--include-deps enable dependency tracking code
-Verbosity of generated rules:
- --silent-rules enable silent build rules
-
Flavors:
--cygnus assume program is part of Cygnus-style tree
--foreign set strictness to foreign
@@ -8272,8 +8273,6 @@ sub
On Tuesday 2009-04-14 08:09, Ralf Wildenhues wrote:
Here's why:
[...]
Yet another way out: remove per-Makefile.am `AUTOMAKE_OPTIONS =
silent-rules' as well as `automake --silent-rules' so that the only way
to specify them is as option listed in AM_INIT_AUTOMAKE. This may be
inconvenient for
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Ralf Wildenhues on 4/14/2009 12:09 AM:
Hello Bob, Eric, all,
Hello Ralf,
This is an approach that I am happy with. I would not want to deny
anyone access to silent rules if they want it (and I will am likely use
it for my own
* Ralf Wildenhues wrote on Tue, Apr 14, 2009 at 08:09:12AM CEST:
silent-rules reorganization, --enable-silent-rules switch.
[...]
* automake.in (define_verbose_var): Define the default verbose
variable in terms of `$(AM_DEFAULT_VERBOSITY)'.
(handle_configure): Do not pass
Hi Eric, Bob,
* Eric Blake wrote on Tue, Apr 14, 2009 at 02:12:55PM CEST:
According to Ralf Wildenhues on 4/14/2009 12:09 AM:
This patch introduces such an --enable-silent-rules switch.
[...]
Looks like you got what we wanted! Thanks for doing this. The patch
seemed fine by my review,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Ralf Wildenhues on 4/14/2009 2:32 PM:
Hi Eric, Bob,
Hello to you as well,
+Enable the machinery for less verbose build output (@pxref{Options}).
Are you going to document the (optional) argument that specifies the default?
I
* Jan Engelhardt wrote on Thu, Apr 02, 2009 at 09:53:21AM CEST:
On Thursday 2009-04-02 04:01, Eric Blake wrote:
One of Ralf's concerns is that you can't do AC_SUBST([V], [1]), because it
interacts badly with various make implementations. That is, the Makefile
must not pre-define V as the
* Bob Friesenhahn wrote on Wed, Apr 01, 2009 at 11:04:14PM CEST:
On Wed, 1 Apr 2009, Ralf Wildenhues wrote:
* Bob Friesenhahn wrote on Wed, Apr 01, 2009 at 09:32:54PM CEST:
My opinion is that if this mode is optional that it should default to
off
It defaults to off.
It is enabled if the
On Fri, 3 Apr 2009, Ralf Wildenhues wrote:
A)
1) The developer can choose to enable the silent-rules option in
configure.ac (as argument to AM_INIT_AUTOMAKE) or Makefile.am (adding
the option to the AUTOMAKE_OPTIONS variable). Without this option,
there will never be less verbose output.
2)
* Eric Blake wrote on Wed, Apr 01, 2009 at 08:52:36PM CEST:
According to Bob Friesenhahn on 4/1/2009 12:40 PM:
It seems that I will need to permanently define and export the arbitrary
variable 'V' in my shell environment in order to avoid confusion later
since I won't know how a build
On Wed, 1 Apr 2009, Ralf Wildenhues wrote:
* Eric Blake wrote on Wed, Apr 01, 2009 at 08:52:36PM CEST:
According to Bob Friesenhahn on 4/1/2009 12:40 PM:
It seems that I will need to permanently define and export the arbitrary
variable 'V' in my shell environment in order to avoid confusion
On Wed, 1 Apr 2009, Eric Blake wrote:
What's to say that the only reason the default was so verbose was because
nobody had a better option? I personally like the quieter builds, because
it makes warnings much easier to identify and eliminate.
Yes, of course. But identifying and eliminating
...@medozas.de
Ralf Wildenhues ralf.wildenh...@gmx.de
Implement `silent' build rules.
* automake.in (ccer): New field in the language structure.
Initialize it for all registered languages.
(verbose_var, verbose_flag, verbose_dispatch)
(silent_flag
21 matches
Mail list logo
