From: Laurent Desnogues <laurent.desnogues@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: [PATCH] build system: Further improve quiet mode
Date: Mon, 26 Jan 2009 20:04:38 +0100 [thread overview]
Message-ID: <761ea48b0901261104n6fb53c4ey2eec105a6f92e569@mail.gmail.com> (raw)
In-Reply-To: <497DF491.4010808@codemonkey.ws>
On Mon, Jan 26, 2009 at 6:36 PM, Anthony Liguori <anthony@codemonkey.ws> wrote:
>
> BTW, what do people think of printing CFLAGS? I find it not all that
> exciting but if people like it, I'm happy to go with it.
I'm obviously interested since I asked for it :-) I often play with -O
flag when I check every target still builds and sometimes I forget to
set it back to -O2 while I need to run the thing. Having it dumped
early in the build helps me catch when it's wrong as I always look
at the first compilation lines before switching to something else.
Of course it's just a nice-to-have for me, nothing that matters that
much.
Laurent
next prev parent reply other threads:[~2009-01-26 19:04 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-21 18:13 [Qemu-devel] [6380] Make make output quieter (Avi Kivity) Anthony Liguori
2009-01-24 15:10 ` Stuart Brady
2009-01-25 15:53 ` [Qemu-devel] [PATCH] build system: Further improve quiet mode (was: Re: [6380] Make make output quieter (Avi Kivity)) Jan Kiszka
2009-01-25 15:56 ` Laurent Desnogues
2009-01-25 16:30 ` [Qemu-devel] Re: [PATCH] build system: Further improve quiet mode Jan Kiszka
2009-01-25 16:39 ` Laurent Desnogues
2009-01-26 17:36 ` Anthony Liguori
2009-01-26 18:58 ` Lionel Landwerlin
2009-01-26 18:58 ` Paul Brook
2009-01-26 19:41 ` Anthony Liguori
2009-01-27 9:23 ` Laurent Desnogues
2009-01-27 9:47 ` Jan Kiszka
2009-01-27 9:49 ` Jan Kiszka
2009-01-26 19:04 ` Laurent Desnogues [this message]
2009-01-26 17:08 ` [Qemu-devel] " Anthony Liguori
2009-01-26 18:08 ` [Qemu-devel] " Jan Kiszka
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=761ea48b0901261104n6fb53c4ey2eec105a6f92e569@mail.gmail.com \
--to=laurent.desnogues@gmail.com \
--cc=qemu-devel@nongnu.org \
/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 NNTP newsgroup(s).