From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2013-11-21
Date: Fri, 22 Nov 2013 09:22:44 +0100 [thread overview]
Message-ID: <20131122092244.03b0b696@skate> (raw)
In-Reply-To: <CA+csPL55=jghW9jAuzqYW2sbDJgBE4EWfvani-5phAAr9si7-A@mail.gmail.com>
Dear Espen Frimann Koren,
On Fri, 22 Nov 2013 08:58:22 +0100, Espen Frimann Koren wrote:
> I tried last week to tell you that I found the reason for the
> qt5declarative-5.1.1 build failure on ARM.
>
> Either you have to change the defconfig of the build, or you have to
> put in a dependency on the package qt5declarative to locale support
> in the toolchain. For instance hide the package as long as the
> toolchain doesn't support locale (BR2_TOOLCHAIN_BUILDROOT_LOCALE), or
> automatically select BR2_TOOLCHAIN_BUILDROOT_LOCALE when ticking off
> qt5declarative
What bothers me a bit with this conclusion is that the compilation
fails when building something for the *host*, so the fact that the
target does or does not support locales should not make any difference.
See the compilation line:
g++ -c -pipe -O2 -fPIC -fvisibility=hidden -fvisibility-inlines-hidden -fno-exceptions -Wall -W -D_REENTRANT -DQT_NO_LIBUDEV -DQT_NO_XCB -DQT_BUILD_QMLDEVTOOLS_LIB -DQT_BUILDING_QT -DQT_NO_CAST_TO_ASCII -DQT_ASCII_CAST_WARNINGS -DQT_MOC_COMPAT -DQT_USE_QSTRINGBUILDER -DQT_DEPRECATED_WARNINGS -DQT_DISABLE_DEPRECATED_BEFORE=0x050000 -DQT_NO_EXCEPTIONS -D_LARGEFILE64_SOURCE -D_LARGEFILE_SOURCE -DQT_NO_DEBUG -DQT_BOOTSTRAP_LIB -DQT_BOOTSTRAPPED -DQT_LITE_UNICODE -DQT_NO_CAST_TO_ASCII -DQT_NO_CODECS -DQT_NO_DATASTREAM -DQT_NO_LIBRARY -DQT_NO_QOBJECT -DQT_NO_SYSTEMLOCALE -DQT_NO_THREAD -DQT_NO_UNICODETABLES -DQT_NO_USING_NAMESPACE -DQT_NO_DEPRECATED -DQT_NO_TRANSLATION -DQT_QMAKE_LOCATION="/scratch/peko/build/qt5base-5.1.1/bin/qmake" -I/scratch/peko/host/usr/mkspecs/linux-g++ -I. -I../../include -I../../include/QtQml -I../../include/QtQml/5.1.1 -I../../include/QtQml/5.1.1/QtQml -I/scratch/peko/host/usr/arm-buildroot-linux-uclibcgnueabi/sysroot/usr/include -I/scratch/peko/host/usr/a
rm-build
root-linux-uclibcgnueabi/sysroot/usr/include/QtCore -I/scratch/peko/host/usr/arm-buildroot-linux-uclibcgnueabi/sysroot/usr/include/QtXml -I/scratch/peko/host/usr/arm-buildroot-linux-uclibcgnueabi/sysroot/usr/include/QtCore/5.1.1 -I/scratch/peko/host/usr/arm-buildroot-linux-uclibcgnueabi/sysroot/usr/include/QtCore/5.1.1/QtCore -I/scratch/peko/host/usr/arm-buildroot-linux-uclibcgnueabi/sysroot/usr/include/QtXml/5.1.1 -I/scratch/peko/host/usr/arm-buildroot-linux-uclibcgnueabi/sysroot/usr/include/QtXml/5.1.1/QtXml -o .obj/release-shared/qqmljsparser.o ../qml/qml/parser/qqmljsparser.cpp
It is using "g++", so it is building for the *host*. But it is using a
huge number of header files for the target. So I think there is
something screwed in the Qt build process *or* in the way we use it.
Selecting locale support for the target will just "hide" the problem
without fixing it for real, I believe (but I may have misunderstood the
problem, of course).
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2013-11-22 8:22 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-22 7:30 [Buildroot] [autobuild.buildroot.net] Build results for 2013-11-21 Thomas Petazzoni
2013-11-22 7:58 ` Espen Frimann Koren
2013-11-22 8:22 ` Thomas Petazzoni [this message]
2013-12-23 13:09 ` Fatih Aşıcı
2013-11-22 8:14 ` [Buildroot] Analysis of build failures Thomas Petazzoni
2013-11-22 9:15 ` Fabio Porcedda
2013-11-29 10:25 ` Fabio Porcedda
2013-11-22 10:42 ` Thomas De Schampheleire
2013-11-22 12:59 ` Thomas De Schampheleire
2013-11-22 16:01 ` Arnout Vandecappelle
2013-11-22 16:03 ` Thomas De Schampheleire
2013-11-22 11:56 ` Thomas Petazzoni
2013-11-22 11:58 ` Fatih Aşıcı
2013-11-22 12:13 ` Thomas Petazzoni
2013-11-23 23:07 ` Arnout Vandecappelle
2013-11-22 15:20 ` Peter Korsgaard
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=20131122092244.03b0b696@skate \
--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