All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Cédric Marie" <cedric.marie@openmailbox.org>
To: buildroot@busybox.net
Subject: [Buildroot] CMake and VERBOSE variable
Date: Thu, 18 Jun 2015 10:29:21 +0200	[thread overview]
Message-ID: <0d88f0bd848eeb62c868dc2d5dffe496@openmailbox.org> (raw)
In-Reply-To: <5579E9EF.4070402@mind.be>

Hi,

Le 2015-06-11 22:05, Arnout Vandecappelle a ?crit?:
>  A quick review of a few typical packages (linux, busybox, uClibc, 
> u-boot,
> autotools-baed) only turns up uClibc that has a not-very-well 
> documented use of
> VERBOSE. So perhaps we should just revert Bernhard's patch and 
> completely remove
> VERBOSE.
> 
>  Peter?
> 
>  In fact, the export of quiet Q KBUILD_VERBOSE comes directly from the 
> kernel
> (another commit from Bernhard, log "adjust infrastructure for new 
> kconfig"). But
> of course, in the kernel the build system has complete control over 
> what will be
> called with this stuff in the environment. For us that's a lot more 
> complicated.
> So I think we should get rid of all these exports, and leave it up to 
> individual
> packages to do that. Only V is something that is really generally used 
> I think.


Indeed, all these settings are done the same way in the root Makefile of 
the kernel.
Since KBUILD_VERBOSE doesn't seem to be used anywhere else in Buildroot 
(not even in support/kconfig), I also tend to think that this could be 
removed.

What should we do next?
I'm not familiar enough with all these verbose settings, and also with 
the kernel, to be able to check that we're not breaking anything when 
removing them.
Should I first send a patch that moves the export in the right place 
that you have suggested?
Or wait for a cleaning of all these exports?

Regards,

-- 
C?dric

  reply	other threads:[~2015-06-18  8:29 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-09  7:54 [Buildroot] CMake and VERBOSE variable Cédric Marie
2015-06-10 22:00 ` Arnout Vandecappelle
2015-06-11  7:37   ` Cédric Marie
2015-06-11 20:05     ` Arnout Vandecappelle
2015-06-18  8:29       ` Cédric Marie [this message]
2015-06-21 19:23         ` Arnout Vandecappelle
2015-06-22  9:47           ` Cédric Marie
2015-06-22 10:50             ` Samuel Martin
2015-06-22 11:26               ` Cédric Marie
2015-06-22 11:57                 ` Samuel Martin
2015-06-22 14:22                   ` Cédric Marie
2015-08-20 13:04                     ` Cédric Marie
2015-08-22 23:10                       ` Arnout Vandecappelle
2015-08-30 20:27                         ` Cédric Marie
2015-08-31  7:28                         ` Thomas Petazzoni
2015-08-31 12:35                           ` Cédric Marie
2015-08-31 22:34                             ` Arnout Vandecappelle
2015-09-05 21:18                               ` Cédric Marie

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=0d88f0bd848eeb62c868dc2d5dffe496@openmailbox.org \
    --to=cedric.marie@openmailbox.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.