From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v3 3/3] nios2: add 3c120 and 10m50 devboards MAINTAINERS
Date: Wed, 11 Nov 2015 04:02:08 +0100 [thread overview]
Message-ID: <201511110402.08359.marex@denx.de> (raw)
In-Reply-To: <5642AE0E.6010705@wytron.com.tw>
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
next prev parent reply other threads:[~2015-11-11 3:02 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-10 12:37 [U-Boot] [PATCH 1/2] nios2: rename board nios2-generic to 3c120_devboard Thomas Chou
2015-11-10 12:37 ` [U-Boot] [PATCH 2/2] nios2: add 3c120 and 10m50 devboards MAINTAINERS Thomas Chou
2015-11-10 13:47 ` [U-Boot] [PATCH 1/2] nios2: rename board nios2-generic to 3c120_devboard Marek Vasut
2015-11-10 14:48 ` [U-Boot] [PATCH v2 " Thomas Chou
2015-11-10 14:48 ` [U-Boot] [PATCH v2 2/2] nios2: add 3c120 and 10m50 devboards MAINTAINERS Thomas Chou
2015-11-10 14:52 ` [U-Boot] [PATCH v2 1/2] nios2: rename board nios2-generic to 3c120_devboard Marek Vasut
2015-11-11 0:06 ` [U-Boot] [PATCH v3 1/3] " Thomas Chou
2015-11-11 0:06 ` [U-Boot] [PATCH v3 2/3] nios2: change README.nios2 to use 10m50 as template Thomas Chou
2015-11-11 0:06 ` [U-Boot] [PATCH v3 3/3] nios2: add 3c120 and 10m50 devboards MAINTAINERS Thomas Chou
2015-11-11 0:27 ` Marek Vasut
2015-11-11 1:18 ` Thomas Chou
2015-11-11 1:41 ` Marek Vasut
2015-11-11 2:55 ` Thomas Chou
2015-11-11 3:02 ` Marek Vasut [this message]
2015-11-11 5:06 ` Thomas Chou
2016-01-06 13:43 ` Marek Vasut
2015-11-11 1:48 ` Thomas Chou
2015-11-11 2:27 ` Marek Vasut
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201511110402.08359.marex@denx.de \
--to=marex@denx.de \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox