-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?
>
>
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 rev
* 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 `-
On Tue, 14 Apr 2009, Eric Blake wrote:
If so, is it worth trying to trim the AC_ARG_ENABLE output to only mention
the non-default case? That is:
AM_SILENT_RULES=> outputs 2 lines for --{en,dis}able-silent-rules
AM_SILENT_RULES([yes]) => outputs 1 line for --disable-silent-rules
AM_SILE
-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
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
AM_INIT_AUTOMAKE => 0,
AM_MAINTAINER_MODE => 0,
AM_PROG_CC_C_O => 0,
+ AM_SILENT_RULES => 0,
_AM_SUBST_NOTMAKE => 1,
_AM_COND_IF => 1,
_AM_COND_ELSE => 1,
@@ -5405,6 +5405,10 @@ s
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) T
* 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.
>>
>>
* 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 a
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 only means of setting the package's default,
>if it cannot be overr
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 w
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
[dropping m4-discuss]
According to Bob Friesenhahn on 4/1/2009 1:32 PM:
>> As I wrote off-list already, unless you use the 'silent-rules' option
>> for your packages, your code should be built as always.
>
> This new m4 release is the first package I
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 *developer* (Makefile.am author) chooses so.
I take it you sugges
* 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 *developer* (Makefile.am author) chooses so.
I take it you suggest that it default to on only if *both* th
Hello John,
can we try *not* to add more mailing lists, and limit on-topic replies
to the libtool lists? For others, please just start a new thread on the
list that seems the most appropriate; thanks!
* John Calcote wrote on Wed, Apr 01, 2009 at 10:08:33PM CEST:
>
> Is there any command-line opt
While we're on the issue of Automake silent rules, I've got a comment
about Libtool hiding half of it's compiles.(Thus, I've added the libtool
list as well.)
I was recently building a project that failed without an error message,
while running under "non-silent" mode, or the original GNU 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 l
* 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
19 matches
Mail list logo
