From: Luca Ceresoli <luca@lucaceresoli.net>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2013-02-12
Date: Mon, 18 Feb 2013 20:37:15 +0100 [thread overview]
Message-ID: <512282EB.7070702@lucaceresoli.net> (raw)
In-Reply-To: <20130215055400.6688c117@skate>
Thomas Petazzoni wrote:
> Dear Luca Ceresoli,
>
> On Thu, 14 Feb 2013 22:21:49 +0100, Luca Ceresoli wrote:
>
>> Should I send a patch to set -no-pch? I'm reluctant because it's not a real
>> fix, and compile time could increase significantly, I guess.
>>
>> Thomas, this probably affects Qt5 Beta 1 as well, according to this blog
>> post:
>> http://gpupowered.org/node/14. Would you mind testing it on your Qt5 branch?
> For Qt5, I do have -no-pch otherwise it doesn't build
> (http://git.free-electrons.com/users/thomas-petazzoni/buildroot/commit/?h=qt5&id=7c1f7b9967d814e3f5c838e7090ac04b9d06af51).
> Apparently, there are bugs in the precompiled headers implementation.
Given that precompiled headers are disabled when using ccache, and they are
broken otherwise (at least with some toolchains), I think it's best to just
add -no-pch inconditionally.
I'll send a patch that does so, and copy your comment at the commit you
pointedme to:
> -no-pch to workaround the issue described at
> http://comments.gmane.org/gmane.comp.lib.qt.devel/5933
You might want to sign off the patch then.
Luca
next prev parent reply other threads:[~2013-02-18 19:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-13 7:34 [Buildroot] [autobuild.buildroot.net] Build results for 2013-02-12 Thomas Petazzoni
2013-02-14 21:21 ` Luca Ceresoli
2013-02-15 4:54 ` Thomas Petazzoni
2013-02-18 19:37 ` Luca Ceresoli [this message]
2013-02-18 19:39 ` [Buildroot] [PATCH] qt: disable precompiled headers to workaround compilation failure Luca Ceresoli
2013-02-18 21:27 ` Peter Korsgaard
2013-02-14 23:01 ` [Buildroot] [autobuild.buildroot.net] Build results for 2013-02-12 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=512282EB.7070702@lucaceresoli.net \
--to=luca@lucaceresoli.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 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.