On 02/01/2016 06:57 PM, Tom Rini wrote:
On Mon, Jan 25, 2016 at 08:22:41PM +0100, Roger Meier wrote:
- install using addons.apt
- remove MAKEALL
- split mpc85xx boards
- remove TEST_CONFIG_CMD, just info
- fetch mips toolchain via buildman
- remove --list-error-boards param
- conditional script
- use TOOLCHAIN instead of INSTALL_TOOLCHAIN
- add aarch64
- enable notifications via email
Signed-off-by: Roger Meier <r.me...@siemens.com>
Cc: Wolfgang Denk <w...@denx.de>
Cc: Heiko Schocher <h...@denx.de>
Cc: Tom Rini <tr...@ti.com>
Cc: Daniel Schwierzeck <daniel.schwierz...@gmail.com>
Cc: Andreas Färber <afaer...@suse.de>
Tested-by: Daniel Schwierzeck <daniel.schwierz...@gmail.com>
Acked-by: Heiko Schocher <h...@denx.de>
Applied to u-boot/master, thanks!
I wanted to add something to this file, so I set up my own travis-ci.org
account and made it run against my own github U-Boot repo "fork" to test
my change. However, most of the builds failed before I even modified
.travis.yml. For example:
$ if [[ "${TOOLCHAIN}" == *arm* ]]; then sh
eldk-eglibc-i686-arm-toolchain-gmae-5.4.sh -y ; fi
Enter target directory for SDK (default: /opt/eldk-5.4/armv5te):
/opt/eldk-5.4/armv5te
You are about to install the SDK to "/opt/eldk-5.4/armv5te". Proceed[Y/n]?Y
Sorry, you are not allowed to execute as root.
Do I need to perform some manual configuration of my
repo/branch/profile/... before this .travis.yml will work correctly
(container vs VM I wonder?), or perhaps obtain some kind of
authorization from the Travis CI admins? If so, if that could all be
documented in a comment at the top of .travis.yml that would be
extremely helpful. Bonus points if it can be handled simply be adding
extra configuration options into .travis.yml so that it "just works"
without manual steps.
_______________________________________________
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot
