From: Heiko Schocher <hs@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/6] travis-ci: Use = not : when writing ~/.buildman
Date: Thu, 27 Oct 2016 06:20:41 +0200 [thread overview]
Message-ID: <58118099.3090001@denx.de> (raw)
In-Reply-To: <20161026170536.2367-1-swarren@wwwdotorg.org>
Hello Stephen,
Am 26.10.2016 um 19:05 schrieb Stephen Warren:
> From: Stephen Warren <swarren@nvidia.com>
>
> Travis CI seems to be confused when there's a colon in an echo command,
> and this is currently worked around using a variable that contains the
> text we want to echo. Use = syntax instead so that we can remove the
> work-around; it's rather confusing until you find out what it's for.
>
> Signed-off-by: Stephen Warren <swarren@nvidia.com>
> ---
> .travis.yml | 6 ++----
> 1 file changed, 2 insertions(+), 4 deletions(-)
Thanks!
Reviewed-by: Heiko Schocher <hs@denx.de>
bye,
Heiko
>
> diff --git a/.travis.yml b/.travis.yml
> index 00be5ff20396..f91e1bc271fe 100644
> --- a/.travis.yml
> +++ b/.travis.yml
> @@ -38,8 +38,7 @@ install:
> - ln -s travis-ci /tmp/uboot-test-hooks/bin/`hostname`
> - ln -s travis-ci /tmp/uboot-test-hooks/py/`hostname`
> # prepare buildman environment
> - - export BUILDMAN_ROOT="root:"
> - - echo -e "[toolchain]\n${BUILDMAN_ROOT} /usr" > ~/.buildman
> + - echo -e "[toolchain]\nroot = /usr" > ~/.buildman
> - echo -e "\n[toolchain-alias]\nblackfin = bfin\nsh = sh4\nopenrisc = or32" >> ~/.buildman
> - cat ~/.buildman
> - virtualenv /tmp/venv
> @@ -105,8 +104,7 @@ matrix:
> - BUILDMAN="sandbox x86"
> TOOLCHAIN="x86_64"
> script:
> - - export BUILDMAN_X86="x86:";
> - echo -e "\n[toolchain-prefix]\n${BUILDMAN_X86} ${HOME}/.buildman-toolchains/gcc-4.9.0-nolibc/x86_64-linux/bin/x86_64-linux-" >> ~/.buildman
> + - echo -e "\n[toolchain-prefix]\nx86 = ${HOME}/.buildman-toolchains/gcc-4.9.0-nolibc/x86_64-linux/bin/x86_64-linux-" >> ~/.buildman
> - env:
> - BUILDMAN="kirkwood"
> - env:
>
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
next prev parent reply other threads:[~2016-10-27 4:20 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-26 17:05 [U-Boot] [PATCH 1/6] travis-ci: Use = not : when writing ~/.buildman Stephen Warren
2016-10-26 17:05 ` [U-Boot] [PATCH 2/6] travis-ci: use correct exit code on errors Stephen Warren
2016-10-27 4:21 ` Heiko Schocher
2016-10-29 17:41 ` [U-Boot] [U-Boot, " Tom Rini
2016-10-26 17:05 ` [U-Boot] [PATCH 3/6] travis-ci: centralize ~/.buildman editing Stephen Warren
2016-10-27 4:21 ` Heiko Schocher
2016-10-29 17:41 ` [U-Boot] [U-Boot, " Tom Rini
2016-10-26 17:05 ` [U-Boot] [PATCH 4/6] travis-ci: use buildman -P everywhere Stephen Warren
2016-10-27 4:22 ` Heiko Schocher
2016-10-29 17:41 ` [U-Boot] [U-Boot,4/6] " Tom Rini
2016-10-26 17:05 ` [U-Boot] [PATCH 5/6] travis-ci: don't invoke exit on success Stephen Warren
2016-10-27 6:12 ` Heiko Schocher
2016-10-29 17:41 ` [U-Boot] [U-Boot,5/6] " Tom Rini
2016-10-26 17:05 ` [U-Boot] [PATCH 6/6] travis-ci: compile with buildman when running test/py Stephen Warren
2016-10-26 18:56 ` Stephen Warren
2016-10-26 18:59 ` Tom Rini
2016-10-26 19:04 ` Stephen Warren
2016-10-27 6:13 ` Heiko Schocher
2016-10-29 17:41 ` [U-Boot] [U-Boot, " Tom Rini
2016-10-27 4:20 ` Heiko Schocher [this message]
2016-10-29 17:41 ` [U-Boot] [U-Boot, 1/6] travis-ci: Use = not : when writing ~/.buildman Tom Rini
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=58118099.3090001@denx.de \
--to=hs@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.