From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] buildman errors
Date: Sun, 24 Jan 2016 14:33:03 -0500 [thread overview]
Message-ID: <20160124193303.GT3359@bill-the-cat> (raw)
In-Reply-To: <56A50378.6030400@denx.de>
On Sun, Jan 24, 2016 at 06:01:44PM +0100, Stefano Babic wrote:
> On 24/01/2016 17:41, Marek Vasut wrote:
> > On Sunday, January 24, 2016 at 05:19:54 PM, Tom Rini wrote:
> >> On Sun, Jan 24, 2016 at 12:00:42PM +0800, Bin Meng wrote:
> >>> Hi,
> >>>
> >>> Summary of 71 commits for 1100 boards (24 threads, 1 job per thread)
> >>> 01: iocon / bamboo: Drop CONFIG_SYS_LONGHELP
> >>>
> >>> blackfin: + bf561-acvilon cm-bf561 blackstamp bf537-minotaur
> >>>
> >>> bct-brettl2 cm-bf527 bf506f-ezkit ip04 bf527-sdp pr1 bf527-ad7160-eval
> >>> bf609-ezkit bf537-stamp bf527-ezkit-v2 cm-bf537e tcm-bf518 cm-bf537u
> >>> bf527-ezkit cm-bf533 bf533-ezkit ibf-dsp561 bf537-pnav bf537-srv1
> >>> cm-bf548 bf538f-ezkit bf548-ezkit bf525-ucr2 blackvme tcm-bf537
> >>> bf533-stamp dnp5370 bf518f-ezbrd bf526-ezbrd bf561-ezkit br4
> >>>
> >>> aarch64: + test
> >>>
> >>> avr32: + atngw100mkii grasshopper atstk1002 atngw100
> >>>
> >>> sh: + sh7753evb sh7785lcr_32bit sh7785lcr
> >>>
> >>> arc: + arcangel4-be axs101 axs103 tb100 arcangel4
> >>>
> >>> openrisc: + openrisc-generic
> >>>
> >>> powerpc: + TQM834x katmai
> >>>
> >>> arm: + mx28evk mx28evk_nand xfi3 bg0900 sansa_fuze_plus
> >>>
> >>> mx23evk m28evk sc_sps_1 mx28evk_spi apx4devkit mx23_olinuxino
> >>> mx28evk_auart_console
> >
> > All of MXS is broken, why ? I don't recall any chances to MXS being done
> > recently, so what happened ?
>
> I confirm this - I have not seen any breakage (but I built today with an
> older gcc). Bing, can you output what you have seen for mxs boards ?
> They looks ok to me.
They're good for me too, BUT! I suspect it comes down to the openssl-dev
requirement on the host side which I also have thought Marek noted at
some point as a problem anyhow due to license issues maybe?
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20160124/ee115069/attachment.sig>
next prev parent reply other threads:[~2016-01-24 19:33 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-24 4:00 [U-Boot] buildman errors Bin Meng
2016-01-24 16:19 ` Tom Rini
2016-01-24 16:41 ` Marek Vasut
2016-01-24 17:01 ` Stefano Babic
2016-01-24 19:33 ` Tom Rini [this message]
2016-01-25 2:42 ` Bin Meng
2016-01-25 2:45 ` Bin Meng
2016-01-25 2:52 ` Marek Vasut
2016-01-25 2:58 ` Bin Meng
2016-01-25 3:01 ` Marek Vasut
2016-01-25 3:12 ` Bin Meng
2016-01-25 3:20 ` Marek Vasut
2016-01-25 2:34 ` Bin Meng
2016-01-25 3:05 ` Tom Rini
2016-01-25 3:18 ` Bin Meng
2016-01-25 14:12 ` Tom Rini
2016-01-26 4:26 ` Bin Meng
2016-01-26 5:29 ` Marek Vasut
2016-01-26 14:47 ` Tom Rini
2016-01-27 1:55 ` Bin Meng
2016-01-27 2:08 ` Tom Rini
2016-01-27 5:21 ` Bin Meng
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=20160124193303.GT3359@bill-the-cat \
--to=trini@konsulko.com \
--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