From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] buildman errors
Date: Tue, 26 Jan 2016 06:29:22 +0100 [thread overview]
Message-ID: <201601260629.22976.marex@denx.de> (raw)
In-Reply-To: <CAEUhbmWqz7yMAonRY3APw_mgCc-gDRP9Q3N_0RqzBKSYZf6Y7w@mail.gmail.com>
On Tuesday, January 26, 2016 at 05:26:07 AM, Bin Meng wrote:
> Hi Tom,
>
> On Mon, Jan 25, 2016 at 10:12 PM, Tom Rini <trini@konsulko.com> wrote:
> > On Mon, Jan 25, 2016 at 11:18:26AM +0800, Bin Meng wrote:
> >> Hi Tom,
> >>
> >> On Mon, Jan 25, 2016 at 11:05 AM, Tom Rini <trini@konsulko.com> wrote:
> >> > On Mon, Jan 25, 2016 at 10:34:16AM +0800, Bin Meng wrote:
> >> >> Hi Tom,
> >> >>
> >> >> On Mon, Jan 25, 2016 at 12:19 AM, Tom Rini <trini@konsulko.com> 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
> >> >> >>
> >> >> >> nds32: + adp-ag101p
> >> >> >
> >> >> > I need to finally fetch a few toolchains as I don't do
> >> >> > avr32/sh/openrisc/nds32 iirc. As a tangent, x86 is very broken
> >> >> > with gcc 5.x, can you look into it? :)
> >> >>
> >> >> Sure, I can look into x86. Which gcc 5.x toolchain are you using?
> >> >
> >> > Pretty much any, I've seen it for a long time but not had time to poke
> >> > at the libgcc "fun" that's involved here.
> >>
> >> I mean if there is any prebuilt gcc 5.x for me to grab and test? Or do
> >> I need build one from gcc source?
> >
> > Fedora has shipped with gcc 5.x for a release or two and Debian/unstable
> > is how I get all of my gcc 5.x toolchains for build testing.
>
> I installed a fresh Fedora 23 and got gcc 5.1.1 up and running.
> However I see _zero_ compiler warnings/errors using gcc 5.1.1 when
> building all of the 9 x86 boards.
>
> The only thing I noticed, which is probably best matched to what you
> said "x86 is very broken with gcc 5.x", is:
>
> HOSTCC tools/aisimage.o
> In file included from tools/aisimage.c:10:0:
> include/image.h:923:27: fatal error: openssl/evp.h: No such file or
> directory compilation terminated.
> scripts/Makefile.host:111: recipe for target 'tools/aisimage.o' failed
> make[1]: *** [tools/aisimage.o] Error 1
> Makefile:1196: recipe for target 'tools' failed
> make: *** [tools] Error 2
>
> But this is nothing related to gcc 5.x. It should be something related
> to openssl. After I "dnf install openssl-devel", minnowmax can be
> built successfully without any error/warning.
Yeah, that's our standard openssl bug :-)
next prev parent reply other threads:[~2016-01-26 5:29 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
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 [this message]
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=201601260629.22976.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 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.