All of lore.kernel.org
 help / color / mirror / Atom feed
From: Julien CORJON <corjon.j@ecagroup.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2015-07-27
Date: Tue, 28 Jul 2015 12:19:49 +0000	[thread overview]
Message-ID: <55B77365.5090505@ecagroup.com> (raw)
In-Reply-To: <20150728105715.22962d48@free-electrons.com>

Thomas, All

Le 28/07/2015 10:57, Thomas Petazzoni a ?crit :
> Hello,
>
> Brendan, Guillaume, J?rg, Waldemar, Samuel, Johan, Maxime, Alexey, Max,
> Gustavo, Julien, Vicente, Clayton, see below. Thanks!
>
> On Tue, 28 Jul 2015 08:30:18 +0200 (CEST), Thomas Petazzoni wrote:
>> Build statistics for 2015-07-27
>> ===============================
>>
>>          success : 124
>>         failures : 68
>
> This is getting a bit better, so let's have a look at the build
> failures. Here are some quick stats I gathered on the failure reasons:
>
> 	misc issues:			19
> 	ARC toolchain problems:		12
> 	musl:				 8
> 	too old gcc:			 8
> 	sourceforge download problem:	 6
> 	static linking issues:		 4
> 	atomic issues:			 3
> 	issues already fixed:		 3
> 	host-erlang-rebar timeout:	 2
> 	xtensa toolchain problems:	 2
> 	gcc 5.x problems:		 2
>
>

[snip]

>
>>           arm |                  qt5base-5.5.0 | NOK | http://autobuild.buildroot.net/results/30acea45fb497942129ca57c143bab6174e14609/
>
> painting/qbrush.cpp
> painting/qbrush.cpp:38:29: fatal error: qplatformpixmap.h: No such file or directory
> compilation terminated.
>
> Julien, do you know what's going on ? It might be fixed by one of the
> patch you submitted, can you point to it if that's the case ?

Bug as been submitted to Qt here : 
https://bugreports.qt.io/browse/QTBUG-47400
I made a patch for buildroot here : 
https://patchwork.ozlabs.org/patch/500018/ and we said we tag it as 
"Changes Requested" until Qt mainline patch will be accepted (see 
https://codereview.qt-project.org/#/c/122145/)
Since Qt Continuous integration system does not seems to fail on this 
issue, I think we can include this one to qt5base package "as is".
Should I submit the patch yet or wait for the mainline patch to be accepted?

>
>>      mips64el |                  qt5base-5.5.0 | NOK | http://autobuild.buildroot.net/results/f91de4a596817997b2f35c24b07aec43916c9e1b/
>
> /home/peko/autobuild/instance-0/output/host/usr/mips64el-buildroot-linux-gnu/sysroot/usr/include/gnu/lib-names.h:34:37: fatal error: gnu/lib-names-n64_soft.h: No such file or directory
>   # include <gnu/lib-names-n64_soft.h>
>
> Vicente ?
>
>>        mipsel |                  qt5base-5.5.0 | NOK | http://autobuild.buildroot.net/results/f0891474fe2cd3e47b1489f147e31f698dbd013f/
>
> painting/qbrush.cpp:38:29: fatal error: qplatformpixmap.h: No such file or directory
>   #include "qplatformpixmap.h"
>

[snip]

>
> Thomas
>

Julien

  parent reply	other threads:[~2015-07-28 12:19 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-28  6:30 [Buildroot] [autobuild.buildroot.net] Build results for 2015-07-27 Thomas Petazzoni
2015-07-28  8:57 ` Thomas Petazzoni
2015-07-28 10:34   ` Max Filippov
2015-07-28 10:41   ` Brendan Heading
2015-07-28 12:19   ` Julien CORJON [this message]
2015-07-28 12:21     ` Thomas Petazzoni
2015-07-28 14:00   ` Jörg Krause
2015-07-28 14:05     ` Thomas Petazzoni

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=55B77365.5090505@ecagroup.com \
    --to=corjon.j@ecagroup.com \
    --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.