* [Buildroot] [autobuild.buildroot.net] Build results for 2013-11-21
@ 2013-11-22 7:30 Thomas Petazzoni
2013-11-22 7:58 ` Espen Frimann Koren
2013-11-22 8:14 ` [Buildroot] Analysis of build failures Thomas Petazzoni
0 siblings, 2 replies; 16+ messages in thread
From: Thomas Petazzoni @ 2013-11-22 7:30 UTC (permalink / raw)
To: buildroot
Build statistics for 2013-11-21
===============================
success : 77
failures : 28
timeouts : 0
TOTAL : 105
Classification of failures by reason
====================================
libglib2-2.36.3 | 3
toolchain-external-undefined | 2
rpm-5.2.0 | 1
libroxml-2.2.3 | 1
omniorb-4.1.6 | 1
iozone-3_414 | 1
w_scan-20130331 | 1
attr-2.4.47 | 1
tinymembench-v0.2 | 1
qt-4.8.5 | 1
qt5declarative-5.1.1 | 1
libcap-ng-0.7.3 | 1
sdl_ttf-2.0.11 | 1
libvncserver-0.9.9 | 1
icu-51.2 | 1
bootutils-1.0.0 | 1
apr-1.4.8 | 1
schifra-0.0.1 | 1
alsa-lib-1.0.26 | 1
kmod-15 | 1
lvm2-2.02.103 | 1
sqlite-3080002 | 1
ola-0.8.32 | 1
mdadm-3.2.6 | 1
openssl-1.0.1e | 1
Detail of failures
===================
mipsel | alsa-lib-1.0.26 | NOK | http://autobuild.buildroot.net/results/417dac44eb077079f16a039881a45fa1b1782497/
mipsel | apr-1.4.8 | NOK | http://autobuild.buildroot.net/results/20926ed11e7d86cd6c54700eb609b3fa1740b8a7/
mipsel | attr-2.4.47 | NOK | http://autobuild.buildroot.net/results/03e5b85c71e5b624e42245f04d305042ec9136fa/
mipsel | bootutils-1.0.0 | NOK | http://autobuild.buildroot.net/results/a51b3723f176a98abff809313a5f863e2539e103/
bfin | icu-51.2 | NOK | http://autobuild.buildroot.net/results/fc643356587aaed0c3e7c2205dad0c40f02eede1/
xtensa | iozone-3_414 | NOK | http://autobuild.buildroot.net/results/04896be35649215d8141cb737185c0c10ad11d12/
xtensa | kmod-15 | NOK | http://autobuild.buildroot.net/results/622d25321d76f505de6aef4e33d0e421ba701de5/
avr32 | libcap-ng-0.7.3 | NOK | http://autobuild.buildroot.net/results/73c7c211a51c312bbe4eb6a540f3ad9c92c79ebe/
microblaze | libglib2-2.36.3 | NOK | http://autobuild.buildroot.net/results/2cd1b11c43655cfd3bcbe8f6e127ea5e4a607e9d/
microblaze | libglib2-2.36.3 | NOK | http://autobuild.buildroot.net/results/bcbc99ec7987fe10d4e752eb96840a7ec1be2744/
bfin | libglib2-2.36.3 | NOK | http://autobuild.buildroot.net/results/d5c743294314584473cdd6098ebcfae42971803c/
avr32 | libroxml-2.2.3 | NOK | http://autobuild.buildroot.net/results/e22d94fca3eabb4e54d82af04319f17ad8e10c20/
arm | libvncserver-0.9.9 | NOK | http://autobuild.buildroot.net/results/c3082693fe0da0c54d4bbf950dd6d74e1395c1d9/
arm | lvm2-2.02.103 | NOK | http://autobuild.buildroot.net/results/b0b386969459dda9c294f1ccb4927ca225fa6bdd/
bfin | mdadm-3.2.6 | NOK | http://autobuild.buildroot.net/results/52cc56df2aa278d92141918de74833d7e4fd3d47/
aarch64 | ola-0.8.32 | NOK | http://autobuild.buildroot.net/results/5967dfd4bd7c2b68e2911a98b9b84c8fe7adf0aa/
arm | omniorb-4.1.6 | NOK | http://autobuild.buildroot.net/results/dfc083bff04eba68456edd359424293842b6f42d/
microblaze | openssl-1.0.1e | NOK | http://autobuild.buildroot.net/results/2299063bb4e84833ee3edccec960d551b5fcdfe5/
mips64el | qt-4.8.5 | NOK | http://autobuild.buildroot.net/results/fd7e7e53290f235b540ed5f3c784e2584fdb41e0/
arm | qt5declarative-5.1.1 | NOK | http://autobuild.buildroot.net/results/82bb89d5b29dc6bd40f840bc04845b6c87157985/
mips64el | rpm-5.2.0 | NOK | http://autobuild.buildroot.net/results/bcff4b81bfbb1191f97317b0945c74d948c9774b/
arm | schifra-0.0.1 | NOK | http://autobuild.buildroot.net/results/1ec3664f28492bf3da53dcbe8ceeb165bce8df6d/
arm | sdl_ttf-2.0.11 | NOK | http://autobuild.buildroot.net/results/f4ad0468f17520a645f029878876a972421a87b4/
arc | sqlite-3080002 | NOK | http://autobuild.buildroot.net/results/4f09bbb3cf646e7e45c86d43a50b440245e136e2/
mips64el | tinymembench-v0.2 | NOK | http://autobuild.buildroot.net/results/bab68bcf8714f215ac0b0c2546fa06608377fbb0/
powerpc | toolchain-external-undefined | NOK | http://autobuild.buildroot.net/results/8fb291915b3ce5dc955f5e7e60eea2a4a6202143/
arm | toolchain-external-undefined | NOK | http://autobuild.buildroot.net/results/cc4c41b99005c82e546a9e2916df97180be32b2b/
powerpc | w_scan-20130331 | NOK | http://autobuild.buildroot.net/results/7ac90c6087640585a9afb0e31ad9e690eded89f5/
--
http://autobuild.buildroot.net
^ permalink raw reply [flat|nested] 16+ messages in thread
* [Buildroot] [autobuild.buildroot.net] Build results for 2013-11-21
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
2013-11-22 8:14 ` [Buildroot] Analysis of build failures Thomas Petazzoni
1 sibling, 1 reply; 16+ messages in thread
From: Espen Frimann Koren @ 2013-11-22 7:58 UTC (permalink / raw)
To: buildroot
Hi.
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
Sp1
On 22 November 2013 08:30, Thomas Petazzoni <
thomas.petazzoni@free-electrons.com> wrote:
> Build statistics for 2013-11-21
> ===============================
>
> success : 77
> failures : 28
> timeouts : 0
> TOTAL : 105
>
> Classification of failures by reason
> ====================================
>
> libglib2-2.36.3 | 3
> toolchain-external-undefined | 2
> rpm-5.2.0 | 1
> libroxml-2.2.3 | 1
> omniorb-4.1.6 | 1
> iozone-3_414 | 1
> w_scan-20130331 | 1
> attr-2.4.47 | 1
> tinymembench-v0.2 | 1
> qt-4.8.5 | 1
> qt5declarative-5.1.1 | 1
> libcap-ng-0.7.3 | 1
> sdl_ttf-2.0.11 | 1
> libvncserver-0.9.9 | 1
> icu-51.2 | 1
> bootutils-1.0.0 | 1
> apr-1.4.8 | 1
> schifra-0.0.1 | 1
> alsa-lib-1.0.26 | 1
> kmod-15 | 1
> lvm2-2.02.103 | 1
> sqlite-3080002 | 1
> ola-0.8.32 | 1
> mdadm-3.2.6 | 1
> openssl-1.0.1e | 1
>
> Detail of failures
> ===================
>
> mipsel | alsa-lib-1.0.26 | NOK |
> http://autobuild.buildroot.net/results/417dac44eb077079f16a039881a45fa1b1782497/
> mipsel | apr-1.4.8 | NOK |
> http://autobuild.buildroot.net/results/20926ed11e7d86cd6c54700eb609b3fa1740b8a7/
> mipsel | attr-2.4.47 | NOK |
> http://autobuild.buildroot.net/results/03e5b85c71e5b624e42245f04d305042ec9136fa/
> mipsel | bootutils-1.0.0 | NOK |
> http://autobuild.buildroot.net/results/a51b3723f176a98abff809313a5f863e2539e103/
> bfin | icu-51.2 | NOK |
> http://autobuild.buildroot.net/results/fc643356587aaed0c3e7c2205dad0c40f02eede1/
> xtensa | iozone-3_414 | NOK |
> http://autobuild.buildroot.net/results/04896be35649215d8141cb737185c0c10ad11d12/
> xtensa | kmod-15 | NOK |
> http://autobuild.buildroot.net/results/622d25321d76f505de6aef4e33d0e421ba701de5/
> avr32 | libcap-ng-0.7.3 | NOK |
> http://autobuild.buildroot.net/results/73c7c211a51c312bbe4eb6a540f3ad9c92c79ebe/
> microblaze | libglib2-2.36.3 | NOK |
> http://autobuild.buildroot.net/results/2cd1b11c43655cfd3bcbe8f6e127ea5e4a607e9d/
> microblaze | libglib2-2.36.3 | NOK |
> http://autobuild.buildroot.net/results/bcbc99ec7987fe10d4e752eb96840a7ec1be2744/
> bfin | libglib2-2.36.3 | NOK |
> http://autobuild.buildroot.net/results/d5c743294314584473cdd6098ebcfae42971803c/
> avr32 | libroxml-2.2.3 | NOK |
> http://autobuild.buildroot.net/results/e22d94fca3eabb4e54d82af04319f17ad8e10c20/
> arm | libvncserver-0.9.9 | NOK |
> http://autobuild.buildroot.net/results/c3082693fe0da0c54d4bbf950dd6d74e1395c1d9/
> arm | lvm2-2.02.103 | NOK |
> http://autobuild.buildroot.net/results/b0b386969459dda9c294f1ccb4927ca225fa6bdd/
> bfin | mdadm-3.2.6 | NOK |
> http://autobuild.buildroot.net/results/52cc56df2aa278d92141918de74833d7e4fd3d47/
> aarch64 | ola-0.8.32 | NOK |
> http://autobuild.buildroot.net/results/5967dfd4bd7c2b68e2911a98b9b84c8fe7adf0aa/
> arm | omniorb-4.1.6 | NOK |
> http://autobuild.buildroot.net/results/dfc083bff04eba68456edd359424293842b6f42d/
> microblaze | openssl-1.0.1e | NOK |
> http://autobuild.buildroot.net/results/2299063bb4e84833ee3edccec960d551b5fcdfe5/
> mips64el | qt-4.8.5 | NOK |
> http://autobuild.buildroot.net/results/fd7e7e53290f235b540ed5f3c784e2584fdb41e0/
> arm | qt5declarative-5.1.1 | NOK |
> http://autobuild.buildroot.net/results/82bb89d5b29dc6bd40f840bc04845b6c87157985/
> mips64el | rpm-5.2.0 | NOK |
> http://autobuild.buildroot.net/results/bcff4b81bfbb1191f97317b0945c74d948c9774b/
> arm | schifra-0.0.1 | NOK |
> http://autobuild.buildroot.net/results/1ec3664f28492bf3da53dcbe8ceeb165bce8df6d/
> arm | sdl_ttf-2.0.11 | NOK |
> http://autobuild.buildroot.net/results/f4ad0468f17520a645f029878876a972421a87b4/
> arc | sqlite-3080002 | NOK |
> http://autobuild.buildroot.net/results/4f09bbb3cf646e7e45c86d43a50b440245e136e2/
> mips64el | tinymembench-v0.2 | NOK |
> http://autobuild.buildroot.net/results/bab68bcf8714f215ac0b0c2546fa06608377fbb0/
> powerpc | toolchain-external-undefined | NOK |
> http://autobuild.buildroot.net/results/8fb291915b3ce5dc955f5e7e60eea2a4a6202143/
> arm | toolchain-external-undefined | NOK |
> http://autobuild.buildroot.net/results/cc4c41b99005c82e546a9e2916df97180be32b2b/
> powerpc | w_scan-20130331 | NOK |
> http://autobuild.buildroot.net/results/7ac90c6087640585a9afb0e31ad9e690eded89f5/
>
>
> --
> http://autobuild.buildroot.net
>
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20131122/b483aa4d/attachment.html>
^ permalink raw reply [flat|nested] 16+ messages in thread
* [Buildroot] Analysis of build failures
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:14 ` Thomas Petazzoni
2013-11-22 9:15 ` Fabio Porcedda
` (4 more replies)
1 sibling, 5 replies; 16+ messages in thread
From: Thomas Petazzoni @ 2013-11-22 8:14 UTC (permalink / raw)
To: buildroot
Hello,
On Fri, 22 Nov 2013 08:30:02 +0100 (CET), Thomas Petazzoni wrote:
> mipsel | alsa-lib-1.0.26 | NOK | http://autobuild.buildroot.net/results/417dac44eb077079f16a039881a45fa1b1782497/
> mipsel | apr-1.4.8 | NOK | http://autobuild.buildroot.net/results/20926ed11e7d86cd6c54700eb609b3fa1740b8a7/
> mipsel | attr-2.4.47 | NOK | http://autobuild.buildroot.net/results/03e5b85c71e5b624e42245f04d305042ec9136fa/
> mipsel | bootutils-1.0.0 | NOK | http://autobuild.buildroot.net/results/a51b3723f176a98abff809313a5f863e2539e103/
Those four ones are the same:
configure: error: C compiler cannot create executables
probably a toolchain configuration problem, I need to look into this.
> bfin | icu-51.2 | NOK | http://autobuild.buildroot.net/results/fc643356587aaed0c3e7c2205dad0c40f02eede1/
I believe the problem here is that Blackfin needs a "_" to be prefixed
on assembly symbols, compared to the corresponding C symbol.
> xtensa | iozone-3_414 | NOK | http://autobuild.buildroot.net/results/04896be35649215d8141cb737185c0c10ad11d12/
iozone_linux-noaio.o:(.literal+0xfec): undefined reference to `pthread_setaffinity_np'
> xtensa | kmod-15 | NOK | http://autobuild.buildroot.net/results/622d25321d76f505de6aef4e33d0e421ba701de5/
/home/test/test/2/output/host/usr/lib/gcc/xtensa-buildroot-linux-uclibc/4.7.3/../../../../xtensa-buildroot-linux-uclibc/bin/ld: BFD (GNU Binutils) 2.22 internal error, aborting at elf32-xtensa.c line 3374 in elf_xtensa_finish_dynamic_sections
-> seems like an update to Xtensa binutils is needed.
> avr32 | libcap-ng-0.7.3 | NOK | http://autobuild.buildroot.net/results/73c7c211a51c312bbe4eb6a540f3ad9c92c79ebe/
TLS not available on AVR32, discussion on-going on how to solve this.
> microblaze | libglib2-2.36.3 | NOK | http://autobuild.buildroot.net/results/2cd1b11c43655cfd3bcbe8f6e127ea5e4a607e9d/
> microblaze | libglib2-2.36.3 | NOK | http://autobuild.buildroot.net/results/bcbc99ec7987fe10d4e752eb96840a7ec1be2744/
Missing compiler intrinsics. There are patches from Spenser to add
internal toolchain support for Microblaze, so that we can remove the
broken external toolchains.
> bfin | libglib2-2.36.3 | NOK | http://autobuild.buildroot.net/results/d5c743294314584473cdd6098ebcfae42971803c/
A patch has been sent by Thomas DS to make libglib and all its reverse
dependencies not available on !MMU. I believe it's the good way to go
for now, until we have a proper patch to make libglib2 usable on !MMU
systems. Peter, can you merge http://patchwork.ozlabs.org/patch/292839/ ?
> avr32 | libroxml-2.2.3 | NOK | http://autobuild.buildroot.net/results/e22d94fca3eabb4e54d82af04319f17ad8e10c20/
Simon Dawson has already sent a patch to fix this:
http://patchwork.ozlabs.org/patch/293203/. Peter, can you merge this.
> arm | libvncserver-0.9.9 | NOK | http://autobuild.buildroot.net/results/c3082693fe0da0c54d4bbf950dd6d74e1395c1d9/
libvncserver needs thread support.
> arm | lvm2-2.02.103 | NOK | http://autobuild.buildroot.net/results/b0b386969459dda9c294f1ccb4927ca225fa6bdd/
Missing dependency?
/home/test/test/1/output/host/usr/bin/arm-linux-gcc -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -pipe -Os -fPIC -O2 --static -O2 -L../libdm -L../lib -L../libdaemon/client -L../libdm \
-o dmsetup dmsetup.o -ldevmapper
/home/test/test/1/output/host/opt/ext-toolchain/bin/../lib/gcc/arm-buildroot-linux-uclibcgnueabi/4.7.3/../../../../arm-buildroot-linux-uclibcgnueabi/bin/ld: cannot find -ldevmapper
> bfin | mdadm-3.2.6 | NOK | http://autobuild.buildroot.net/results/52cc56df2aa278d92141918de74833d7e4fd3d47/
Needs MMU. Gustavo has sent a patch,
http://patchwork.ozlabs.org/patch/293083/.
> aarch64 | ola-0.8.32 | NOK | http://autobuild.buildroot.net/results/5967dfd4bd7c2b68e2911a98b9b84c8fe7adf0aa/
I've sent two patches to fix this:
http://patchwork.ozlabs.org/patch/293258/ and
http://patchwork.ozlabs.org/patch/293259/.
> arm | omniorb-4.1.6 | NOK | http://autobuild.buildroot.net/results/dfc083bff04eba68456edd359424293842b6f42d/
Thread support needed, patch at
http://patchwork.ozlabs.org/patch/293205/.
> microblaze | openssl-1.0.1e | NOK | http://autobuild.buildroot.net/results/2299063bb4e84833ee3edccec960d551b5fcdfe5/
Needs the internal toolchain backend support for Microblaze.
> mips64el | qt-4.8.5 | NOK | http://autobuild.buildroot.net/results/fd7e7e53290f235b540ed5f3c784e2584fdb41e0/
There is no support for mips64 in QtScript, which uses JavaScriptCore.
Options are:
* Disable the possibility of enabling QtScript on mips64el/mips64
* Adapt the patch that was done for webkit-gtk to allow
mips64el/mips64 usage: http://patches.openembedded.org/patch/51625/
> arm | qt5declarative-5.1.1 | NOK | http://autobuild.buildroot.net/results/82bb89d5b29dc6bd40f840bc04845b6c87157985/
Weird thing. It's having problems when building things for the host...
but it uses target headers when building for the host. Someone needs to
look closely into this. Fatih ? :-)
> mips64el | rpm-5.2.0 | NOK | http://autobuild.buildroot.net/results/bcff4b81bfbb1191f97317b0945c74d948c9774b/
checking whether to build with BeeCrypt library... no
configure: error: mandatory BeeCrypt library not found
make: *** [/home/test/test/3/output/build/rpm-5.2.0/.stamp_configured] Error 1
rpm has a dependency on beecrypt, so normally it should have been built
before. Seems like rpm isn't "seeing" that beecrypt is around :-)
> arm | schifra-0.0.1 | NOK | http://autobuild.buildroot.net/results/1ec3664f28492bf3da53dcbe8ceeb165bce8df6d/
Patch has been sent to fix this:
http://patchwork.ozlabs.org/patch/293270/. To be applied.
> arm | sdl_ttf-2.0.11 | NOK | http://autobuild.buildroot.net/results/f4ad0468f17520a645f029878876a972421a87b4/
OpenGL/libraries problem.
linux-gnueabi/sysroot/usr/lib
/home/test/test/2/output/host/opt/ext-toolchain/bin/../lib/gcc/arm-none-linux-gnueabi/4.7.3/../../../../arm-none-linux-gnueabi/bin/ld: warning: libXdamage.so.1, needed by /home/test/test/2/output/host/usr/arm-buildroot-linux-gnueabi/sysroot/usr/lib/libGL.so, not found (try using -rpath or -rpath-link)
/home/test/test/2/output/host/opt/ext-toolchain/bin/../lib/gcc/arm-none-linux-gnueabi/4.7.3/../../../../arm-none-linux-gnueabi/bin/ld: warning: libXfixes.so.3, needed by /home/test/test/2/output/host/usr/arm-buildroot-linux-gnueabi/sysroot/usr/lib/libGL.so, not found (try using -rpath or -rpath-link)
/home/test/test/2/output/host/opt/ext-toolchain/bin/../lib/gcc/arm-none-linux-gnueabi/4.7.3/../../../../arm-none-linux-gnueabi/bin/ld: warning: libXext.so.6, needed by /home/test/test/2/output/host/usr/arm-buildroot-linux-gnueabi/sysroot/usr/lib/libGL.so, not found (try using -rpath or -rpath-link)
/home/test/test/2/output/host/opt/ext-toolchain/bin/../lib/gcc/arm-none-linux-gnueabi/4.7.3/../../../../arm-none-linux-gnueabi/bin/ld: warning: libX11.so.6, needed by /home/test/test/2/output/host/usr/arm-buildroot-linux-gnueabi/sysroot/usr/lib/libGL.so, not found (try using -rpath or -rpath-link)
> arc | sqlite-3080002 | NOK | http://autobuild.buildroot.net/results/4f09bbb3cf646e7e45c86d43a50b440245e136e2/
ARC compiler problem. Fixed by the bump of the toolchain components for
ARC (patches already submitted by Mischa).
> mips64el | tinymembench-v0.2 | NOK | http://autobuild.buildroot.net/results/bab68bcf8714f215ac0b0c2546fa06608377fbb0/
Fixed by http://patchwork.ozlabs.org/patch/293207/.
> powerpc | toolchain-external-undefined | NOK | http://autobuild.buildroot.net/results/8fb291915b3ce5dc955f5e7e60eea2a4a6202143/
> arm | toolchain-external-undefined | NOK | http://autobuild.buildroot.net/results/cc4c41b99005c82e546a9e2916df97180be32b2b/
These are autobuilder script issues. Don't take them into account (even
though I indeed need to find a solution for these).
> powerpc | w_scan-20130331 | NOK | http://autobuild.buildroot.net/results/7ac90c6087640585a9afb0e31ad9e690eded89f5/
Too old kernel headers, but the toolchain is the latest PowerPC
toolchain from CodeSourcery.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
^ permalink raw reply [flat|nested] 16+ messages in thread
* [Buildroot] [autobuild.buildroot.net] Build results for 2013-11-21
2013-11-22 7:58 ` Espen Frimann Koren
@ 2013-11-22 8:22 ` Thomas Petazzoni
2013-12-23 13:09 ` Fatih Aşıcı
0 siblings, 1 reply; 16+ messages in thread
From: Thomas Petazzoni @ 2013-11-22 8:22 UTC (permalink / raw)
To: buildroot
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
^ permalink raw reply [flat|nested] 16+ messages in thread
* [Buildroot] Analysis of build failures
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
` (3 subsequent siblings)
4 siblings, 1 reply; 16+ messages in thread
From: Fabio Porcedda @ 2013-11-22 9:15 UTC (permalink / raw)
To: buildroot
Hi Thomas,
On Fri, Nov 22, 2013 at 9:14 AM, Thomas Petazzoni
<thomas.petazzoni@free-electrons.com> wrote:
> Hello,
>
> On Fri, 22 Nov 2013 08:30:02 +0100 (CET), Thomas Petazzoni wrote:
> ...
>> arm | lvm2-2.02.103 | NOK | http://autobuild.buildroot.net/results/b0b386969459dda9c294f1ccb4927ca225fa6bdd/
>
> Missing dependency?
>
> /home/test/test/1/output/host/usr/bin/arm-linux-gcc -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -pipe -Os -fPIC -O2 --static -O2 -L../libdm -L../lib -L../libdaemon/client -L../libdm \
> -o dmsetup dmsetup.o -ldevmapper
> /home/test/test/1/output/host/opt/ext-toolchain/bin/../lib/gcc/arm-buildroot-linux-uclibcgnueabi/4.7.3/../../../../arm-buildroot-linux-uclibcgnueabi/bin/ld: cannot find -ldevmapper
>
> ...
I will try to look into this.
Best regards
--
Fabio Porcedda
^ permalink raw reply [flat|nested] 16+ messages in thread
* [Buildroot] Analysis of build failures
2013-11-22 8:14 ` [Buildroot] Analysis of build failures Thomas Petazzoni
2013-11-22 9:15 ` Fabio Porcedda
@ 2013-11-22 10:42 ` Thomas De Schampheleire
2013-11-22 12:59 ` Thomas De Schampheleire
2013-11-22 11:56 ` Thomas Petazzoni
` (2 subsequent siblings)
4 siblings, 1 reply; 16+ messages in thread
From: Thomas De Schampheleire @ 2013-11-22 10:42 UTC (permalink / raw)
To: buildroot
Hi Thomas,
Thanks for the analysis!
On Fri, Nov 22, 2013 at 9:14 AM, Thomas Petazzoni
<thomas.petazzoni@free-electrons.com> wrote:
[..]
>> mips64el | rpm-5.2.0 | NOK | http://autobuild.buildroot.net/results/bcff4b81bfbb1191f97317b0945c74d948c9774b/
>
> checking whether to build with BeeCrypt library... no
> configure: error: mandatory BeeCrypt library not found
> make: *** [/home/test/test/3/output/build/rpm-5.2.0/.stamp_configured] Error 1
>
> rpm has a dependency on beecrypt, so normally it should have been built
> before. Seems like rpm isn't "seeing" that beecrypt is around :-)
I will look into this...
Best regards,
Thomas
^ permalink raw reply [flat|nested] 16+ messages in thread
* [Buildroot] Analysis of build failures
2013-11-22 8:14 ` [Buildroot] Analysis of build failures Thomas Petazzoni
2013-11-22 9:15 ` Fabio Porcedda
2013-11-22 10:42 ` Thomas De Schampheleire
@ 2013-11-22 11:56 ` Thomas Petazzoni
2013-11-22 11:58 ` Fatih Aşıcı
2013-11-22 15:20 ` Peter Korsgaard
4 siblings, 0 replies; 16+ messages in thread
From: Thomas Petazzoni @ 2013-11-22 11:56 UTC (permalink / raw)
To: buildroot
Dear Thomas Petazzoni,
On Fri, 22 Nov 2013 09:14:11 +0100, Thomas Petazzoni wrote:
> On Fri, 22 Nov 2013 08:30:02 +0100 (CET), Thomas Petazzoni wrote:
>
> > mipsel | alsa-lib-1.0.26 | NOK | http://autobuild.buildroot.net/results/417dac44eb077079f16a039881a45fa1b1782497/
> > mipsel | apr-1.4.8 | NOK | http://autobuild.buildroot.net/results/20926ed11e7d86cd6c54700eb609b3fa1740b8a7/
> > mipsel | attr-2.4.47 | NOK | http://autobuild.buildroot.net/results/03e5b85c71e5b624e42245f04d305042ec9136fa/
> > mipsel | bootutils-1.0.0 | NOK | http://autobuild.buildroot.net/results/a51b3723f176a98abff809313a5f863e2539e103/
>
> Those four ones are the same:
>
> configure: error: C compiler cannot create executables
>
> probably a toolchain configuration problem, I need to look into this.
Caused by the deprecation of mips 1, 2, 3 and 4. The toolchain used was
built for mips4, so when linked against code for mips32, it doesn't
work (because apparently, mips32 code isn't compatible with mips4 code).
So I've started rebuilding the set of toolchains on top of 2013.11-rc2,
by replacing the mips4 toolchain by a mips32 toolchain.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
^ permalink raw reply [flat|nested] 16+ messages in thread
* [Buildroot] Analysis of build failures
2013-11-22 8:14 ` [Buildroot] Analysis of build failures Thomas Petazzoni
` (2 preceding siblings ...)
2013-11-22 11:56 ` Thomas Petazzoni
@ 2013-11-22 11:58 ` Fatih Aşıcı
2013-11-22 12:13 ` Thomas Petazzoni
2013-11-22 15:20 ` Peter Korsgaard
4 siblings, 1 reply; 16+ messages in thread
From: Fatih Aşıcı @ 2013-11-22 11:58 UTC (permalink / raw)
To: buildroot
On Friday 22 November 2013 10:14:11 Thomas Petazzoni wrote:
> > arm | qt5declarative-5.1.1 | NOK |
> >http://autobuild.buildroot.net/results/82bb89d5b29dc6bd40f840bc04845b6c87
> >157985/
>
> Weird thing. It's having problems when building things for the host...
> but it uses target headers when building for the host. Someone needs to
> look closely into this. Fatih ? :-)
All those headers belong to Qt. Qt does not install headers into host prefix.
This might be intentional. It doesn't sound like a problem to me.
^ permalink raw reply [flat|nested] 16+ messages in thread
* [Buildroot] Analysis of build failures
2013-11-22 11:58 ` Fatih Aşıcı
@ 2013-11-22 12:13 ` Thomas Petazzoni
2013-11-23 23:07 ` Arnout Vandecappelle
0 siblings, 1 reply; 16+ messages in thread
From: Thomas Petazzoni @ 2013-11-22 12:13 UTC (permalink / raw)
To: buildroot
Dear Fatih A??c?,
On Fri, 22 Nov 2013 13:58:29 +0200, Fatih A??c? wrote:
> On Friday 22 November 2013 10:14:11 Thomas Petazzoni wrote:
> > > arm | qt5declarative-5.1.1 | NOK |
> > >http://autobuild.buildroot.net/results/82bb89d5b29dc6bd40f840bc04845b6c87
> > >157985/
> >
> > Weird thing. It's having problems when building things for the host...
> > but it uses target headers when building for the host. Someone needs to
> > look closely into this. Fatih ? :-)
>
> All those headers belong to Qt. Qt does not install headers into host prefix.
> This might be intentional. It doesn't sound like a problem to me.
It does to me. Headers correspond to libraries. And therefore, headers
installed in $(STAGING_DIR) match libraries installed in
$(STAGING_DIR), and so built for the target. Including headers from
$(STAGING_DIR) to build native tools seems wrong.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
^ permalink raw reply [flat|nested] 16+ messages in thread
* [Buildroot] Analysis of build failures
2013-11-22 10:42 ` Thomas De Schampheleire
@ 2013-11-22 12:59 ` Thomas De Schampheleire
2013-11-22 16:01 ` Arnout Vandecappelle
0 siblings, 1 reply; 16+ messages in thread
From: Thomas De Schampheleire @ 2013-11-22 12:59 UTC (permalink / raw)
To: buildroot
Hi,
On Fri, Nov 22, 2013 at 11:42 AM, Thomas De Schampheleire
<patrickdepinguin@gmail.com> wrote:
> Hi Thomas,
>
> Thanks for the analysis!
>
> On Fri, Nov 22, 2013 at 9:14 AM, Thomas Petazzoni
> <thomas.petazzoni@free-electrons.com> wrote:
> [..]
>>> mips64el | rpm-5.2.0 | NOK | http://autobuild.buildroot.net/results/bcff4b81bfbb1191f97317b0945c74d948c9774b/
>>
>> checking whether to build with BeeCrypt library... no
>> configure: error: mandatory BeeCrypt library not found
>> make: *** [/home/test/test/3/output/build/rpm-5.2.0/.stamp_configured] Error 1
>>
>> rpm has a dependency on beecrypt, so normally it should have been built
>> before. Seems like rpm isn't "seeing" that beecrypt is around :-)
>
> I will look into this...
The problem is that rpm uses beecrypt, and beecrypt depends on openmp
(libgomp), but the test in rpm does not include -lgomp.
I found a few references to this problem in older threads:
http://lists.busybox.net/pipermail/buildroot/2012-October/059839.html
http://lists.busybox.net/pipermail/buildroot/2012-November/061560.html
From these threads, there is a suggestion to disable openmp in
beecrypt (from you, ThomasP, actually). I haven't tried it yet, but it
sounds like this would solve the above autobuild problem.
Any input on this?
Thanks,
Thomas
^ permalink raw reply [flat|nested] 16+ messages in thread
* [Buildroot] Analysis of build failures
2013-11-22 8:14 ` [Buildroot] Analysis of build failures Thomas Petazzoni
` (3 preceding siblings ...)
2013-11-22 11:58 ` Fatih Aşıcı
@ 2013-11-22 15:20 ` Peter Korsgaard
4 siblings, 0 replies; 16+ messages in thread
From: Peter Korsgaard @ 2013-11-22 15:20 UTC (permalink / raw)
To: buildroot
>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@free-electrons.com> writes:
> A patch has been sent by Thomas DS to make libglib and all its reverse
> dependencies not available on !MMU. I believe it's the good way to go
> for now, until we have a proper patch to make libglib2 usable on !MMU
> systems. Peter, can you merge http://patchwork.ozlabs.org/patch/292839/ ?
Done.
>> avr32 | libroxml-2.2.3 | NOK | http://autobuild.buildroot.net/results/e22d94fca3eabb4e54d82af04319f17ad8e10c20/
> Simon Dawson has already sent a patch to fix this:
> http://patchwork.ozlabs.org/patch/293203/. Peter, can you merge this.
Done.
>> arm | libvncserver-0.9.9 | NOK | http://autobuild.buildroot.net/results/c3082693fe0da0c54d4bbf950dd6d74e1395c1d9/
> libvncserver needs thread support.
Ahh, I already tried fixing that in:
commit b6ee44b6d497f412b5b6c6223462a8a687c82af7
Author: Peter Korsgaard <peter@korsgaard.com>
Date: Wed Nov 13 09:07:41 2013 +0100
libvncserver: fix build without pthread
Fixes http://autobuild.buildroot.net/results/761/7618028d0781269d2f6f0a14d814da456f207475/
Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
But the openssl support in libvncclient apparently doesn't look at that
option. I'll take a closer look.
>> mips64el | qt-4.8.5 | NOK | http://autobuild.buildroot.net/results/fd7e7e53290f235b540ed5f3c784e2584fdb41e0/
> There is no support for mips64 in QtScript, which uses JavaScriptCore.
> Options are:
> * Disable the possibility of enabling QtScript on mips64el/mips64
> * Adapt the patch that was done for webkit-gtk to allow
> mips64el/mips64 usage: http://patches.openembedded.org/patch/51625/
The first approach seems simples/safest for 2013.11.
>> arm | schifra-0.0.1 | NOK | http://autobuild.buildroot.net/results/1ec3664f28492bf3da53dcbe8ceeb165bce8df6d/
> Patch has been sent to fix this:
> http://patchwork.ozlabs.org/patch/293270/. To be applied.
Done.
>> mips64el | tinymembench-v0.2 | NOK | http://autobuild.buildroot.net/results/bab68bcf8714f215ac0b0c2546fa06608377fbb0/
> Fixed by http://patchwork.ozlabs.org/patch/293207/.
Done.
--
Bye, Peter Korsgaard
^ permalink raw reply [flat|nested] 16+ messages in thread
* [Buildroot] Analysis of build failures
2013-11-22 12:59 ` Thomas De Schampheleire
@ 2013-11-22 16:01 ` Arnout Vandecappelle
2013-11-22 16:03 ` Thomas De Schampheleire
0 siblings, 1 reply; 16+ messages in thread
From: Arnout Vandecappelle @ 2013-11-22 16:01 UTC (permalink / raw)
To: buildroot
On 22/11/13 13:59, Thomas De Schampheleire wrote:
> Hi,
>
> On Fri, Nov 22, 2013 at 11:42 AM, Thomas De Schampheleire
> <patrickdepinguin@gmail.com> wrote:
>> Hi Thomas,
>>
>> Thanks for the analysis!
>>
>> On Fri, Nov 22, 2013 at 9:14 AM, Thomas Petazzoni
>> <thomas.petazzoni@free-electrons.com> wrote:
>> [..]
>>>> mips64el | rpm-5.2.0 | NOK | http://autobuild.buildroot.net/results/bcff4b81bfbb1191f97317b0945c74d948c9774b/
>>>
>>> checking whether to build with BeeCrypt library... no
>>> configure: error: mandatory BeeCrypt library not found
>>> make: *** [/home/test/test/3/output/build/rpm-5.2.0/.stamp_configured] Error 1
>>>
>>> rpm has a dependency on beecrypt, so normally it should have been built
>>> before. Seems like rpm isn't "seeing" that beecrypt is around :-)
>>
>> I will look into this...
>
> The problem is that rpm uses beecrypt, and beecrypt depends on openmp
> (libgomp), but the test in rpm does not include -lgomp.
>
> I found a few references to this problem in older threads:
> http://lists.busybox.net/pipermail/buildroot/2012-October/059839.html
> http://lists.busybox.net/pipermail/buildroot/2012-November/061560.html
>
> From these threads, there is a suggestion to disable openmp in
> beecrypt (from you, ThomasP, actually). I haven't tried it yet, but it
> sounds like this would solve the above autobuild problem.
>
> Any input on this?
I completely agree with the idea. Should be a matter of adding
--disable-openmp to BEECRYPT_CONF_OPT.
Regards,
Arnout
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
^ permalink raw reply [flat|nested] 16+ messages in thread
* [Buildroot] Analysis of build failures
2013-11-22 16:01 ` Arnout Vandecappelle
@ 2013-11-22 16:03 ` Thomas De Schampheleire
0 siblings, 0 replies; 16+ messages in thread
From: Thomas De Schampheleire @ 2013-11-22 16:03 UTC (permalink / raw)
To: buildroot
On Fri, Nov 22, 2013 at 5:01 PM, Arnout Vandecappelle <arnout@mind.be> wrote:
> On 22/11/13 13:59, Thomas De Schampheleire wrote:
>>
>> Hi,
>>
>> On Fri, Nov 22, 2013 at 11:42 AM, Thomas De Schampheleire
>> <patrickdepinguin@gmail.com> wrote:
>>>
>>> Hi Thomas,
>>>
>>> Thanks for the analysis!
>>>
>>> On Fri, Nov 22, 2013 at 9:14 AM, Thomas Petazzoni
>>> <thomas.petazzoni@free-electrons.com> wrote:
>>> [..]
>>>>>
>>>>> mips64el | rpm-5.2.0 | NOK |
>>>>> http://autobuild.buildroot.net/results/bcff4b81bfbb1191f97317b0945c74d948c9774b/
>>>>
>>>>
>>>> checking whether to build with BeeCrypt library... no
>>>> configure: error: mandatory BeeCrypt library not found
>>>> make: *** [/home/test/test/3/output/build/rpm-5.2.0/.stamp_configured]
>>>> Error 1
>>>>
>>>> rpm has a dependency on beecrypt, so normally it should have been built
>>>> before. Seems like rpm isn't "seeing" that beecrypt is around :-)
>>>
>>>
>>> I will look into this...
>>
>>
>> The problem is that rpm uses beecrypt, and beecrypt depends on openmp
>> (libgomp), but the test in rpm does not include -lgomp.
>>
>> I found a few references to this problem in older threads:
>> http://lists.busybox.net/pipermail/buildroot/2012-October/059839.html
>> http://lists.busybox.net/pipermail/buildroot/2012-November/061560.html
>>
>> From these threads, there is a suggestion to disable openmp in
>> beecrypt (from you, ThomasP, actually). I haven't tried it yet, but it
>> sounds like this would solve the above autobuild problem.
>>
>> Any input on this?
>
>
> I completely agree with the idea. Should be a matter of adding
> --disable-openmp to BEECRYPT_CONF_OPT.
>
I tried that and it works fine.
However, in the mean time Vicente sent another proposal (see other
thread), but I conclude from the threads above that it is not the
right patch...
Best regards,
Thomas
^ permalink raw reply [flat|nested] 16+ messages in thread
* [Buildroot] Analysis of build failures
2013-11-22 12:13 ` Thomas Petazzoni
@ 2013-11-23 23:07 ` Arnout Vandecappelle
0 siblings, 0 replies; 16+ messages in thread
From: Arnout Vandecappelle @ 2013-11-23 23:07 UTC (permalink / raw)
To: buildroot
On 22/11/13 13:13, Thomas Petazzoni wrote:
> Dear Fatih A??c?,
>
> On Fri, 22 Nov 2013 13:58:29 +0200, Fatih A??c? wrote:
>> On Friday 22 November 2013 10:14:11 Thomas Petazzoni wrote:
>>>> arm | qt5declarative-5.1.1 | NOK |
>>>> http://autobuild.buildroot.net/results/82bb89d5b29dc6bd40f840bc04845b6c87
>>>> 157985/
>>>
>>> Weird thing. It's having problems when building things for the host...
>>> but it uses target headers when building for the host. Someone needs to
>>> look closely into this. Fatih ? :-)
>>
>> All those headers belong to Qt. Qt does not install headers into host prefix.
>> This might be intentional. It doesn't sound like a problem to me.
>
> It does to me. Headers correspond to libraries. And therefore, headers
> installed in $(STAGING_DIR) match libraries installed in
> $(STAGING_DIR), and so built for the target. Including headers from
> $(STAGING_DIR) to build native tools seems wrong.
And just to prove that point: when the staging dir is removed from the
include path, that file compiles fine. That is, after symlinking the
QtCore directory to somewhere else in the include path, otherwise the Qt
includes can't be found. Another solution is to replace the -I with
-idirafter, so the system includes come first.
The reason that the staging dir has to be included is because that's
the only place where you can find the core Qt libraries.
The funny thing is that Qt is smart enough to link with the libraries
in host/usr/lib and install the executables in host/usr/bin...
Regards,
Arnout
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
^ permalink raw reply [flat|nested] 16+ messages in thread
* [Buildroot] Analysis of build failures
2013-11-22 9:15 ` Fabio Porcedda
@ 2013-11-29 10:25 ` Fabio Porcedda
0 siblings, 0 replies; 16+ messages in thread
From: Fabio Porcedda @ 2013-11-29 10:25 UTC (permalink / raw)
To: buildroot
On Fri, Nov 22, 2013 at 10:15 AM, Fabio Porcedda
<fabio.porcedda@gmail.com> wrote:
> Hi Thomas,
>
> On Fri, Nov 22, 2013 at 9:14 AM, Thomas Petazzoni
> <thomas.petazzoni@free-electrons.com> wrote:
>> Hello,
>>
>> On Fri, 22 Nov 2013 08:30:02 +0100 (CET), Thomas Petazzoni wrote:
>> ...
>>> arm | lvm2-2.02.103 | NOK | http://autobuild.buildroot.net/results/b0b386969459dda9c294f1ccb4927ca225fa6bdd/
>>
>> Missing dependency?
>>
>> /home/test/test/1/output/host/usr/bin/arm-linux-gcc -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -pipe -Os -fPIC -O2 --static -O2 -L../libdm -L../lib -L../libdaemon/client -L../libdm \
>> -o dmsetup dmsetup.o -ldevmapper
>> /home/test/test/1/output/host/opt/ext-toolchain/bin/../lib/gcc/arm-buildroot-linux-uclibcgnueabi/4.7.3/../../../../arm-buildroot-linux-uclibcgnueabi/bin/ld: cannot find -ldevmapper
>>
>> ...
>
> I will try to look into this.
The problem is still present on the master branch.
The minimal defconfig to reproduce the problem is:
BR2_PREFER_STATIC_LIB=y
BR2_TOOLCHAIN_BUILDROOT_LARGEFILE=y
BR2_PACKAGE_LVM2=y
The problem is related to "BR2_PREFER_STATIC_LIB=y" without that
option it builds fine.
Updating it to the latest available git version does not fix the issue.
I will try to investigate further.
Regards
--
Fabio Porcedda
^ permalink raw reply [flat|nested] 16+ messages in thread
* [Buildroot] [autobuild.buildroot.net] Build results for 2013-11-21
2013-11-22 8:22 ` Thomas Petazzoni
@ 2013-12-23 13:09 ` Fatih Aşıcı
0 siblings, 0 replies; 16+ messages in thread
From: Fatih Aşıcı @ 2013-12-23 13:09 UTC (permalink / raw)
To: buildroot
On Friday 22 November 2013 10:22:44 Thomas Petazzoni wrote:
> 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/inc
> lude -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/inc
> lude/QtXml
> -I/scratch/peko/host/usr/arm-buildroot-linux-uclibcgnueabi/sysroot/usr/inc
> lude/QtCore/5.1.1
> -I/scratch/peko/host/usr/arm-buildroot-linux-uclibcgnueabi/sysroot/usr/inc
> lude/QtCore/5.1.1/QtCore
> -I/scratch/peko/host/usr/arm-buildroot-linux-uclibcgnueabi/sysroot/usr/inc
> lude/QtXml/5.1.1
> -I/scratch/peko/host/usr/arm-buildroot-linux-uclibcgnueabi/sysroot/usr/inc
> lude/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
Putting qt headers into a subdirectory in /usr/include fixes the problem. See
the comments at https://bugreports.qt-project.org/browse/QTBUG-35330.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20131223/61971a31/attachment-0002.html>
^ permalink raw reply [flat|nested] 16+ messages in thread
end of thread, other threads:[~2013-12-23 13:09 UTC | newest]
Thread overview: 16+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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
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
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox