From: Peter Seiderer <ps.report@gmx.net>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2017-02-08
Date: Thu, 9 Feb 2017 17:35:06 +0100 [thread overview]
Message-ID: <20170209173506.7894720f@gmx.net> (raw)
In-Reply-To: <20170209072858.F0F7520C2B@mail.free-electrons.com>
On Thu, 9 Feb 2017 08:28:58 +0100 (CET), Thomas Petazzoni <thomas.petazzoni@free-electrons.com> wrote:
> Hello,
>
> Build statistics for 2017-02-08
> ================================
>
[...]
> mipsel | qt5base-5.8.0 | NOK | http://autobuild.buildroot.net/results/219162ba616289f799a5053c4dcc6b8574284283
Project ERROR: Library 'libpng' is not defined.
make[3]: *** [sub-3rdparty-freetype-make_first] Error 3
Maybe https://codereview.qt-project.org/#/c/182309/3 is missing?
> i686 | qt5base-5.8.0 | NOK | http://autobuild.buildroot.net/results/1841e983b91305ab814274bdf382cd70e1c1c110
> mips64el | qt5base-5.8.0 | NOK | http://autobuild.buildroot.net/results/b5f59d85c9f175c9b0f6c11b47456fbadee25daa
> nios2 | qt5base-5.8.0 | NOK | http://autobuild.buildroot.net/results/9d2efb3aece56dcb5d9ddbc3ca3e0ecaeff9b8a6
> arm | qt5base-5.8.0 | NOK | http://autobuild.buildroot.net/results/20307edcbcb9c44480e0b03c30eeefc3ad812aab
g++ -c -o project.o -pipe -std=c++11 ...
cc1plus: error: unrecognized command line option "-std=c++11"
The host compiler needs support for c++11, any possibility to express this requirement in buildroot?
Regards,
Peter
next prev parent reply other threads:[~2017-02-09 16:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-09 7:28 [Buildroot] [autobuild.buildroot.net] Build results for 2017-02-08 Thomas Petazzoni
2017-02-09 16:35 ` Peter Seiderer [this message]
2017-02-09 16:39 ` Thomas Petazzoni
2017-02-09 17:30 ` Peter Seiderer
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=20170209173506.7894720f@gmx.net \
--to=ps.report@gmx.net \
--cc=buildroot@busybox.net \
/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.