From: Peter Seiderer <ps.report@gmx.net>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/qt5base: fix building with correct optimization
Date: Tue, 1 Oct 2019 23:48:38 +0200 [thread overview]
Message-ID: <20191001234838.33cbd903@gmx.net> (raw)
In-Reply-To: <20191001233246.36aef601@gmx.net>
Re-added buildroot at builroot.org and Julien Corjon to CC (hit the wrong button for reply)...
Regards,
Peter
On Tue, 1 Oct 2019 23:32:46 +0200, Peter Seiderer <ps.report@gmx.net> wrote:
> Hello Giulio,
>
> On Tue, 1 Oct 2019 12:23:04 +0200, Giulio Benetti <giulio.benetti@benettiengineering.com> wrote:
>
> > On previous patch:
> > https://git.buildroot.net/buildroot/commit/?id=7c0aa83527e0b0179f9e3f73a3e63df1fdc5a6e6
> > we didn't take care that QMAKE_CXXFLAGS_RELEASE variable is set to
> > QMAKE_CFLAGS_OPTIMIZE(-O2) inside the same file:
> > mkspecs/common/gcc-base.conf
> > So overriding all QMAKE_CFLAGS_OPTIMIZE* variables after gcc.base.conf
> > file doesn't change the content of QMAKE_CXXFLAGS_RELEASE.
> > QMAKE_CXXFLAGS_RELEASE/DEBUG is appended to the end of QMAKE_CXXFLAGS in
> > mkspecs/features/default_post.prf if building with or without debug
> > symbols.
> >
> > Let's override directly QMAKE_CFLAGS_RELEASE/DEBUG and
> > QMAKE_CXXFLAGS_RELEASE/DEBUG in qmake.conf.in and drop all
> > QMAKE_CFLAGS_OPTIMIZE* variables overriding.
>
> What is the difference in the resulting compile flags?
>
> >
> > Fixes:
> > http://autobuild.buildroot.net/results/ada/adaa9b4bcc6f9d2b5e82c479859a07e8abf5cf13/
> > http://autobuild.buildroot.net/results/a83/a83bdd1f3bf309c07abebe871b017c331ed36e67/
>
> qgeoaddress.cpp: In function 'QString formattedAddress(const QGeoAddress&, const QString&)':
> qgeoaddress.cpp:285:1: error: VOIDmode on an output
> }
> ^
> (insn 849 12033 850 87 (parallel [
> (const_int 0 [0])
> (reg:SI 970)
> (mem/v:SI (reg/f:SI 3694 [ D.102094.d ]) [-1 S4 A32])
> (reg:SI 970)
> (reg:SI 3527)
> (const_int 0 [0])
> (const_int 32773 [0x8005])
> (const_int 0 [0])
> (clobber (scratch:SI))
> ]) "/home/buildroot/autobuild/instance-1/output-1/host/opt/ext-toolchain/microblazeel-buildroot-linux-uclibc/include/c++/7.4.0/bits/atomic_base.h":304 85 {atomic_compare_and_swapsi}
> (nil))
> qgeoaddress.cpp:285:1: internal compiler error: in do_output_reload, at reload1.c:7978
>
> And why does it fix in internal compile error?
>
> Regards,
> Peter
>
> >
> > Signed-off-by: Giulio Benetti <giulio.benetti@benettiengineering.com>
> > ---
> > package/qt5/qt5base/qmake.conf.in | 8 ++++----
> > 1 file changed, 4 insertions(+), 4 deletions(-)
> >
> > diff --git a/package/qt5/qt5base/qmake.conf.in b/package/qt5/qt5base/qmake.conf.in
> > index 2eb564e172..66b80c302a 100644
> > --- a/package/qt5/qt5base/qmake.conf.in
> > +++ b/package/qt5/qt5base/qmake.conf.in
> > @@ -15,10 +15,10 @@ QMAKE_CXX = $${CROSS_COMPILE}g++
> > # modifications to gcc-base.conf
> > QMAKE_CFLAGS += $${BR_COMPILER_CFLAGS}
> > QMAKE_CXXFLAGS += $${BR_COMPILER_CXXFLAGS}
> > -QMAKE_CFLAGS_OPTIMIZE =
> > -QMAKE_CFLAGS_OPTIMIZE_DEBUG =
> > -QMAKE_CFLAGS_OPTIMIZE_FULL =
> > -QMAKE_CFLAGS_OPTIMIZE_SIZE =
> > +QMAKE_CFLAGS_DEBUG =
> > +QMAKE_CXXFLAGS_DEBUG =
> > +QMAKE_CFLAGS_RELEASE =
> > +QMAKE_CXXFLAGS_RELEASE =
> > CONFIG += nostrip
> >
> > QMAKE_LIBS += -lrt -lpthread -ldl
>
next prev parent reply other threads:[~2019-10-01 21:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-01 10:23 [Buildroot] [PATCH] package/qt5base: fix building with correct optimization Giulio Benetti
[not found] ` <20191001233246.36aef601@gmx.net>
2019-10-01 21:48 ` Peter Seiderer [this message]
2019-10-02 15:53 ` Giulio Benetti
2019-10-02 18:46 ` Peter Seiderer
2019-10-02 19:06 ` Peter Seiderer
2019-10-02 21:30 ` Giulio Benetti
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=20191001234838.33cbd903@gmx.net \
--to=ps.report@gmx.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox