From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] Silencing the build
Date: Mon, 21 Jul 2014 19:16:27 +0200 [thread overview]
Message-ID: <20140721171627.GB3874@free.fr> (raw)
In-Reply-To: <CAHkwnC-vKfLhiFF2cYcwrLHFJA0ojCL+X2okeSqODsg_gQw3fQ@mail.gmail.com>
Fabio, All,
On 2014-07-21 18:25 +0200, Fabio Porcedda spake thusly:
> On Fri, Jul 18, 2014 at 10:15 PM, Yann E. MORIN <yann.morin.1998@free.fr> wrote:
> > Well, I still believe the build should be verbose by default, otherwise
> > we would miss a lot of important information on bug reports. The problem
> > is where to store the build.log in case of a silent build, so the user
> > can provide it.
>
> I don't know a way to store the full log (stdout & stderr) and view a
> filtered version of stdout & the unfiltered stderr, maybe you have an
> idea?
brmake() {
# This is a bash function, pipefail is not POSIX
set -o pipefail
make "${@}" 2>&1 \
|tee build.log \
|sed -r -e '/^.{4}>>>[[:space:]]+(.*).{5}$/!d; s//\1/;'
}
> > I think the best we can do is document a simple solution (like my little
> > function above, for example).
>
> Yes, i think it's a good idea.
>
> I personally prefer using a line like this:
> make | grep --color=never ">>> "
> to be able to distinguish more easily stdoud messages from stderr messages.
Yes, why not. That's a bit trickier to handle, but no undoable. It would
need playing tricks with redirection and duplicating filedescriptors...
> Nevertheless, I still would like that this patch will be applied because:
> - using "make -s" is still simpler that using some "make | sed
> ........", many tools have a quiet flag for this reason.
> - is a work already done.
> - does not change the usual behavior.
> - it's just adds 12 line of code .
I'll have another look at it...
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2014-07-21 17:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-09 11:46 [Buildroot] [PATCH 1/2] apply-patches.sh: don't print anything when "-s" option is used Fabio Porcedda
2014-07-09 11:46 ` [Buildroot] [PATCH 2/2] package/Makefile.in: fix coding style regarding the '=' sign Fabio Porcedda
2014-07-15 19:28 ` [Buildroot] [PATCH 1/2] apply-patches.sh: don't print anything when "-s" option is used Thomas Petazzoni
2014-07-17 17:40 ` Fabio Porcedda
2014-07-17 18:31 ` [Buildroot] Silencing the build Thomas Petazzoni
2014-07-17 20:29 ` Yann E. MORIN
2014-07-18 8:18 ` Fabio Porcedda
2014-07-18 20:15 ` Yann E. MORIN
2014-07-21 16:25 ` Fabio Porcedda
2014-07-21 17:16 ` Yann E. MORIN [this message]
2014-07-21 17:26 ` [Buildroot] [PATCH 1/2] apply-patches.sh: don't print anything when "-s" option is used Yann E. MORIN
2014-07-25 16:42 ` Fabio Porcedda
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=20140721171627.GB3874@free.fr \
--to=yann.morin.1998@free.fr \
--cc=buildroot@busybox.net \
/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