From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stephen Warren Date: Thu, 7 Jul 2016 12:27:53 -0600 Subject: [U-Boot] [PATCH 00/11] buildman: Make the tool friendlier for first-time users In-Reply-To: <1467580467-19186-1-git-send-email-sjg@chromium.org> References: <1467580467-19186-1-git-send-email-sjg@chromium.org> Message-ID: <577E9F29.20301@wwwdotorg.org> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de On 07/03/2016 03:14 PM, Simon Glass wrote: > This makes a few minor improvements to buildman to make it work more easiler > for first-time users: > > - Improve progress and warning messages when fetching toolchains > - Fix a bug where toolchain paths can be overwritten when fetching > - Note at the top of the help how to get started > > Also this series removes MAKEALL. Since buildman has been around for 3 years > it may be time to do this. If not, we can leave it for now. Sounds great:-) BTW, one problem I've come across with buildman recently is that it re-orders warnings/errors from the compiler. In particular, it seems to separate what it thinks are warning from errors (perhaps stdout/stderr split??) but I'm not sure it always gets it right, and I think elides duplicate lines when doing so. When running buildman repeatedly while doing development, and experiencing a compile error, this makes it extremely difficult to interpret some of the compiler's multi-line messages. Is it possible to have an option that turns off all the output processing, and just shows stderr/out mixed up as they would appear "interactively" when manually invoked from a shell, with no post-processing? Occasionally I have to fall back to a manual "make" invocation due to this.