Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Marco Trapanese <marcotrapanese@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] Qt5 fails to compile with gcc 6.1.0
Date: Sat, 7 May 2016 15:02:34 +0200	[thread overview]
Message-ID: <572DE76A.4070103@gmail.com> (raw)
In-Reply-To: <20160507142800.6fec8574@free-electrons.com>

Il 07/05/2016 14:28, Thomas Petazzoni ha scritto:

> However your version is "-dirty" which means you have modified
> Buildroot. But we have no idea which modifications you have made. Maybe
> those modifications are the reason for the failure?

I did the following:

git clone git://git.buildroot.net/buildroot
git pull

then I applied the patches you suggested for Qt5 and bluez5: 
https://patchwork.ozlabs.org/patch/612072/
Of course I changed the post-build script and the genimage commands in 
the boards directory, but I think I'm allowed to do this.

> Also, please don't use gcc 6.x for now, and stay with gcc 4.9, so
> please test with gcc 4.9.
>
> Please disable LTO support for the moment. It isn't enabled by default,
> and we don't test it that often, so please disable it for now.
>
> Please stay with the default of binutils 2.25 instead of selecting
> binutils 2.26.
>
> Once you have changed those configuration options and removed your local
> Buildroot modifications, please try again a complete build "make clean
> all" and see if it works or not. If it doesn't, I'll try to reproduce
> here.


Well, I've downloaded buildroot from scratch to be sure.
I confirm the "dirty" flag appears after applying the patches for 
Qt5/bluez5.

Attached there is the new .config file.
It's compiling right now. I will inform you of the results.

Thanks
Marco

-------------- next part --------------
A non-text attachment was scrubbed...
Name: .config
Type: application/xml
Size: 92413 bytes
Desc: not available
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20160507/08754f04/attachment-0001.wsdl>

  reply	other threads:[~2016-05-07 13:02 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-07  9:51 [Buildroot] Qt5 fails to compile with gcc 6.1.0 Marco Trapanese
2016-05-07 11:50 ` Marco Trapanese
2016-05-07 12:01   ` Marco Trapanese
2016-05-07 12:11   ` Thomas Petazzoni
2016-05-07 12:16     ` Marco Trapanese
2016-05-07 12:28       ` Thomas Petazzoni
2016-05-07 13:02         ` Marco Trapanese [this message]
2016-05-07 19:27         ` [Buildroot] Kernel panic with glibc Marco Trapanese
2016-05-07 22:08 ` [Buildroot] Qt5 fails to compile with gcc 6.1.0 Arnout Vandecappelle

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=572DE76A.4070103@gmail.com \
    --to=marcotrapanese@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox