On Fri, May 06, 2016 at 06:03:11PM +0100, Andre Przywara wrote: > Hi, > > On 06/05/16 16:09, Tom Rini wrote: > > On Wed, May 04, 2016 at 10:15:28PM +0100, Andre Przywara wrote: > > > > [snip] > >> P.S. tools/buildman/README was TL;DR, so I just tested Pine64 and > >> Bananapi compilation. If someone with a working buildman setup could > >> test this for build regressions, I'd be grateful. > > > > This is good feedback. FWIW, you can just do ./tools/buildman/buildman > > -p /path/to/toolchain-prefix- > > Mmmh, not sure how is this supposed to work in my case, where I simply > have all the toolchains under /usr/bin. > Every kind of parameter to -p I could come up with didn't find any of my > toolchains, though having just: > ============= > [toolchain] > root: / > ============= > in ~/.buildman did the trick and it really found all of my toolchains.
So yes, -p is intended for the case of "just use this one toolchain I know I have" ie -p /usr/bin/arm-none-eabi- and we should better document that you can do: $ cat .buildman.host-tools [toolchain] host = /usr for the case of having many (or, any) system wide cross toolchains. That's my .buildman for using all of the debian system cross compilers. > Letting it build for all architectures now, but so far arm and arm64 > seemed to looked good. Great, thanks! -- Tom
signature.asc
Description: Digital signature
_______________________________________________ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot