bcm63xx/u-boot/tools/buildman, branch master

buildman: Deal more nicely with invalid build-status file

2019-05-21T23:33:23Z

The 'done' files created by buildman may end up being empty if buildman runs out of disk space while writing them. At present buildman dies with an exception when using -s to check the build status. Fix this. Seriesl-cc: trini Signed-off-by: Simon Glass

buildman: fix typo

2019-02-09T19:50:22Z

Fix a typo in the error message from CheckOutputDir(). Signed-off-by: Chris Packham Reviewed-by: Simon Glass

buildman: Write the environment out to an 'env' file

2019-02-09T19:50:22Z

Sometimes it is useful to see the environment that was used to build U-Boot. Write this out to a file in the build directory. Signed-off-by: Simon Glass

buildman: Fix tabs in GetWrapper()

2019-01-15T00:47:13Z

This function has tabs instead of spaces. Fix it. Signed-off-by: Simon Glass

buildman: Add support for building with clang

2019-01-15T00:47:13Z

Add a -O option which allows building with clang. Signed-off-by: Simon Glass

buildman: Deal nicely with invalid build-status file

2019-01-15T00:47:13Z

The 'done' files created by buildman may end up being empty if buildman runs out of disk space while writing them. This error is then persistent, since even if disk space is reclaimed and the build retries, the empty file causes an exception in the builder thread. Deal with this silently by doing a rebuild. Signed-off-by: Simon Glass

buildman: Drop comment about Ctrl-C problem

2019-01-15T00:47:13Z

This bug is now fixed, so drop this comment. Signed-off-by: Simon Glass

buildman/toolchain.py: handle inconsistent tarball names

2018-12-05T13:06:30Z

Unfortunately, for some releases the kernel.org toolchain tarball names adhere to the following pattern: -gcc--nolib--.tar.xz e.g.: x86_64-gcc-8.1.0-nolibc-aarch64-linux.tar.xz while others use the following pattern: -gcc--nolib_-.tar.xz e.g.: x86_64-gcc-7.3.0-nolibc_aarch64-linux.tar.xz Notice that the first pattern has dashes throughout, while the second has dashes throughout except just before the target architecture which has an underscore. The "dash throughout" versions from kernel.org are: 8.1.0, 6.4.0, 5.5.0, 4.9.4, 4.8.5, 4.6.1 while the "dash and underscore" versions from kernel.org are: 7.3.0, 4.9.0, 4.8.0, 4.7.3, 4.6.3, 4.6.2, 4.5.1, 4.2.4 This tweak allows the code to handle both versions. Note that this tweak also causes the architecture parsing to get confused and find the following two bogus architectures, "2.0" and "64", which are explicitly checked for, and removed. Signed-off-by: Trevor Woerner Reviewed-by: Simon Glass Change single quotes to double quotes: Signed-off-by: Simon Glass

buildman/toolchain.py: fix toolchain directory

2018-12-05T13:01:35Z

The hexagon toolchain (4.6.1) from kernel.org, for example, was packaged in a way that is different from most toolchains. The first entry when unpacking most toolchain tarballs is: gcc--nolib/- e.g.: gcc-8.1.0-nolibc/aarch64-linux/ The first entry of the hexagon toolchain, however, is: gcc-4.6.1-nolibc/ This causes the buildman logic in toolchain.py::ScanPath() to not be able to find the "*gcc" executable since it looks in gcc-4.6.1-nolib/{.|bin|usr/bin} instead of gcc-4.6.1/hexagon-linux/{.|bin|usr/bin}. Therefore when buildman tries to download a set of toolchains that includes hexagon, the script fails. This update takes the second line of the tarball unpacking (which works for all the toolchains I've tested from kernel.org) and parses it to take the first two elements, separated by '/'. It makes this logic a bit more robust. Signed-off-by: Trevor Woerner Reviewed-by: Simon Glass

buildman: Show boards with warning with w+

2018-11-21T02:14:22Z

At present we should boards with warnings in the same way as those with errors. This is not ideal. Add a new 'warn' state and show these listed in yellow to match the actual warning lines printing with -e. Signed-off-by: Simon Glass