public inbox for cygwin-patches@cygwin.com
 help / color / mirror / Atom feed
From: Jon Turney <jon.turney@dronecode.org.uk>
To: Cygwin Patches <cygwin-patches@cygwin.com>
Subject: Re: [PATCH 0/4] Silence more build rules
Date: Thu, 20 Jan 2022 14:58:14 +0000	[thread overview]
Message-ID: <2ea2f6f7-a057-d2d5-4731-27f1b0f3eb72@dronecode.org.uk> (raw)
In-Reply-To: <41c0e46f-bbd3-6e7a-e433-66fa94f95187@SystematicSw.ab.ca>

On 19/01/2022 19:12, Brian Inglis wrote:
> On 2022-01-19 07:39, Corinna Vinschen wrote:
>> On Jan 19 13:15, Jon Turney wrote:
>>> Jon Turney (4):
>>>    Cygwin: silence most custom build rules
>>>    Cygwin: silence dblatex when building PDFs
>>>    Cygwin: silence xsltproc when writing chunked html
>>>    Cygwin: silence xsltproc when writing manpages
>>>
>>>   winsup/cygwin/Makefile.am | 38 ++++++++++++++++-----------------
>>>   winsup/doc/Makefile.am    | 45 ++++++++++++++++++++++-----------------
>>>   2 files changed, 45 insertions(+), 38 deletions(-)
> 
> Hopefully these are now changed to be the helpful type of build rules 
> that output only "CC foo" when commands work and show the complete 
> command line and diagnostics when commands err?
> 
> Or do we have to now have to rerun with V=1 to see error diagnostics?

This just uses automake's standard way of silencing make [1], so the 
latter is correct. You will need to run 'make V=1' to see the command.

Doing the former with full generality using make seems very challenging. 
Please submit patches to automake for that! :)

[1] 
https://www.gnu.org/software/automake/manual/html_node/Automake-Silent-Rules.html

      reply	other threads:[~2022-01-20 14:58 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-19 13:15 Jon Turney
2022-01-19 13:15 ` [PATCH 1/4] Cygwin: silence most custom " Jon Turney
2022-01-19 13:15 ` [PATCH 2/4] Cygwin: silence dblatex when building PDFs Jon Turney
2022-01-20 16:43   ` Jon Turney
2022-01-20 16:46     ` Corinna Vinschen
2022-01-20 20:02       ` Jon Turney
2022-01-26 15:19         ` Jon Turney
2022-01-19 13:15 ` [PATCH 3/4] Cygwin: silence xsltproc when writing chunked html Jon Turney
2022-01-19 13:15 ` [PATCH 4/4] Cygwin: silence xsltproc when writing manpages Jon Turney
2022-01-19 14:39 ` [PATCH 0/4] Silence more build rules Corinna Vinschen
2022-01-19 19:12   ` Brian Inglis
2022-01-20 14:58     ` Jon Turney [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2ea2f6f7-a057-d2d5-4731-27f1b0f3eb72@dronecode.org.uk \
    --to=jon.turney@dronecode.org.uk \
    --cc=cygwin-patches@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).