Re: [Buildroot] uClibc build verbosity control

Vineet Gupta <[email protected]>
Newsgroups gmane.comp.lib.uclibc.general
Message-ID <C2D7FE5348E1B147BCA15975FBA230756659BE0C@IN01WEMBXB.internal.synopsys.com>
On Tuesday 28 April 2015 01:46 AM, Bernhard Reutner-Fischer wrote:

On April 27, 2015 11:21:10 AM GMT+02:00, Waldemar Brodkorb <[email protected]><mailto:[email protected]> wrote:


>Hi Vineet,
>Vineet Gupta wrote,
>


>> Hi,
>>
>> uClibc verbosity control V=xx is different from other mainstream


>projects: namely Busybox and Linux kernel.


>> To print full cmdlines (when debugging obscure toolchain issues) we


>need to pass V=2 whereas kernel/busybox take V=1.


>>
>> Can this be changed (I can provide a patch) assuming this doesn't


>break existing scripts upsetting some people.


>>
>> My issue is specifically when using likes of Buildroot, there's no


>obvious way to get the cmdlines of uClibc and/or other projects (unless
>there's some obvious way I'm missing).


Just add V=2 to make flags used for uclibc?

Still requires manually hacking some Makefile etc, since V=xx is tyoically given at cmdline once for entire build.



>
>Good idea. Send a patch. I am pro.


I found the terse output with just defines rather neat.
If there is consensus that the current V=1 has no benefit then we can drop it in favour of just silent 0 and fully verbose 1.


No, the idea is to keep both V=1 and V=2, but make them like other projects.
e.g. in kernel build, V=2 prints the single liners, while V=1 prints the verbose cmdline,
While in uClibc it's the other way around. Same with Busybox AFAIKR.

Simple patch below addresses that, please consider applying.
---------------------->8-------------------------

From 52a6620ea078d65d058b97b9785c3b3b0c3b0a0b Mon Sep 17 00:00:00 2001
From: Vineet Gupta <[email protected]><mailto:[email protected]>
Date: Tue, 28 Apr 2015 12:02:56 +0530
Subject: [PATCH] buildsys: Change build verbostiy behaviour V=n

Currently V=2 prints the verbose cmdline, anything else (say V=1) prints
the terse single liners. This doesn't match with other projects such as
kernel/busybox.

So change that by making V=1 print the verbose cmdline and others (say
V=2) to print the single liners.

Signed-off-by: Vineet Gupta <[email protected]><mailto:[email protected]>
---
 Makerules | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Makerules b/Makerules
index 3ef756ecbd74..d6f7e2460ffe 100644
--- a/Makerules
+++ b/Makerules
@@ -94,7 +94,7 @@ else
 export MAKE_IS_SILENT := n
 SECHO := @echo
 ifneq ($(V)$(VERBOSE),)
-ifeq ($(V),1)
+ifeq ($(V),2)
 DISP := bri# brief, like pur but with defines
 Q := @
 else
--
1.9.1
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.