From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Qt5 fails to compile with gcc 6.1.0
Date: Sat, 7 May 2016 14:28:00 +0200 [thread overview]
Message-ID: <20160507142800.6fec8574@free-electrons.com> (raw)
In-Reply-To: <572DDCA5.8060204@gmail.com>
Hello,
On Sat, 7 May 2016 14:16:37 +0200, Marco Trapanese wrote:
> Yes, I always "make clean all".
>
> Attached there is the .config file.
> The version is Buildroot 2016.05-git-01197-gda433d6-dirty
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?
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.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-05-07 12:28 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 [this message]
2016-05-07 13:02 ` Marco Trapanese
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=20160507142800.6fec8574@free-electrons.com \
--to=thomas.petazzoni@free-electrons.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