Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Seiderer <ps.report@gmx.net>
To: buildroot@busybox.net
Subject: [Buildroot] Analysis of build results for 2018-08-09
Date: Mon, 13 Aug 2018 21:49:10 +0200	[thread overview]
Message-ID: <20180813214910.6b6b1bef@gmx.net> (raw)
In-Reply-To: <20180811001555.0b515e22@windsurf>

Hello *,
On Sat, 11 Aug 2018 00:15:55 +0200, Thomas Petazzoni <thomas.petazzoni@bootlin.com> wrote:

> Hello,
> 
> On Fri, 10 Aug 2018 08:00:17 +0200 (CEST), Thomas Petazzoni wrote:
[...]
> 
> >   aarch64_be |                 qt5base-5.11.1 | NOK | http://autobuild.buildroot.net/results/1fe2be0f26e5b92db57a5cfb5646dd253b731a5c |       
> 
> This is just about adapting the Double-Conversion header to support AArch64 BE.
> 

Fixed by [1], compiles fine with the patch applied and using a
buildroot AArch64 BE generated toolchain...

> >         i686 |             qt5location-5.11.1 | NOK | http://autobuild.buildroot.net/results/8b5531e44c4f4258c950902b2cd92d1ac8a8491e |       
> 
> Some crazy C++ error. Peter (Seiderer), could you have a look ?
> 

No clue either, maybe the used compiler
        $ ./host/bin/i686-ctng-linux-gnu-g++ --version
    i686-ctng-linux-gnu-g++ (crosstool-NG hg+-c65fcf8a34b7) 4.8.2

is to old for the c++11 [2] QPointer<QGeoMap> and QOverload<const QString &>::of(&QGeoMap::copyrightsChanged)
dance for the connect?

Regards,
Peter

[1] https://patchwork.ozlabs.org/patch/957169/
[2] http://doc.qt.io/qt-5/qtglobal.html#qOverload

      parent reply	other threads:[~2018-08-13 19:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-10  6:00 [Buildroot] [autobuild.buildroot.net] Build results for 2018-08-09 Thomas Petazzoni
2018-08-10 22:15 ` [Buildroot] Analysis of build " Thomas Petazzoni
2018-08-11  0:20   ` Matthew Weber
2018-08-11 10:25     ` Thomas Petazzoni
2018-08-13 19:49   ` Peter Seiderer [this message]

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=20180813214910.6b6b1bef@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox