Re: uClibc build verbosity control
Bernhard Reutner-Fischer <[email protected]>
| Newsgroups | gmane.comp.lib.uclibc.buildroot,gmane.comp.lib.uclibc.general |
|---|---|
| Message-ID | <[email protected]> |
On April 27, 2015 11:21:10 AM GMT+02:00, Waldemar Brodkorb <wbx-bm4kxRPcj/[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? > >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.