From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [git commit branch/next] qt: bump version
Date: Sun, 26 Feb 2012 21:29:14 +0100 [thread overview]
Message-ID: <877gz9z6cl.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <20120226095808.775a2b05@gmail.com> (Ismael Luceno's message of "Sun, 26 Feb 2012 09:58:08 -0200")
>>>>> "Ismael" == Ismael Luceno <ismael.luceno@gmail.com> writes:
Ismael> Hi.
Ismael> I've been working on QT4.8, and I found that it fails to compile
Ismael> with GCC 4.6.2 on ARM, due to -fstrict-volatile-bitfields becoming
Ismael> default [0].
Ismael> Also, I'm wondering if it should override or append to QMAKE_CFLAGS
Ismael> and QMAKE_CXXFLAGS...
Ismael> [0] <http://gcc.gnu.org/ml/gcc-patches/2010-11/msg02245.html>
I think we can just add -fno-strict-volatile-bitfields to QT_CXXFLAGS
for arm/armeb and gcc 4.6.x.
--
Bye, Peter Korsgaard
prev parent reply other threads:[~2012-02-26 20:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-25 21:52 [Buildroot] [git commit branch/next] qt: bump version Peter Korsgaard
2012-02-26 11:58 ` Ismael Luceno
2012-02-26 20:29 ` Peter Korsgaard [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=877gz9z6cl.fsf@macbook.be.48ers.dk \
--to=jacmet@uclibc.org \
--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