From mboxrd@z Thu Jan  1 00:00:00 1970
From: Marek Vasut <marex@denx.de>
Date: Wed, 11 Nov 2015 04:02:08 +0100
Subject: [U-Boot] [PATCH v3 3/3] nios2: add 3c120 and 10m50 devboards
	MAINTAINERS
In-Reply-To: <5642AE0E.6010705@wytron.com.tw>
References: <1447159057-15865-1-git-send-email-thomas@wytron.com.tw>
 <201511110241.15419.marex@denx.de> <5642AE0E.6010705@wytron.com.tw>
Message-ID: <201511110402.08359.marex@denx.de>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de

On Wednesday, November 11, 2015 at 03:55:10 AM, Thomas Chou wrote:
> Hi Marek,
> 
> On 2015?11?11? 09:41, Marek Vasut wrote:
> > I gave up on buildman. I want some builder where I can stop the builds if
> > something goes wrong, but instead of this, buildman spawns multiple
> > processes somewhere on my machine at random and I have no control over
> > that. I'd like to reevaluate buildman eventually, but now I don't have
> > the time or interest to dig in it.
> 
> I'd use "killall python" on another terminal to stop the builder.

I absolutelly don't want to do killall python, it'd bring down much more than
this buildman ;-)

> I setup it in around an hour including download toolchains from kernel.org.
> 
> 1. Create ~/.buildman from the template in buildman/README
> 
> # Buildman settings file
> 
> [toolchain]
> root: /
> rest: /toolchains/*
> eldk: /opt/eldk-4.2
> arm: /opt/linaro/gcc-linaro-arm-linux-gnueabihf-4.8-2013.08_linux
> aarch64: /opt/linaro/gcc-linaro-aarch64-none-elf-4.8-2013.10_linux
> 
> [toolchain-alias]
> x86: i386
> blackfin: bfin
> sh: sh4
> nds32: nds32le
> openrisc: or32
> 
> 2. Fetch the toolchains from kernel.org
> 
> $ for i in aarch64 arm avr32 i386 m68k microblaze mips or32 powerpc sh4
> sparc sparc64
> do
> ./tools/buildman/buildman --fetch-arch $i
> done
> $ mv ~/.buildman-toolchains/*/* /toolchains/
> 
> # arc:
> https://github.com/foss-for-synopsys-dwc-arc-processors/toolchain/releases
> # blackfin: http://sourceforge.net/projects/adi-toolchain/files/
> # nds32: http://osdk.andestech.com/packages/
> # nios2: https://sourcery.mentor.com/GNUToolchain/subscription42545
> # sh: http://sourcery.mentor.com/public/gnu_toolchain/sh-linux-gnu
> 
>   nds32: http://osdk.andestech.com/packages/nds32le-linux-glibc-v1.tgz

OK, so can I use it in some blocking way ?

How do I for example build board "foo" and obtain the result of the build?

Best regards,
Marek Vasut