On 04/23/2015 08:30 PM, Simon Glass wrote: > Hi, > > On 23 April 2015 at 12:23, Simon Glass <s...@chromium.org> wrote: >> On 20 April 2015 at 03:46, Michal Simek <michal.si...@xilinx.com> wrote: >>> Also read gcc 4.9.0 at kernel.org which also have Microblaze toolchain. >>> >>> Signed-off-by: Michal Simek <michal.si...@xilinx.com> >>> --- >>> >>> tools/buildman/README | 2 +- >>> tools/buildman/toolchain.py | 2 +- >>> 2 files changed, 2 insertions(+), 2 deletions(-) >> >> Acked-by: Simon Glass <s...@chromium.org> >> Tested-by: Simon Glass <s...@chromium.org> > > However it does cause a test failure. > > ./tools/buildman/buildman -t > Checking: https://www.kernel.org/pub/tools/crosstool/files/bin/x86_64/4.9.0/ > <unittest.result.TestResult run=34 errors=0 failures=1> > Traceback (most recent call last): > File > "/usr/local/google/c/cosarm/src/third_party/u-boot/files/tools/buildman/test.py", > line 415, in testToolchainDownload > self.toolchains.LocateArchUrl('arm')) > AssertionError: > 'https://www.kernel.org/pub/tools/crosstool/files/bin/x86_64/4.6.3/x86_64-gcc-4.6.3-nolibc_arm-unknown-linux-gnueabi.tar.xz' > != > 'https://www.kernel.org/pub/tools/crosstool/files/bin/x86_64/4.9.0/x86_64-gcc-4.9.0-nolibc_arm-unknown-linux-gnueabi.tar.xz' > > I'll fix that up when applying.
Thanks. I was curious why you didn't add 4.9.0 there but maybe this was the reason. Thanks for fixing it. Michal _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
