* [Buildroot] [autobuild.buildroot.net] Build results for 2016-01-15
@ 2016-01-16 7:30 Thomas Petazzoni
2016-01-16 23:11 ` [Buildroot] Analysis of build failures Thomas Petazzoni
0 siblings, 1 reply; 25+ messages in thread
From: Thomas Petazzoni @ 2016-01-16 7:30 UTC (permalink / raw)
To: buildroot
Build statistics for 2016-01-15
===============================
success : 206
failures : 136
timeouts : 3
TOTAL : 345
Classification of failures by reason
====================================
assimp-v3.2 | 23
boost-1.60.0 | 20
libffi-3.2.1 | 15
host-vboot-utils-bbdd62f9b0... | 7
luabitop-1.0.2-1 | 5
unknown | 4
qt-4.8.7 | 4
bind-9.10.3-P2 | 3
uboot-tools-2015.10 | 3
ruby-2.3.0 | 3
zbar-854a5d97059e395807091a... | 2
libnss-3.21 | 2
alsa-utils-1.1.0 | 2
gst1-plugins-bad-1.6.2 | 2
ltp-testsuite-20150903 | 2
ffmpeg-2.8.4 | 2
moarvm-2015.10 | 2
libcap-ng-0.7.4 | 2
util-linux-2.27.1 | 1
host-python3-3.4.3 | 1
hidapi-d17db57b9d4354752e0a... | 1
sconeserver-3b886c3dda6eda3... | 1
httping-2.4 | 1
trousers-0.3.13 | 1
mesa3d-11.1.0 | 1
nut-2.7.2 | 1
dvbsnoop-1.4.50 | 1
libdrm-2.4.66 | 1
linux-firmware-bbe4917c054e... | 1
faifa-v0.1 | 1
pinentry-0.9.4 | 1
imx-kobs-3.14.28-1.0.0 | 1
iputils-s20121011 | 1
opencv-2.4.10 | 1
flann-04b4a56533faf8c8228d0... | 1
ipsec-tools-0.8.2 | 1
rpm-5.2.0 | 1
make[3]: *** [code/CMakeFil... | 1
canfestival-7740ac6fdedc23e... | 1
erlang-17.5 | 1
vpnc-0.5.3 | 1
fxload-2008_10_13 | 1
nfs-utils-1.3.3 | 1
harfbuzz-1.1.3 | 1
code/CMakeFiles/assimp.dir/... | 1
openpgm-release-5-2-122 | 1
bluez5_utils-5.37 | 1
iprutils-2.4.5 | 1
tstools-08f6be304040e7b8476... | 1
rabbitmq-c-0.7.1 | 1
lighttpd-1.4.39 | 1
valgrind-3.11.0 | 1
chocolate-doom-2.2.1 | 1
sane-backends-1.0.25 | 1
Detail of failures
===================
xtensa | alsa-utils-1.1.0 | NOK | http://autobuild.buildroot.net/results/1bf954501960db802c3e2280b30b70d6813bdb32/
arm | alsa-utils-1.1.0 | NOK | http://autobuild.buildroot.net/results/7ba954e03822d758e25356935b0dfc2c91d3712a/
bfin | assimp-v3.2 | NOK | http://autobuild.buildroot.net/results/a5558d054ab19f078d0992f8b691f35f3f1323c0/
bfin | assimp-v3.2 | NOK | http://autobuild.buildroot.net/results/f0d25c8b08ba32361d47bd6bc344695f168396de/
bfin | assimp-v3.2 | NOK | http://autobuild.buildroot.net/results/3f143ea946ad98176d8e5eaddecfa0bda11c0439/
sparc64 | assimp-v3.2 | NOK | http://autobuild.buildroot.net/results/510c59e13f1412ffb831801e6389a32a76b543b6/
sparc | assimp-v3.2 | NOK | http://autobuild.buildroot.net/results/3f6f7a72bec601688991111f21e897306b1d76ca/
xtensa | assimp-v3.2 | NOK | http://autobuild.buildroot.net/results/5eab445d66a977cdfb73a6b5dede6af692c28b16/
xtensa | assimp-v3.2 | NOK | http://autobuild.buildroot.net/results/a511687d937c2575d8edffe9235b1507be1c9442/
bfin | assimp-v3.2 | NOK | http://autobuild.buildroot.net/results/eb659085949c6b62108b8c46c50e8abd01681f23/
bfin | assimp-v3.2 | NOK | http://autobuild.buildroot.net/results/4f3c001e8fa6781c4a2ca9d82023f959b7897035/
powerpc | assimp-v3.2 | NOK | http://autobuild.buildroot.net/results/5a90ba61c5ac863a7779af7783c7b0584a0c79e3/
powerpc | assimp-v3.2 | NOK | http://autobuild.buildroot.net/results/a70ec3a94a18db77f094c71d8be055ae0d99862b/
xtensa | assimp-v3.2 | NOK | http://autobuild.buildroot.net/results/c0a57f9a03c308dcf8129d300d12f4a7d6d999de/
powerpc | assimp-v3.2 | NOK | http://autobuild.buildroot.net/results/d37761e95f2f45e92ef641e7117ff6d02f2865d1/
xtensa | assimp-v3.2 | NOK | http://autobuild.buildroot.net/results/651efb92cd38569a1c53000c642b37a5c4b21115/
powerpc | assimp-v3.2 | NOK | http://autobuild.buildroot.net/results/498380d65b3e3d604a36facec894fc60a30a5d74/
mips | assimp-v3.2 | NOK | http://autobuild.buildroot.net/results/37ce98706477b259da4e9527878aeada2d52366c/
powerpc | assimp-v3.2 | NOK | http://autobuild.buildroot.net/results/686755f4f925811fccbdadbe28ba7561af8c51ad/
bfin | assimp-v3.2 | NOK | http://autobuild.buildroot.net/results/2f46b77f27ca7df9ae80ecaa6fdca6d981eeb8ff/
powerpc | assimp-v3.2 | NOK | http://autobuild.buildroot.net/results/7be9e4860ca47f8906c355577d71c0c6e8d597be/
powerpc | assimp-v3.2 | NOK | http://autobuild.buildroot.net/results/c0bc9693cfbac282599c73e7f0b6dd19e41bbfa3/
xtensa | assimp-v3.2 | NOK | http://autobuild.buildroot.net/results/23b6e683aa3db28d2103e47fd263dc9c5afd99b8/
xtensa | assimp-v3.2 | NOK | http://autobuild.buildroot.net/results/903515ab22c112dacf1583fff77c859c6f68985d/
powerpc | assimp-v3.2 | NOK | http://autobuild.buildroot.net/results/23e03277f61490b6f48035075df0fc5e5474168f/
mipsel | bind-9.10.3-P2 | NOK | http://autobuild.buildroot.net/results/c4f88c724829e1a2ff152c756ea3dae80fef149c/
mips64el | bind-9.10.3-P2 | NOK | http://autobuild.buildroot.net/results/870879c3d20dcfb327329fab0d8c13f320fd5788/
mipsel | bind-9.10.3-P2 | NOK | http://autobuild.buildroot.net/results/1d1889f407adce09f313e8660f8b660f256ea277/
arm | bluez5_utils-5.37 | NOK | http://autobuild.buildroot.net/results/83112559d84dc156141339a31e3e02f1a2af5155/
powerpc | boost-1.60.0 | NOK | http://autobuild.buildroot.net/results/e92fc7bac808e708e1aadd1b8e6677d003e5bbe4/
arm | boost-1.60.0 | NOK | http://autobuild.buildroot.net/results/46d0907fe06a7b93bb092ad4bf869a2e0030cf32/
x86_64 | boost-1.60.0 | NOK | http://autobuild.buildroot.net/results/9ef4d4f5d793f9a854d3a398d00eec6ce9b59178/
x86_64 | boost-1.60.0 | NOK | http://autobuild.buildroot.net/results/74e22545f50c9f9e7f12208a1cb9cbb9154a6150/
powerpc | boost-1.60.0 | NOK | http://autobuild.buildroot.net/results/5438729ded4bf9887a1dc080366aee9abf27fb19/
x86_64 | boost-1.60.0 | NOK | http://autobuild.buildroot.net/results/99ef4325d424569bbd900d6590b8a3a5e445c140/
arc | boost-1.60.0 | NOK | http://autobuild.buildroot.net/results/caded0b9ff89ba69cb3775d5fef18565a85a398a/
x86_64 | boost-1.60.0 | NOK | http://autobuild.buildroot.net/results/b81bcc845a091ff1182df7dec306492b67db10ea/
xtensa | boost-1.60.0 | NOK | http://autobuild.buildroot.net/results/29241cbf4791947e8bd990253716d8d43e219c23/
mips64el | boost-1.60.0 | NOK | http://autobuild.buildroot.net/results/648507a680fa0360622ad1fdd47fdf30d3c54091/
x86_64 | boost-1.60.0 | NOK | http://autobuild.buildroot.net/results/dea9364e8d8276bbcf42847822ef5da905cd7007/
x86_64 | boost-1.60.0 | NOK | http://autobuild.buildroot.net/results/adcea53d916e0825cb5963768304dfe883d5d379/
microblazeel | boost-1.60.0 | NOK | http://autobuild.buildroot.net/results/41ee80a733bc676d07d8296b262125b616070835/
xtensa | boost-1.60.0 | NOK | http://autobuild.buildroot.net/results/2c555d574540caf3a3b1ed64502274d3ba1f551b/
arc | boost-1.60.0 | NOK | http://autobuild.buildroot.net/results/316dc6221a50537234e4b3e88268363d61b9bf59/
arc | boost-1.60.0 | NOK | http://autobuild.buildroot.net/results/d4eb7cdbfd1152bb5a2a80f832c5edf524852701/
sh4 | boost-1.60.0 | NOK | http://autobuild.buildroot.net/results/3bb3e2b683eabe7a6a9626f083b761b158a418ba/
x86_64 | boost-1.60.0 | NOK | http://autobuild.buildroot.net/results/0e2f3f4e4fa9dca521206d52fc061709534be12b/
x86_64 | boost-1.60.0 | NOK | http://autobuild.buildroot.net/results/84f5d3417ef5cdb826435b0029ddc8d2e9e4ec44/
x86_64 | boost-1.60.0 | NOK | http://autobuild.buildroot.net/results/428cb84d3bde356050b04647a599aea0fae6aeff/
arm | canfestival-7740ac6fdedc23e... | NOK | http://autobuild.buildroot.net/results/5c5a48b050223d5f4f66a3a5ddde12cb17e310d7/
arm | chocolate-doom-2.2.1 | NOK | http://autobuild.buildroot.net/results/20019b0daebf1aaf44e0802603108ff712f60513/
microblazeel | code/CMakeFiles/assimp.dir/... | TIM | http://autobuild.buildroot.net/results/50b9c93c0ee080c42362fd6d210745446077d7f5/
arm | dvbsnoop-1.4.50 | NOK | http://autobuild.buildroot.net/results/2040d919e9d2564cf283ab815bea5ef34840ee61/
aarch64 | erlang-17.5 | NOK | http://autobuild.buildroot.net/results/0cd22eb74fa29e5a85bf897762e16ab3daf33962/
x86_64 | faifa-v0.1 | NOK | http://autobuild.buildroot.net/results/617e5635e0c508f82043f21886b6ce9a30549ad2/
mips64el | ffmpeg-2.8.4 | NOK | http://autobuild.buildroot.net/results/12ef8ee60b3c016e8998ff240a6dc51e682f3058/
mips64el | ffmpeg-2.8.4 | NOK | http://autobuild.buildroot.net/results/a964ce679fed3eaaebd0ee2f39639d8243e227ef/
microblazeel | flann-04b4a56533faf8c8228d0... | NOK | http://autobuild.buildroot.net/results/6126357850f15fb97828cd1b186e71ced83716eb/
microblazeel | fxload-2008_10_13 | NOK | http://autobuild.buildroot.net/results/4fa96981077c61599cc04b7c0f96b9f430f17f85/
i686 | gst1-plugins-bad-1.6.2 | NOK | http://autobuild.buildroot.net/results/fab7afc3490d77a6b29760394337298f2fd55d51/
x86_64 | gst1-plugins-bad-1.6.2 | NOK | http://autobuild.buildroot.net/results/4da1b0454fe7bf028a62058d28dafda104fb75f4/
sparc | harfbuzz-1.1.3 | NOK | http://autobuild.buildroot.net/results/30dec74537539dcbfa97eb9f90f40b2a814830d1/
aarch64 | hidapi-d17db57b9d4354752e0a... | NOK | http://autobuild.buildroot.net/results/7d70b7dac91209d1a63c131e9eb098bd8be3e84c/
powerpc | host-python3-3.4.3 | NOK | http://autobuild.buildroot.net/results/49d02998eeb5817d92574f61f6786a4f5c71d131/
nios2 | host-vboot-utils-bbdd62f9b0... | NOK | http://autobuild.buildroot.net/results/e8e730f90357fd9818d19ae48b7533c8c5dcbc49/
arm | host-vboot-utils-bbdd62f9b0... | NOK | http://autobuild.buildroot.net/results/3c673e550535d741d2773e359ed2bebaebad6ad2/
bfin | host-vboot-utils-bbdd62f9b0... | NOK | http://autobuild.buildroot.net/results/5d526c4348a0ab3d802a9ef795096b2bfd1b3515/
arm | host-vboot-utils-bbdd62f9b0... | NOK | http://autobuild.buildroot.net/results/e64262b0045195892b2c7ed08cfef8f5682b9793/
x86_64 | host-vboot-utils-bbdd62f9b0... | NOK | http://autobuild.buildroot.net/results/844424b9db5ced38f90936fdc96eba480de34459/
bfin | host-vboot-utils-bbdd62f9b0... | NOK | http://autobuild.buildroot.net/results/3ef4945e7c51f354eb4444fc40f50ba0e86929e9/
arc | host-vboot-utils-bbdd62f9b0... | NOK | http://autobuild.buildroot.net/results/cec1c9d0723d72693d526dcfc3e9432b7694911f/
arm | httping-2.4 | NOK | http://autobuild.buildroot.net/results/f88f0dd592a52128d250b2c8668a524d6ca35d24/
arm | imx-kobs-3.14.28-1.0.0 | NOK | http://autobuild.buildroot.net/results/05a159c7f8382237d4c941b1bb6de7dad72708f3/
arm | iprutils-2.4.5 | NOK | http://autobuild.buildroot.net/results/61e121c25fc07083bcccedfcb4f938d18f5c5456/
arm | ipsec-tools-0.8.2 | NOK | http://autobuild.buildroot.net/results/ce0bb96971147669c1bb253ce259eb5756f1d85e/
x86_64 | iputils-s20121011 | NOK | http://autobuild.buildroot.net/results/12cb73f3def95efe706bcd957bc2c091e7931d5a/
nios2 | libcap-ng-0.7.4 | NOK | http://autobuild.buildroot.net/results/ae9eca750d27f80cf8b0743f41cdfcc50ea476f1/
nios2 | libcap-ng-0.7.4 | NOK | http://autobuild.buildroot.net/results/dca1ba4a15cd9326a43e99d78bd13021bc87d9a2/
sparc | libdrm-2.4.66 | NOK | http://autobuild.buildroot.net/results/fa0ac44d3c7953b2e2afa03cd7570d8a5d49fcc4/
mips | libffi-3.2.1 | NOK | http://autobuild.buildroot.net/results/cf7fd3dc8a1373c6c963a83e55d093b945f90f1a/
mips64el | libffi-3.2.1 | NOK | http://autobuild.buildroot.net/results/a7dd03a12c06a1f01826f01f91b39af396dca0d8/
mips64el | libffi-3.2.1 | NOK | http://autobuild.buildroot.net/results/a39a87c6547c9daa27e8a257c9e573d4c222fca4/
mips | libffi-3.2.1 | NOK | http://autobuild.buildroot.net/results/f09b5d6120203cd5ddc60951828f880905297bcb/
mips | libffi-3.2.1 | NOK | http://autobuild.buildroot.net/results/108cdfac94e88bfdc318e0689295a3799cc23069/
mips64el | libffi-3.2.1 | NOK | http://autobuild.buildroot.net/results/c14cabcc51f6870a0ab2381b32220d944590669f/
mips64el | libffi-3.2.1 | NOK | http://autobuild.buildroot.net/results/f05e78f97928c5da48678cdf2e465d413fd5feca/
mips | libffi-3.2.1 | NOK | http://autobuild.buildroot.net/results/0094b3f30f8815fa5ef10afb3b0e506549ee8674/
mips64el | libffi-3.2.1 | NOK | http://autobuild.buildroot.net/results/4de0087f2bf63612c4354970d8307be7fa8beefd/
mips64el | libffi-3.2.1 | NOK | http://autobuild.buildroot.net/results/5d9f963a30eea53dd22f0b0d6f0d63592114977a/
mips64el | libffi-3.2.1 | NOK | http://autobuild.buildroot.net/results/0616fba52db8793ea5ac1383c47a86a72aae682f/
mips64el | libffi-3.2.1 | NOK | http://autobuild.buildroot.net/results/e2d5f87095f877c9ff7807419014e4af8b43130b/
mips | libffi-3.2.1 | NOK | http://autobuild.buildroot.net/results/4dc9605b801518aa8075972e46e83d4df98cdbb5/
mips64el | libffi-3.2.1 | NOK | http://autobuild.buildroot.net/results/26dd14f492e4a544400f2d2c6800ee5cde4a0b1f/
mips | libffi-3.2.1 | NOK | http://autobuild.buildroot.net/results/8c668a64b6b9ed4ba7a77c3d3211a41de89c33b6/
arm | libnss-3.21 | NOK | http://autobuild.buildroot.net/results/9ba9e0c148110b69763c12e37a37738deab3f118/
powerpc | libnss-3.21 | NOK | http://autobuild.buildroot.net/results/cef2fe3d87b742743a54a2fdbc585771e175a9e6/
i686 | lighttpd-1.4.39 | NOK | http://autobuild.buildroot.net/results/13faa9ebce00359b8943775364a432ce422fe8b8/
arm | linux-firmware-bbe4917c054e... | TIM | http://autobuild.buildroot.net/results/fc6001a9fcaeab2a67d03d5809360de00c16392a/
sparc | ltp-testsuite-20150903 | NOK | http://autobuild.buildroot.net/results/faa42138e2b5a07b965926e55b831cb6e8eb3c0c/
sparc64 | ltp-testsuite-20150903 | NOK | http://autobuild.buildroot.net/results/85e181c2f75037e0d9b9a7bd288d9fdaa828bb34/
arm | luabitop-1.0.2-1 | NOK | http://autobuild.buildroot.net/results/80d137d91e6f6173e29074cf12a38f192ce0d7ca/
xtensa | luabitop-1.0.2-1 | NOK | http://autobuild.buildroot.net/results/15a0e4c3879eb56604fa88c2e31be641e933afa7/
aarch64 | luabitop-1.0.2-1 | NOK | http://autobuild.buildroot.net/results/39d2bae1398bd17891a9d0d2f698340fc7dca591/
i686 | luabitop-1.0.2-1 | NOK | http://autobuild.buildroot.net/results/7ac0eb736ad264c59637059ce207989c392f00f7/
aarch64 | luabitop-1.0.2-1 | NOK | http://autobuild.buildroot.net/results/a95d9b6eee7b41a0ce4cf6456fde08291cd8b860/
microblazeel | make[3]: *** [code/CMakeFil... | TIM | http://autobuild.buildroot.net/results/8df9f0dd9cbc0446c0458d89cb182d0feb795774/
arc | mesa3d-11.1.0 | NOK | http://autobuild.buildroot.net/results/7b3f5c0e3c59bd49614e8ad4eee3d89e3527a939/
sparc64 | moarvm-2015.10 | NOK | http://autobuild.buildroot.net/results/268e328e2d9ea951c0728ab6031d32e2b460d015/
sparc64 | moarvm-2015.10 | NOK | http://autobuild.buildroot.net/results/84847a9201244fce3e05e5e4e201f2e1848238de/
powerpc | nfs-utils-1.3.3 | NOK | http://autobuild.buildroot.net/results/948f81d7ed2c080a675ee9fec754f6fda1fd905f/
arm | nut-2.7.2 | NOK | http://autobuild.buildroot.net/results/8fb9cb823d723903f11d70325b0ea09e103504cf/
sparc64 | opencv-2.4.10 | NOK | http://autobuild.buildroot.net/results/84cfdfa21205954cb8f0e5541332570ba5206add/
arm | openpgm-release-5-2-122 | NOK | http://autobuild.buildroot.net/results/aa2cf491dfb199a349afd107046f428107a583a0/
mipsel | pinentry-0.9.4 | NOK | http://autobuild.buildroot.net/results/d8d6414ae28d9ea84118dfa5c0f73d9334a1c417/
arc | qt-4.8.7 | NOK | http://autobuild.buildroot.net/results/a85a1839a45fb6102e53131ecc8f6dadf92bcdc2/
nios2 | qt-4.8.7 | NOK | http://autobuild.buildroot.net/results/199b8ed788e4ca3eca03b95710a3bb644d81d187/
nios2 | qt-4.8.7 | NOK | http://autobuild.buildroot.net/results/546f94ee09fcff27ea2d7c6cebb0b48aec1881f8/
nios2 | qt-4.8.7 | NOK | http://autobuild.buildroot.net/results/bb90227b6a18bde0cef45f82620de560d48866e7/
arm | rabbitmq-c-0.7.1 | NOK | http://autobuild.buildroot.net/results/2ef1ed958db8012224f9174334e9c58edace604a/
sh4 | rpm-5.2.0 | NOK | http://autobuild.buildroot.net/results/499f2a3204a6afab96322c431732541fefd622e8/
arc | ruby-2.3.0 | NOK | http://autobuild.buildroot.net/results/8e98934b066d4973d88e7d28b042b99550d68ae8/
powerpc | ruby-2.3.0 | NOK | http://autobuild.buildroot.net/results/d0a77147cba429bb42f102141810a23e831a8bcb/
arc | ruby-2.3.0 | NOK | http://autobuild.buildroot.net/results/748771df79b8537d3f4baeb1f7d423dec1f8c519/
arm | sane-backends-1.0.25 | NOK | http://autobuild.buildroot.net/results/9759238db294c0703e8c685f2adc41dba3fdb31f/
mips64el | sconeserver-3b886c3dda6eda3... | NOK | http://autobuild.buildroot.net/results/be8d1ad7c05b39f8ed65b86f938bc2d9530e3c6d/
arc | trousers-0.3.13 | NOK | http://autobuild.buildroot.net/results/c3d3bedffe0f4ba40f33d18e90a4802f4a7bfffb/
arm | tstools-08f6be304040e7b8476... | NOK | http://autobuild.buildroot.net/results/357de0b07b2104e0c94cb3d21ca2096df0796071/
xtensa | uboot-tools-2015.10 | NOK | http://autobuild.buildroot.net/results/64ac87a2a4847a45fc96cfaa4ded7f0821f66701/
xtensa | uboot-tools-2015.10 | NOK | http://autobuild.buildroot.net/results/9ebc5e3a6f1dd3ceb90d6786a1c5455c965f819e/
microblazeel | uboot-tools-2015.10 | NOK | http://autobuild.buildroot.net/results/a197f03c1751a87c7f71e057f2c4619538b4b6c8/
xtensa | unknown | NOK | http://autobuild.buildroot.net/results/f913556517654f833bf17f141597ba41570b02b7/
arm | unknown | NOK | http://autobuild.buildroot.net/results/865ce538e3dc3ce8005a39b5400fc3f019d7a411/
arm | unknown | NOK | http://autobuild.buildroot.net/results/0581889edfb7bf5ca0f23e3111ac6eeffbee3376/
mips64el | unknown | NOK | http://autobuild.buildroot.net/results/1abb03babacacf13db33ae9fe89b5d52925b58b1/
arm | util-linux-2.27.1 | NOK | http://autobuild.buildroot.net/results/2ca06e6bb9b147a44400e26acdd41dcc3ab7d9e4/
mips | valgrind-3.11.0 | NOK | http://autobuild.buildroot.net/results/a00f4856c4094508334477296d0ec203466fe56e/
arm | vpnc-0.5.3 | NOK | http://autobuild.buildroot.net/results/aacb5ae636e2ae2df67a91696b1d2af276777b22/
nios2 | zbar-854a5d97059e395807091a... | NOK | http://autobuild.buildroot.net/results/d4a9e291ad1b36bd268b4b850aa10be3ac00b6d9/
arm | zbar-854a5d97059e395807091a... | NOK | http://autobuild.buildroot.net/results/c9cdee9e5cd031e5927b7aa26d92c48dbe35c1e7/
--
http://autobuild.buildroot.net
^ permalink raw reply [flat|nested] 25+ messages in thread
* [Buildroot] Analysis of build failures
2016-01-16 7:30 [Buildroot] [autobuild.buildroot.net] Build results for 2016-01-15 Thomas Petazzoni
@ 2016-01-16 23:11 ` Thomas Petazzoni
2016-01-17 1:42 ` Frank Hunleth
` (10 more replies)
0 siblings, 11 replies; 25+ messages in thread
From: Thomas Petazzoni @ 2016-01-16 23:11 UTC (permalink / raw)
To: buildroot
Hello,
Gustavo, Vicente, J?rg, Frank, Bernd, Maxime, Carsten, Davide, Jeremy,
VIcente, Gilles, Gary, Romain, Matt, Waldemar, Fran?ois, Alexey, Joris,
Volkov: there are some specific build failures for which your help
would be appreciated. See below. Thanks in advance for your help!
On Sat, 16 Jan 2016 08:30:21 +0100 (CET), Thomas Petazzoni wrote:
> xtensa | alsa-utils-1.1.0 | NOK | http://autobuild.buildroot.net/results/1bf954501960db802c3e2280b30b70d6813bdb32/
> arm | alsa-utils-1.1.0 | NOK | http://autobuild.buildroot.net/results/7ba954e03822d758e25356935b0dfc2c91d3712a/
<dlfcn.h> needed by the topology code. Fixed in
https://git.busybox.net/buildroot/commit/?id=4707383c5d501a9ad7698579e5d0a4e2ab758c7e.
> bfin | assimp-v3.2 | NOK | http://autobuild.buildroot.net/results/a5558d054ab19f078d0992f8b691f35f3f1323c0/
Compiler error, in FLAT mode. Not sure what's going on, as I was able
to build assimp properly in a minimal Blackfin FLAT configuration.
> bfin | assimp-v3.2 | NOK | http://autobuild.buildroot.net/results/f0d25c8b08ba32361d47bd6bc344695f168396de/
> bfin | assimp-v3.2 | NOK | http://autobuild.buildroot.net/results/3f143ea946ad98176d8e5eaddecfa0bda11c0439/
> sparc64 | assimp-v3.2 | NOK | http://autobuild.buildroot.net/results/510c59e13f1412ffb831801e6389a32a76b543b6/
> sparc | assimp-v3.2 | NOK | http://autobuild.buildroot.net/results/3f6f7a72bec601688991111f21e897306b1d76ca/
> xtensa | assimp-v3.2 | NOK | http://autobuild.buildroot.net/results/5eab445d66a977cdfb73a6b5dede6af692c28b16/
> xtensa | assimp-v3.2 | NOK | http://autobuild.buildroot.net/results/a511687d937c2575d8edffe9235b1507be1c9442/
> bfin | assimp-v3.2 | NOK | http://autobuild.buildroot.net/results/eb659085949c6b62108b8c46c50e8abd01681f23/
> bfin | assimp-v3.2 | NOK | http://autobuild.buildroot.net/results/4f3c001e8fa6781c4a2ca9d82023f959b7897035/
> powerpc | assimp-v3.2 | NOK | http://autobuild.buildroot.net/results/5a90ba61c5ac863a7779af7783c7b0584a0c79e3/
> powerpc | assimp-v3.2 | NOK | http://autobuild.buildroot.net/results/a70ec3a94a18db77f094c71d8be055ae0d99862b/
> xtensa | assimp-v3.2 | NOK | http://autobuild.buildroot.net/results/c0a57f9a03c308dcf8129d300d12f4a7d6d999de/
> powerpc | assimp-v3.2 | NOK | http://autobuild.buildroot.net/results/d37761e95f2f45e92ef641e7117ff6d02f2865d1/
> xtensa | assimp-v3.2 | NOK | http://autobuild.buildroot.net/results/651efb92cd38569a1c53000c642b37a5c4b21115/
> powerpc | assimp-v3.2 | NOK | http://autobuild.buildroot.net/results/498380d65b3e3d604a36facec894fc60a30a5d74/
> mips | assimp-v3.2 | NOK | http://autobuild.buildroot.net/results/37ce98706477b259da4e9527878aeada2d52366c/
> powerpc | assimp-v3.2 | NOK | http://autobuild.buildroot.net/results/686755f4f925811fccbdadbe28ba7561af8c51ad/
> bfin | assimp-v3.2 | NOK | http://autobuild.buildroot.net/results/2f46b77f27ca7df9ae80ecaa6fdca6d981eeb8ff/
> powerpc | assimp-v3.2 | NOK | http://autobuild.buildroot.net/results/7be9e4860ca47f8906c355577d71c0c6e8d597be/
> powerpc | assimp-v3.2 | NOK | http://autobuild.buildroot.net/results/c0bc9693cfbac282599c73e7f0b6dd19e41bbfa3/
> xtensa | assimp-v3.2 | NOK | http://autobuild.buildroot.net/results/23b6e683aa3db28d2103e47fd263dc9c5afd99b8/
> xtensa | assimp-v3.2 | NOK | http://autobuild.buildroot.net/results/903515ab22c112dacf1583fff77c859c6f68985d/
> powerpc | assimp-v3.2 | NOK | http://autobuild.buildroot.net/results/23e03277f61490b6f48035075df0fc5e5474168f/
I guess most if not all of these are fixed by
https://git.busybox.net/buildroot/commit/?id=25ba49518a93265ecb3146e6eb21a2a138989100
and
https://git.busybox.net/buildroot/commit/?id=9ebac3bd050ee57cdd8a5ede053aed5522f5e8dc.
> mipsel | bind-9.10.3-P2 | NOK | http://autobuild.buildroot.net/results/c4f88c724829e1a2ff152c756ea3dae80fef149c/
> mips64el | bind-9.10.3-P2 | NOK | http://autobuild.buildroot.net/results/870879c3d20dcfb327329fab0d8c13f320fd5788/
> mipsel | bind-9.10.3-P2 | NOK | http://autobuild.buildroot.net/results/1d1889f407adce09f313e8660f8b660f256ea277/
Vicente, Gustavo, can you have a look at those issues? It seems to be
limited to MIPS, and I don't think it was happening before the recent
bump of the bind package.
> arm | bluez5_utils-5.37 | NOK | http://autobuild.buildroot.net/results/83112559d84dc156141339a31e3e02f1a2af5155/
Fixed by
https://git.busybox.net/buildroot/commit/?id=d7c54cb0c0cf8cb013d88ad3c2989ec323323235.
> powerpc | boost-1.60.0 | NOK | http://autobuild.buildroot.net/results/e92fc7bac808e708e1aadd1b8e6677d003e5bbe4/
> arm | boost-1.60.0 | NOK | http://autobuild.buildroot.net/results/46d0907fe06a7b93bb092ad4bf869a2e0030cf32/
> x86_64 | boost-1.60.0 | NOK | http://autobuild.buildroot.net/results/9ef4d4f5d793f9a854d3a398d00eec6ce9b59178/
> x86_64 | boost-1.60.0 | NOK | http://autobuild.buildroot.net/results/74e22545f50c9f9e7f12208a1cb9cbb9154a6150/
> powerpc | boost-1.60.0 | NOK | http://autobuild.buildroot.net/results/5438729ded4bf9887a1dc080366aee9abf27fb19/
> x86_64 | boost-1.60.0 | NOK | http://autobuild.buildroot.net/results/99ef4325d424569bbd900d6590b8a3a5e445c140/
> arc | boost-1.60.0 | NOK | http://autobuild.buildroot.net/results/caded0b9ff89ba69cb3775d5fef18565a85a398a/
> x86_64 | boost-1.60.0 | NOK | http://autobuild.buildroot.net/results/b81bcc845a091ff1182df7dec306492b67db10ea/
> xtensa | boost-1.60.0 | NOK | http://autobuild.buildroot.net/results/29241cbf4791947e8bd990253716d8d43e219c23/
> mips64el | boost-1.60.0 | NOK | http://autobuild.buildroot.net/results/648507a680fa0360622ad1fdd47fdf30d3c54091/
> x86_64 | boost-1.60.0 | NOK | http://autobuild.buildroot.net/results/dea9364e8d8276bbcf42847822ef5da905cd7007/
> x86_64 | boost-1.60.0 | NOK | http://autobuild.buildroot.net/results/adcea53d916e0825cb5963768304dfe883d5d379/
> microblazeel | boost-1.60.0 | NOK | http://autobuild.buildroot.net/results/41ee80a733bc676d07d8296b262125b616070835/
> xtensa | boost-1.60.0 | NOK | http://autobuild.buildroot.net/results/2c555d574540caf3a3b1ed64502274d3ba1f551b/
> arc | boost-1.60.0 | NOK | http://autobuild.buildroot.net/results/316dc6221a50537234e4b3e88268363d61b9bf59/
> arc | boost-1.60.0 | NOK | http://autobuild.buildroot.net/results/d4eb7cdbfd1152bb5a2a80f832c5edf524852701/
> sh4 | boost-1.60.0 | NOK | http://autobuild.buildroot.net/results/3bb3e2b683eabe7a6a9626f083b761b158a418ba/
> x86_64 | boost-1.60.0 | NOK | http://autobuild.buildroot.net/results/0e2f3f4e4fa9dca521206d52fc061709534be12b/
> x86_64 | boost-1.60.0 | NOK | http://autobuild.buildroot.net/results/84f5d3417ef5cdb826435b0029ddc8d2e9e4ec44/
> x86_64 | boost-1.60.0 | NOK | http://autobuild.buildroot.net/results/428cb84d3bde356050b04647a599aea0fae6aeff/
Some of these are the isnan() declaration issue, which is now fixed
thanks to
https://git.busybox.net/buildroot/commit/?id=640b75c8d73d713c908d6b288802c9e6bffe76ed.
However, there is still the FE_* definition problem. J?rg, do you have
something in the works to fix this ?
> arm | canfestival-7740ac6fdedc23e... | NOK | http://autobuild.buildroot.net/results/5c5a48b050223d5f4f66a3a5ddde12cb17e310d7/
musl build issue. There was a thread in August between Yann and Brendan
about this. I pinged the thread.
> arm | chocolate-doom-2.2.1 | NOK | http://autobuild.buildroot.net/results/20019b0daebf1aaf44e0802603108ff712f60513/
In static linking configurations, when SDL_mixer is linked against
libmad, chocolate-doom doesn't pass -lmad. To fix this, we need to:
* Fix SDL_mixer.pc so that it references libmad in Libs.private (or
Requires.private ?)
* Either use pkg-config directly in chocolate-doom.mk to pass the
appropriate flags, or change the chocolate-doom build system itself.
Note that a similar problem might appear when SDL_mixer is linked
against vorbis.
Rodrigo, since you added the chocolate-doom package, can you look into
fixing this ?
> microblazeel | code/CMakeFiles/assimp.dir/... | TIM | http://autobuild.buildroot.net/results/50b9c93c0ee080c42362fd6d210745446077d7f5/
Don't care.
> arm | dvbsnoop-1.4.50 | NOK | http://autobuild.buildroot.net/results/2040d919e9d2564cf283ab815bea5ef34840ee61/
musl build issue. Carsten, you added this package back in 2013, can you
have a look ?
> aarch64 | erlang-17.5 | NOK | http://autobuild.buildroot.net/results/0cd22eb74fa29e5a85bf897762e16ab3daf33962/
Build problem due to atomic intrinsics:
more undefined references to `__atomic_store_16' follow
Frank, can you investigate why it builds on x86_64 but not on aarch64 ?
> x86_64 | faifa-v0.1 | NOK | http://autobuild.buildroot.net/results/617e5635e0c508f82043f21886b6ce9a30549ad2/
Classical musl build issue. Maxime, you added this package, so can you
fix it ? :-)
> mips64el | ffmpeg-2.8.4 | NOK | http://autobuild.buildroot.net/results/12ef8ee60b3c016e8998ff240a6dc51e682f3058/
> mips64el | ffmpeg-2.8.4 | NOK | http://autobuild.buildroot.net/results/a964ce679fed3eaaebd0ee2f39639d8243e227ef/
ERROR: fontconfig not found using pkg-config
Bernd, Vicente ?
> microblazeel | flann-04b4a56533faf8c8228d0... | NOK | http://autobuild.buildroot.net/results/6126357850f15fb97828cd1b186e71ced83716eb/
internal compiler error: in gen_reg_rtx, at emit-rtl.c:838
To be tested with the latest gcc version, and potentially report a gcc
bug.
Davide, you added this package back in 2014. Can you have a look ?
> microblazeel | fxload-2008_10_13 | NOK | http://autobuild.buildroot.net/results/4fa96981077c61599cc04b7c0f96b9f430f17f85/
Binutils issue this time:
/tmp/ccQKhnE1.s: Assembler messages:
/tmp/ccQKhnE1.s: Error: PC relative branch to label logerror which is not in the instruction space
/tmp/ccQKhnE1.s: Error: PC relative branch to label logerror which is not in the instruction space
Same deal: test with the latest binutils version, and report a bug if
the problem still exists.
Jeremy, you added the fxload package, can you have a look ?
> i686 | gst1-plugins-bad-1.6.2 | NOK | http://autobuild.buildroot.net/results/fab7afc3490d77a6b29760394337298f2fd55d51/
> x86_64 | gst1-plugins-bad-1.6.2 | NOK | http://autobuild.buildroot.net/results/4da1b0454fe7bf028a62058d28dafda104fb75f4/
gstdvbsrc.c: In function 'gst_dvbsrc_code_rate_get_type':
gstdvbsrc.c:273:6: error: 'FEC_2_5' undeclared (first use in this function)
gstdvbsrc.c:273:6: note: each undeclared identifier is reported only once for each function it appears in
gstdvbsrc.c: In function 'gst_dvbsrc_modulation_get_type':
gstdvbsrc.c:303:6: error: 'QAM_4_NR' undeclared (first use in this function)
gstdvbsrc.c:303:5: error: initializer element is not constant
gstdvbsrc.c:303:5: error: (near initialization for 'modulation_types[13].value')
Not sure. Peter, Gustavo ?
> sparc | harfbuzz-1.1.3 | NOK | http://autobuild.buildroot.net/results/30dec74537539dcbfa97eb9f90f40b2a814830d1/
hb-warning.cc:32:2: error: #error "Could not find any system to define atomic_int macros, library WILL NOT be thread-safe"
#error "Could not find any system to define atomic_int macros, library WILL NOT be thread-safe"
^
hb-warning.cc:33:2: error: #error "Check hb-atomic-private.hh for possible resolutions."
#error "Check hb-atomic-private.hh for possible resolutions."
Gustavo, maybe we simply should disable this package on Sparc ? Only
annoyance is that it is selected by Pango, which means that all reverse
dependencies of Pango would have to be fixed :-/
Another idea ?
> aarch64 | hidapi-d17db57b9d4354752e0a... | NOK | http://autobuild.buildroot.net/results/7d70b7dac91209d1a63c131e9eb098bd8be3e84c/
make[3]: *** No rule to make target `hidtest.o', needed by `hidtest-libusb'. Stop.
Vicente, you added this package, can you have a look ?
> powerpc | host-python3-3.4.3 | NOK | http://autobuild.buildroot.net/results/49d02998eeb5817d92574f61f6786a4f5c71d131/
Modules/getbuildinfo.o: file not recognized: File truncated
collect2: error: ld returned 1 exit status
Ooch, smells like a parallel build issue... but building Python with
make -j1 would really be horrible :-/
> nios2 | host-vboot-utils-bbdd62f9b0... | NOK | http://autobuild.buildroot.net/results/e8e730f90357fd9818d19ae48b7533c8c5dcbc49/
> arm | host-vboot-utils-bbdd62f9b0... | NOK | http://autobuild.buildroot.net/results/3c673e550535d741d2773e359ed2bebaebad6ad2/
> bfin | host-vboot-utils-bbdd62f9b0... | NOK | http://autobuild.buildroot.net/results/5d526c4348a0ab3d802a9ef795096b2bfd1b3515/
> arm | host-vboot-utils-bbdd62f9b0... | NOK | http://autobuild.buildroot.net/results/e64262b0045195892b2c7ed08cfef8f5682b9793/
> x86_64 | host-vboot-utils-bbdd62f9b0... | NOK | http://autobuild.buildroot.net/results/844424b9db5ced38f90936fdc96eba480de34459/
> bfin | host-vboot-utils-bbdd62f9b0... | NOK | http://autobuild.buildroot.net/results/3ef4945e7c51f354eb4444fc40f50ba0e86929e9/
> arc | host-vboot-utils-bbdd62f9b0... | NOK | http://autobuild.buildroot.net/results/cec1c9d0723d72693d526dcfc3e9432b7694911f/
Issue specific to this autobuilder instance, I'll have a look at this
one.
> arm | httping-2.4 | NOK | http://autobuild.buildroot.net/results/f88f0dd592a52128d250b2c8668a524d6ca35d24/
Improper libintl handling. Gustavo, you bumped this package last year,
can you have a look ?
> arm | imx-kobs-3.14.28-1.0.0 | NOK | http://autobuild.buildroot.net/results/05a159c7f8382237d4c941b1bb6de7dad72708f3/
Gary, can you have a look ?
> arm | iprutils-2.4.5 | NOK | http://autobuild.buildroot.net/results/61e121c25fc07083bcccedfcb4f938d18f5c5456/
Musl build issue:
iprlib.h:49:27: fatal error: bits/sockaddr.h: No such file or directory
#include <bits/sockaddr.h>
Romain, you bumped this package recently, can you have a look ?
> arm | ipsec-tools-0.8.2 | NOK | http://autobuild.buildroot.net/results/ce0bb96971147669c1bb253ce259eb5756f1d85e/
Musl build issue. Gustavo, can you have a look ?
> x86_64 | iputils-s20121011 | NOK | http://autobuild.buildroot.net/results/12cb73f3def95efe706bcd957bc2c091e7931d5a/
Musl build issue. Matt, can you have a look ?
> nios2 | libcap-ng-0.7.4 | NOK | http://autobuild.buildroot.net/results/ae9eca750d27f80cf8b0743f41cdfcc50ea476f1/
> nios2 | libcap-ng-0.7.4 | NOK | http://autobuild.buildroot.net/results/dca1ba4a15cd9326a43e99d78bd13021bc87d9a2/
Romain, I don't remember what was the conclusion about this issue. I
remember we discussed it at some point.
> sparc | libdrm-2.4.66 | NOK | http://autobuild.buildroot.net/results/fa0ac44d3c7953b2e2afa03cd7570d8a5d49fcc4/
Waldemar, this is a sparc problem, can you look into it ?
> mips | libffi-3.2.1 | NOK | http://autobuild.buildroot.net/results/cf7fd3dc8a1373c6c963a83e55d093b945f90f1a/
> mips64el | libffi-3.2.1 | NOK | http://autobuild.buildroot.net/results/a7dd03a12c06a1f01826f01f91b39af396dca0d8/
> mips64el | libffi-3.2.1 | NOK | http://autobuild.buildroot.net/results/a39a87c6547c9daa27e8a257c9e573d4c222fca4/
> mips | libffi-3.2.1 | NOK | http://autobuild.buildroot.net/results/f09b5d6120203cd5ddc60951828f880905297bcb/
> mips | libffi-3.2.1 | NOK | http://autobuild.buildroot.net/results/108cdfac94e88bfdc318e0689295a3799cc23069/
> mips64el | libffi-3.2.1 | NOK | http://autobuild.buildroot.net/results/c14cabcc51f6870a0ab2381b32220d944590669f/
> mips64el | libffi-3.2.1 | NOK | http://autobuild.buildroot.net/results/f05e78f97928c5da48678cdf2e465d413fd5feca/
> mips | libffi-3.2.1 | NOK | http://autobuild.buildroot.net/results/0094b3f30f8815fa5ef10afb3b0e506549ee8674/
> mips64el | libffi-3.2.1 | NOK | http://autobuild.buildroot.net/results/4de0087f2bf63612c4354970d8307be7fa8beefd/
> mips64el | libffi-3.2.1 | NOK | http://autobuild.buildroot.net/results/5d9f963a30eea53dd22f0b0d6f0d63592114977a/
> mips64el | libffi-3.2.1 | NOK | http://autobuild.buildroot.net/results/0616fba52db8793ea5ac1383c47a86a72aae682f/
> mips64el | libffi-3.2.1 | NOK | http://autobuild.buildroot.net/results/e2d5f87095f877c9ff7807419014e4af8b43130b/
> mips | libffi-3.2.1 | NOK | http://autobuild.buildroot.net/results/4dc9605b801518aa8075972e46e83d4df98cdbb5/
> mips64el | libffi-3.2.1 | NOK | http://autobuild.buildroot.net/results/26dd14f492e4a544400f2d2c6800ee5cde4a0b1f/
> mips | libffi-3.2.1 | NOK | http://autobuild.buildroot.net/results/8c668a64b6b9ed4ba7a77c3d3211a41de89c33b6/
Vicente, we really need to solve this problem :)
> arm | libnss-3.21 | NOK | http://autobuild.buildroot.net/results/9ba9e0c148110b69763c12e37a37738deab3f118/
/home/buildroot/autobuild/run/instance-1/output/host/usr/arm-buildroot-linux-musleabihf/sysroot/usr/lib/libnspr4.so: undefined reference to `getprotobyname_r'
/home/buildroot/autobuild/run/instance-1/output/host/usr/arm-buildroot-linux-musleabihf/sysroot/usr/lib/libnspr4.so: undefined reference to `getprotobynumber_r'
Musl build issue.
> powerpc | libnss-3.21 | NOK | http://autobuild.buildroot.net/results/cef2fe3d87b742743a54a2fdbc585771e175a9e6/
In file included from secoid.c:1915:0:
verref.h: In function 'SECOID_Init':
verref.h:22:9: error: #pragma GCC diagnostic not allowed inside functions
verref.h:23:9: error: #pragma GCC diagnostic not allowed inside functions
cc1: warnings being treated as errors
old compiler problem.
> i686 | lighttpd-1.4.39 | NOK | http://autobuild.buildroot.net/results/13faa9ebce00359b8943775364a432ce422fe8b8/
mod_magnet.c: In function 'magnet_status_set':
mod_magnet.c:415:2: warning: implicit declaration of function 'luaL_checkint' [-Wimplicit-function-declaration]
mod_magnet.c: In function 'magnet_copy_response_header':
mod_magnet.c:692:2: warning: implicit declaration of function 'lua_getfenv' [-Wimplicit-function-declaration]
mod_magnet.c: In function 'traceback':
mod_magnet.c:839:18: error: 'LUA_GLOBALSINDEX' undeclared (first use in this function)
mod_magnet.c:839:18: note: each undeclared identifier is reported only once for each function it appears in
mod_magnet.c: In function 'magnet_attract':
mod_magnet.c:987:19: error: 'LUA_GLOBALSINDEX' undeclared (first use in this function)
mod_magnet.c:992:2: warning: implicit declaration of function 'lua_setfenv' [-Wimplicit-function-declaration]
Fran?ois, this seems to be Lua related, can you have a look ?
> arm | linux-firmware-bbe4917c054e... | TIM | http://autobuild.buildroot.net/results/fc6001a9fcaeab2a67d03d5809360de00c16392a/
Ignore.
> sparc | ltp-testsuite-20150903 | NOK | http://autobuild.buildroot.net/results/faa42138e2b5a07b965926e55b831cb6e8eb3c0c/
`undefined__sig_stub 'reference
> sparc64 | ltp-testsuite-20150903 | NOK | http://autobuild.buildroot.net/results/85e181c2f75037e0d9b9a7bd288d9fdaa828bb34/
undefined toreference `to__rt_sig_stub '`
Waldemar, can you have a look ?
> arm | luabitop-1.0.2-1 | NOK | http://autobuild.buildroot.net/results/80d137d91e6f6173e29074cf12a38f192ce0d7ca/
> xtensa | luabitop-1.0.2-1 | NOK | http://autobuild.buildroot.net/results/15a0e4c3879eb56604fa88c2e31be641e933afa7/
> aarch64 | luabitop-1.0.2-1 | NOK | http://autobuild.buildroot.net/results/39d2bae1398bd17891a9d0d2f698340fc7dca591/
> i686 | luabitop-1.0.2-1 | NOK | http://autobuild.buildroot.net/results/7ac0eb736ad264c59637059ce207989c392f00f7/
> aarch64 | luabitop-1.0.2-1 | NOK | http://autobuild.buildroot.net/results/a95d9b6eee7b41a0ce4cf6456fde08291cd8b860/
Fixed by https://git.busybox.net/buildroot/commit/?id=be5d265220f36df7e0b633fcc55e3a33b2e74035
> microblazeel | make[3]: *** [code/CMakeFil... | TIM | http://autobuild.buildroot.net/results/8df9f0dd9cbc0446c0458d89cb182d0feb795774/
Ignore.
> arc | mesa3d-11.1.0 | NOK | http://autobuild.buildroot.net/results/7b3f5c0e3c59bd49614e8ad4eee3d89e3527a939/
Compiler problem, issue is known by Synopsys.
> sparc64 | moarvm-2015.10 | NOK | http://autobuild.buildroot.net/results/268e328e2d9ea951c0728ab6031d32e2b460d015/
> sparc64 | moarvm-2015.10 | NOK | http://autobuild.buildroot.net/results/84847a9201244fce3e05e5e4e201f2e1848238de/
./libmoar.so: undefined reference to `AO_fetch_compare_and_swap_full'
Waldemar, can you have a look ?
> powerpc | nfs-utils-1.3.3 | NOK | http://autobuild.buildroot.net/results/948f81d7ed2c080a675ee9fec754f6fda1fd905f/
Not sure:
cache.c: In function 'same_path':
cache.c:429:22: error: field 'fh' has incomplete type
cache.c:436:2: warning: implicit declaration of function 'name_to_handle_at' [-Wimplicit-function-declaration]
Makefile:613: recipe for target 'mountd-cache.o' failed
Maxime, can you have a look ?
> arm | nut-2.7.2 | NOK | http://autobuild.buildroot.net/results/8fb9cb823d723903f11d70325b0ea09e103504cf/
checking whether to build SNMP drivers... yes
configure: error: "neon libraries not found, required for neon based XML/HTTP driver"
Most likely a static linking problem.
Yann, you added the nut package, so ... :-)
> sparc64 | opencv-2.4.10 | NOK | http://autobuild.buildroot.net/results/84cfdfa21205954cb8f0e5541332570ba5206add/
Another atomic related problem. Waldemar ?
> arm | openpgm-release-5-2-122 | NOK | http://autobuild.buildroot.net/results/aa2cf491dfb199a349afd107046f428107a583a0/
Musl build issue:
./include/pgm/gsi.h:47:75: error: unknown type name 'ssize_t'
bool pgm_gsi_create_from_string (pgm_gsi_t*restrict, const char*restrict, ssize_t);
Anyone to look into this?
> mipsel | pinentry-0.9.4 | NOK | http://autobuild.buildroot.net/results/d8d6414ae28d9ea84118dfa5c0f73d9334a1c417/
error: member 'QChar std::__cxx11::basic_string<QChar, std::char_traits<QChar>, secmem::alloc<QChar> >::<anonymous union>::_M_local_buf [8]' with constructor not allowed in union
_CharT _M_local_buf[_S_local_capacity + 1];
Anyone understands this ?
> arc | qt-4.8.7 | NOK | http://autobuild.buildroot.net/results/a85a1839a45fb6102e53131ecc8f6dadf92bcdc2/
Static linking, I'm assuming this *could* be fixed by
https://git.busybox.net/buildroot/commit/?id=12009bb92931b153823110f811632540044d3b02,
though I am not sure. Alexey ?a
> nios2 | qt-4.8.7 | NOK | http://autobuild.buildroot.net/results/199b8ed788e4ca3eca03b95710a3bb644d81d187/
> nios2 | qt-4.8.7 | NOK | http://autobuild.buildroot.net/results/546f94ee09fcff27ea2d7c6cebb0b48aec1881f8/
> nios2 | qt-4.8.7 | NOK | http://autobuild.buildroot.net/results/bb90227b6a18bde0cef45f82620de560d48866e7/
Compiler problem. I don't remember if I reported it.
> arm | rabbitmq-c-0.7.1 | NOK | http://autobuild.buildroot.net/results/2ef1ed958db8012224f9174334e9c58edace604a/
Static linking problem. Joris, can you have a look ?
> sh4 | rpm-5.2.0 | NOK | http://autobuild.buildroot.net/results/499f2a3204a6afab96322c431732541fefd622e8/
Internal compiler error...
> arc | ruby-2.3.0 | NOK | http://autobuild.buildroot.net/results/8e98934b066d4973d88e7d28b042b99550d68ae8/
Compiler issue:
/tmp/cctdImle.s: Assembler messages:
/tmp/cctdImle.s:2253: Error: invalid register number `63'
/tmp/cctdImle.s:2255: Error: invalid register number `63'
Alexey ?
> powerpc | ruby-2.3.0 | NOK | http://autobuild.buildroot.net/results/d0a77147cba429bb42f102141810a23e831a8bcb/
Compiler issue:
eval.c: In function 'rb_protect':
eval.c:881:1: internal compiler error: in move_insn, at haifa-sched.c:3439
> arc | ruby-2.3.0 | NOK | http://autobuild.buildroot.net/results/748771df79b8537d3f4baeb1f7d423dec1f8c519/
Same ARC compiler issue as above.
> arm | sane-backends-1.0.25 | NOK | http://autobuild.buildroot.net/results/9759238db294c0703e8c685f2adc41dba3fdb31f/
../backend/.libs/libsane.a(libepsonds_la-epsonds.o):(.bss+0x10): multiple definition of `source_list'
../backend/.libs/libsane.a(libepson2_la-epson2.o):(.data+0x40): first defined here
../backend/.libs/libsane.a(libepsonds_la-epsonds.o):(.data+0x10): multiple definition of `mode_params'
../backend/.libs/libsane.a(libepson2_la-epson2.o):(.data+0x0): first defined here
Vicente, you bumped sane-backends recently, can you have a look ?
> mips64el | sconeserver-3b886c3dda6eda3... | NOK | http://autobuild.buildroot.net/results/be8d1ad7c05b39f8ed65b86f938bc2d9530e3c6d/
Static linking issue, most likely:
checking for mysql_init in -lmysqlclient... no
configure: error: library 'mysqlclient' is required for the mysql module
Anyone interested ?
> arc | trousers-0.3.13 | NOK | http://autobuild.buildroot.net/results/c3d3bedffe0f4ba40f33d18e90a4802f4a7bfffb/
PIE problem, under discussion.
> arm | tstools-08f6be304040e7b8476... | NOK | http://autobuild.buildroot.net/results/357de0b07b2104e0c94cb3d21ca2096df0796071/
Tries to build a shared library, in a static linking scenario. Anyone ?
> xtensa | uboot-tools-2015.10 | NOK | http://autobuild.buildroot.net/results/64ac87a2a4847a45fc96cfaa4ded7f0821f66701/
> xtensa | uboot-tools-2015.10 | NOK | http://autobuild.buildroot.net/results/9ebc5e3a6f1dd3ceb90d6786a1c5455c965f819e/
> microblazeel | uboot-tools-2015.10 | NOK | http://autobuild.buildroot.net/results/a197f03c1751a87c7f71e057f2c4619538b4b6c8/
Patch pending to fix this.
> xtensa | unknown | NOK | http://autobuild.buildroot.net/results/f913556517654f833bf17f141597ba41570b02b7/
> arm | unknown | NOK | http://autobuild.buildroot.net/results/865ce538e3dc3ce8005a39b5400fc3f019d7a411/
> arm | unknown | NOK | http://autobuild.buildroot.net/results/0581889edfb7bf5ca0f23e3111ac6eeffbee3376/
> mips64el | unknown | NOK | http://autobuild.buildroot.net/results/1abb03babacacf13db33ae9fe89b5d52925b58b1/
2 different dependency problems.
> arm | util-linux-2.27.1 | NOK | http://autobuild.buildroot.net/results/2ca06e6bb9b147a44400e26acdd41dcc3ab7d9e4/
checking for prlimit... no
configure: error: flock selected, but required timer_create function not available
Static linking issue. Anyone ?
> mips | valgrind-3.11.0 | NOK | http://autobuild.buildroot.net/results/a00f4856c4094508334477296d0ec203466fe56e/
Vicente, this one is for you :)
> arm | vpnc-0.5.3 | NOK | http://autobuild.buildroot.net/results/aacb5ae636e2ae2df67a91696b1d2af276777b22/
Yet another static linking issue caused by libintl.
> nios2 | zbar-854a5d97059e395807091a... | NOK | http://autobuild.buildroot.net/results/d4a9e291ad1b36bd268b4b850aa10be3ac00b6d9/
> arm | zbar-854a5d97059e395807091a... | NOK | http://autobuild.buildroot.net/results/c9cdee9e5cd031e5927b7aa26d92c48dbe35c1e7/
Really bogus code triggers a warning that is now an error. Volkov, you
added the zbar package, can you have a look ?
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
^ permalink raw reply [flat|nested] 25+ messages in thread
* [Buildroot] Analysis of build failures
2016-01-16 23:11 ` [Buildroot] Analysis of build failures Thomas Petazzoni
@ 2016-01-17 1:42 ` Frank Hunleth
2016-01-17 11:23 ` Thomas Petazzoni
2016-01-17 15:06 ` Matthew Weber
` (9 subsequent siblings)
10 siblings, 1 reply; 25+ messages in thread
From: Frank Hunleth @ 2016-01-17 1:42 UTC (permalink / raw)
To: buildroot
Hi Thomas,
On Sat, Jan 16, 2016 at 6:11 PM, Thomas Petazzoni
<thomas.petazzoni@free-electrons.com> wrote:
> Hello,
>
> Gustavo, Vicente, J?rg, Frank, Bernd, Maxime, Carsten, Davide, Jeremy,
> VIcente, Gilles, Gary, Romain, Matt, Waldemar, Fran?ois, Alexey, Joris,
> Volkov: there are some specific build failures for which your help
> would be appreciated. See below. Thanks in advance for your help!
>
> On Sat, 16 Jan 2016 08:30:21 +0100 (CET), Thomas Petazzoni wrote:
>
>> xtensa | alsa-utils-1.1.0 | NOK | http://autobuild.buildroot.net/results/1bf954501960db802c3e2280b30b70d6813bdb32/
>> arm | alsa-utils-1.1.0 | NOK | http://autobuild.buildroot.net/results/7ba954e03822d758e25356935b0dfc2c91d3712a/
>
> <dlfcn.h> needed by the topology code. Fixed in
> https://git.busybox.net/buildroot/commit/?id=4707383c5d501a9ad7698579e5d0a4e2ab758c7e.
>
>> bfin | assimp-v3.2 | NOK | http://autobuild.buildroot.net/results/a5558d054ab19f078d0992f8b691f35f3f1323c0/
>
> Compiler error, in FLAT mode. Not sure what's going on, as I was able
> to build assimp properly in a minimal Blackfin FLAT configuration.
>
>> bfin | assimp-v3.2 | NOK | http://autobuild.buildroot.net/results/f0d25c8b08ba32361d47bd6bc344695f168396de/
>> bfin | assimp-v3.2 | NOK | http://autobuild.buildroot.net/results/3f143ea946ad98176d8e5eaddecfa0bda11c0439/
>> sparc64 | assimp-v3.2 | NOK | http://autobuild.buildroot.net/results/510c59e13f1412ffb831801e6389a32a76b543b6/
>> sparc | assimp-v3.2 | NOK | http://autobuild.buildroot.net/results/3f6f7a72bec601688991111f21e897306b1d76ca/
>> xtensa | assimp-v3.2 | NOK | http://autobuild.buildroot.net/results/5eab445d66a977cdfb73a6b5dede6af692c28b16/
>> xtensa | assimp-v3.2 | NOK | http://autobuild.buildroot.net/results/a511687d937c2575d8edffe9235b1507be1c9442/
>> bfin | assimp-v3.2 | NOK | http://autobuild.buildroot.net/results/eb659085949c6b62108b8c46c50e8abd01681f23/
>> bfin | assimp-v3.2 | NOK | http://autobuild.buildroot.net/results/4f3c001e8fa6781c4a2ca9d82023f959b7897035/
>> powerpc | assimp-v3.2 | NOK | http://autobuild.buildroot.net/results/5a90ba61c5ac863a7779af7783c7b0584a0c79e3/
>> powerpc | assimp-v3.2 | NOK | http://autobuild.buildroot.net/results/a70ec3a94a18db77f094c71d8be055ae0d99862b/
>> xtensa | assimp-v3.2 | NOK | http://autobuild.buildroot.net/results/c0a57f9a03c308dcf8129d300d12f4a7d6d999de/
>> powerpc | assimp-v3.2 | NOK | http://autobuild.buildroot.net/results/d37761e95f2f45e92ef641e7117ff6d02f2865d1/
>> xtensa | assimp-v3.2 | NOK | http://autobuild.buildroot.net/results/651efb92cd38569a1c53000c642b37a5c4b21115/
>> powerpc | assimp-v3.2 | NOK | http://autobuild.buildroot.net/results/498380d65b3e3d604a36facec894fc60a30a5d74/
>> mips | assimp-v3.2 | NOK | http://autobuild.buildroot.net/results/37ce98706477b259da4e9527878aeada2d52366c/
>> powerpc | assimp-v3.2 | NOK | http://autobuild.buildroot.net/results/686755f4f925811fccbdadbe28ba7561af8c51ad/
>> bfin | assimp-v3.2 | NOK | http://autobuild.buildroot.net/results/2f46b77f27ca7df9ae80ecaa6fdca6d981eeb8ff/
>> powerpc | assimp-v3.2 | NOK | http://autobuild.buildroot.net/results/7be9e4860ca47f8906c355577d71c0c6e8d597be/
>> powerpc | assimp-v3.2 | NOK | http://autobuild.buildroot.net/results/c0bc9693cfbac282599c73e7f0b6dd19e41bbfa3/
>> xtensa | assimp-v3.2 | NOK | http://autobuild.buildroot.net/results/23b6e683aa3db28d2103e47fd263dc9c5afd99b8/
>> xtensa | assimp-v3.2 | NOK | http://autobuild.buildroot.net/results/903515ab22c112dacf1583fff77c859c6f68985d/
>> powerpc | assimp-v3.2 | NOK | http://autobuild.buildroot.net/results/23e03277f61490b6f48035075df0fc5e5474168f/
>
> I guess most if not all of these are fixed by
> https://git.busybox.net/buildroot/commit/?id=25ba49518a93265ecb3146e6eb21a2a138989100
> and
> https://git.busybox.net/buildroot/commit/?id=9ebac3bd050ee57cdd8a5ede053aed5522f5e8dc.
>
>> mipsel | bind-9.10.3-P2 | NOK | http://autobuild.buildroot.net/results/c4f88c724829e1a2ff152c756ea3dae80fef149c/
>> mips64el | bind-9.10.3-P2 | NOK | http://autobuild.buildroot.net/results/870879c3d20dcfb327329fab0d8c13f320fd5788/
>> mipsel | bind-9.10.3-P2 | NOK | http://autobuild.buildroot.net/results/1d1889f407adce09f313e8660f8b660f256ea277/
>
> Vicente, Gustavo, can you have a look at those issues? It seems to be
> limited to MIPS, and I don't think it was happening before the recent
> bump of the bind package.
>
>> arm | bluez5_utils-5.37 | NOK | http://autobuild.buildroot.net/results/83112559d84dc156141339a31e3e02f1a2af5155/
>
> Fixed by
> https://git.busybox.net/buildroot/commit/?id=d7c54cb0c0cf8cb013d88ad3c2989ec323323235.
>
>> powerpc | boost-1.60.0 | NOK | http://autobuild.buildroot.net/results/e92fc7bac808e708e1aadd1b8e6677d003e5bbe4/
>> arm | boost-1.60.0 | NOK | http://autobuild.buildroot.net/results/46d0907fe06a7b93bb092ad4bf869a2e0030cf32/
>> x86_64 | boost-1.60.0 | NOK | http://autobuild.buildroot.net/results/9ef4d4f5d793f9a854d3a398d00eec6ce9b59178/
>> x86_64 | boost-1.60.0 | NOK | http://autobuild.buildroot.net/results/74e22545f50c9f9e7f12208a1cb9cbb9154a6150/
>> powerpc | boost-1.60.0 | NOK | http://autobuild.buildroot.net/results/5438729ded4bf9887a1dc080366aee9abf27fb19/
>> x86_64 | boost-1.60.0 | NOK | http://autobuild.buildroot.net/results/99ef4325d424569bbd900d6590b8a3a5e445c140/
>> arc | boost-1.60.0 | NOK | http://autobuild.buildroot.net/results/caded0b9ff89ba69cb3775d5fef18565a85a398a/
>> x86_64 | boost-1.60.0 | NOK | http://autobuild.buildroot.net/results/b81bcc845a091ff1182df7dec306492b67db10ea/
>> xtensa | boost-1.60.0 | NOK | http://autobuild.buildroot.net/results/29241cbf4791947e8bd990253716d8d43e219c23/
>> mips64el | boost-1.60.0 | NOK | http://autobuild.buildroot.net/results/648507a680fa0360622ad1fdd47fdf30d3c54091/
>> x86_64 | boost-1.60.0 | NOK | http://autobuild.buildroot.net/results/dea9364e8d8276bbcf42847822ef5da905cd7007/
>> x86_64 | boost-1.60.0 | NOK | http://autobuild.buildroot.net/results/adcea53d916e0825cb5963768304dfe883d5d379/
>> microblazeel | boost-1.60.0 | NOK | http://autobuild.buildroot.net/results/41ee80a733bc676d07d8296b262125b616070835/
>> xtensa | boost-1.60.0 | NOK | http://autobuild.buildroot.net/results/2c555d574540caf3a3b1ed64502274d3ba1f551b/
>> arc | boost-1.60.0 | NOK | http://autobuild.buildroot.net/results/316dc6221a50537234e4b3e88268363d61b9bf59/
>> arc | boost-1.60.0 | NOK | http://autobuild.buildroot.net/results/d4eb7cdbfd1152bb5a2a80f832c5edf524852701/
>> sh4 | boost-1.60.0 | NOK | http://autobuild.buildroot.net/results/3bb3e2b683eabe7a6a9626f083b761b158a418ba/
>> x86_64 | boost-1.60.0 | NOK | http://autobuild.buildroot.net/results/0e2f3f4e4fa9dca521206d52fc061709534be12b/
>> x86_64 | boost-1.60.0 | NOK | http://autobuild.buildroot.net/results/84f5d3417ef5cdb826435b0029ddc8d2e9e4ec44/
>> x86_64 | boost-1.60.0 | NOK | http://autobuild.buildroot.net/results/428cb84d3bde356050b04647a599aea0fae6aeff/
>
> Some of these are the isnan() declaration issue, which is now fixed
> thanks to
> https://git.busybox.net/buildroot/commit/?id=640b75c8d73d713c908d6b288802c9e6bffe76ed.
>
> However, there is still the FE_* definition problem. J?rg, do you have
> something in the works to fix this ?
>
>> arm | canfestival-7740ac6fdedc23e... | NOK | http://autobuild.buildroot.net/results/5c5a48b050223d5f4f66a3a5ddde12cb17e310d7/
>
> musl build issue. There was a thread in August between Yann and Brendan
> about this. I pinged the thread.
>
>> arm | chocolate-doom-2.2.1 | NOK | http://autobuild.buildroot.net/results/20019b0daebf1aaf44e0802603108ff712f60513/
>
> In static linking configurations, when SDL_mixer is linked against
> libmad, chocolate-doom doesn't pass -lmad. To fix this, we need to:
>
> * Fix SDL_mixer.pc so that it references libmad in Libs.private (or
> Requires.private ?)
>
> * Either use pkg-config directly in chocolate-doom.mk to pass the
> appropriate flags, or change the chocolate-doom build system itself.
>
> Note that a similar problem might appear when SDL_mixer is linked
> against vorbis.
>
> Rodrigo, since you added the chocolate-doom package, can you look into
> fixing this ?
>
>> microblazeel | code/CMakeFiles/assimp.dir/... | TIM | http://autobuild.buildroot.net/results/50b9c93c0ee080c42362fd6d210745446077d7f5/
>
> Don't care.
>
>> arm | dvbsnoop-1.4.50 | NOK | http://autobuild.buildroot.net/results/2040d919e9d2564cf283ab815bea5ef34840ee61/
>
> musl build issue. Carsten, you added this package back in 2013, can you
> have a look ?
>
>> aarch64 | erlang-17.5 | NOK | http://autobuild.buildroot.net/results/0cd22eb74fa29e5a85bf897762e16ab3daf33962/
>
> Build problem due to atomic intrinsics:
>
> more undefined references to `__atomic_store_16' follow
>
> Frank, can you investigate why it builds on x86_64 but not on aarch64 ?
I looked into this a little. My suspicion is that the atomic intrinsic
macros in the Erlang code have not been ported to aarch64, but I'm
having trouble following the code. I've inquired on the Erlang mailing
list and will report back.
Regards,
Frank
>
>> x86_64 | faifa-v0.1 | NOK | http://autobuild.buildroot.net/results/617e5635e0c508f82043f21886b6ce9a30549ad2/
>
> Classical musl build issue. Maxime, you added this package, so can you
> fix it ? :-)
>
>> mips64el | ffmpeg-2.8.4 | NOK | http://autobuild.buildroot.net/results/12ef8ee60b3c016e8998ff240a6dc51e682f3058/
>> mips64el | ffmpeg-2.8.4 | NOK | http://autobuild.buildroot.net/results/a964ce679fed3eaaebd0ee2f39639d8243e227ef/
>
> ERROR: fontconfig not found using pkg-config
>
> Bernd, Vicente ?
>
>> microblazeel | flann-04b4a56533faf8c8228d0... | NOK | http://autobuild.buildroot.net/results/6126357850f15fb97828cd1b186e71ced83716eb/
>
> internal compiler error: in gen_reg_rtx, at emit-rtl.c:838
>
> To be tested with the latest gcc version, and potentially report a gcc
> bug.
>
> Davide, you added this package back in 2014. Can you have a look ?
>
>> microblazeel | fxload-2008_10_13 | NOK | http://autobuild.buildroot.net/results/4fa96981077c61599cc04b7c0f96b9f430f17f85/
>
> Binutils issue this time:
>
> /tmp/ccQKhnE1.s: Assembler messages:
> /tmp/ccQKhnE1.s: Error: PC relative branch to label logerror which is not in the instruction space
> /tmp/ccQKhnE1.s: Error: PC relative branch to label logerror which is not in the instruction space
>
> Same deal: test with the latest binutils version, and report a bug if
> the problem still exists.
>
> Jeremy, you added the fxload package, can you have a look ?
>
>
>> i686 | gst1-plugins-bad-1.6.2 | NOK | http://autobuild.buildroot.net/results/fab7afc3490d77a6b29760394337298f2fd55d51/
>> x86_64 | gst1-plugins-bad-1.6.2 | NOK | http://autobuild.buildroot.net/results/4da1b0454fe7bf028a62058d28dafda104fb75f4/
>
> gstdvbsrc.c: In function 'gst_dvbsrc_code_rate_get_type':
> gstdvbsrc.c:273:6: error: 'FEC_2_5' undeclared (first use in this function)
> gstdvbsrc.c:273:6: note: each undeclared identifier is reported only once for each function it appears in
> gstdvbsrc.c: In function 'gst_dvbsrc_modulation_get_type':
> gstdvbsrc.c:303:6: error: 'QAM_4_NR' undeclared (first use in this function)
> gstdvbsrc.c:303:5: error: initializer element is not constant
> gstdvbsrc.c:303:5: error: (near initialization for 'modulation_types[13].value')
>
> Not sure. Peter, Gustavo ?
>
>> sparc | harfbuzz-1.1.3 | NOK | http://autobuild.buildroot.net/results/30dec74537539dcbfa97eb9f90f40b2a814830d1/
>
> hb-warning.cc:32:2: error: #error "Could not find any system to define atomic_int macros, library WILL NOT be thread-safe"
> #error "Could not find any system to define atomic_int macros, library WILL NOT be thread-safe"
> ^
> hb-warning.cc:33:2: error: #error "Check hb-atomic-private.hh for possible resolutions."
> #error "Check hb-atomic-private.hh for possible resolutions."
>
> Gustavo, maybe we simply should disable this package on Sparc ? Only
> annoyance is that it is selected by Pango, which means that all reverse
> dependencies of Pango would have to be fixed :-/
>
> Another idea ?
>
>> aarch64 | hidapi-d17db57b9d4354752e0a... | NOK | http://autobuild.buildroot.net/results/7d70b7dac91209d1a63c131e9eb098bd8be3e84c/
>
> make[3]: *** No rule to make target `hidtest.o', needed by `hidtest-libusb'. Stop.
>
> Vicente, you added this package, can you have a look ?
>
>> powerpc | host-python3-3.4.3 | NOK | http://autobuild.buildroot.net/results/49d02998eeb5817d92574f61f6786a4f5c71d131/
>
> Modules/getbuildinfo.o: file not recognized: File truncated
> collect2: error: ld returned 1 exit status
>
> Ooch, smells like a parallel build issue... but building Python with
> make -j1 would really be horrible :-/
>
>> nios2 | host-vboot-utils-bbdd62f9b0... | NOK | http://autobuild.buildroot.net/results/e8e730f90357fd9818d19ae48b7533c8c5dcbc49/
>> arm | host-vboot-utils-bbdd62f9b0... | NOK | http://autobuild.buildroot.net/results/3c673e550535d741d2773e359ed2bebaebad6ad2/
>> bfin | host-vboot-utils-bbdd62f9b0... | NOK | http://autobuild.buildroot.net/results/5d526c4348a0ab3d802a9ef795096b2bfd1b3515/
>> arm | host-vboot-utils-bbdd62f9b0... | NOK | http://autobuild.buildroot.net/results/e64262b0045195892b2c7ed08cfef8f5682b9793/
>> x86_64 | host-vboot-utils-bbdd62f9b0... | NOK | http://autobuild.buildroot.net/results/844424b9db5ced38f90936fdc96eba480de34459/
>> bfin | host-vboot-utils-bbdd62f9b0... | NOK | http://autobuild.buildroot.net/results/3ef4945e7c51f354eb4444fc40f50ba0e86929e9/
>> arc | host-vboot-utils-bbdd62f9b0... | NOK | http://autobuild.buildroot.net/results/cec1c9d0723d72693d526dcfc3e9432b7694911f/
>
> Issue specific to this autobuilder instance, I'll have a look at this
> one.
>
>> arm | httping-2.4 | NOK | http://autobuild.buildroot.net/results/f88f0dd592a52128d250b2c8668a524d6ca35d24/
>
> Improper libintl handling. Gustavo, you bumped this package last year,
> can you have a look ?
>
>> arm | imx-kobs-3.14.28-1.0.0 | NOK | http://autobuild.buildroot.net/results/05a159c7f8382237d4c941b1bb6de7dad72708f3/
>
> Gary, can you have a look ?
>
>> arm | iprutils-2.4.5 | NOK | http://autobuild.buildroot.net/results/61e121c25fc07083bcccedfcb4f938d18f5c5456/
>
> Musl build issue:
>
> iprlib.h:49:27: fatal error: bits/sockaddr.h: No such file or directory
> #include <bits/sockaddr.h>
>
> Romain, you bumped this package recently, can you have a look ?
>
>> arm | ipsec-tools-0.8.2 | NOK | http://autobuild.buildroot.net/results/ce0bb96971147669c1bb253ce259eb5756f1d85e/
>
> Musl build issue. Gustavo, can you have a look ?
>
>> x86_64 | iputils-s20121011 | NOK | http://autobuild.buildroot.net/results/12cb73f3def95efe706bcd957bc2c091e7931d5a/
>
> Musl build issue. Matt, can you have a look ?
>
>> nios2 | libcap-ng-0.7.4 | NOK | http://autobuild.buildroot.net/results/ae9eca750d27f80cf8b0743f41cdfcc50ea476f1/
>> nios2 | libcap-ng-0.7.4 | NOK | http://autobuild.buildroot.net/results/dca1ba4a15cd9326a43e99d78bd13021bc87d9a2/
>
> Romain, I don't remember what was the conclusion about this issue. I
> remember we discussed it at some point.
>
>> sparc | libdrm-2.4.66 | NOK | http://autobuild.buildroot.net/results/fa0ac44d3c7953b2e2afa03cd7570d8a5d49fcc4/
>
> Waldemar, this is a sparc problem, can you look into it ?
>
>> mips | libffi-3.2.1 | NOK | http://autobuild.buildroot.net/results/cf7fd3dc8a1373c6c963a83e55d093b945f90f1a/
>> mips64el | libffi-3.2.1 | NOK | http://autobuild.buildroot.net/results/a7dd03a12c06a1f01826f01f91b39af396dca0d8/
>> mips64el | libffi-3.2.1 | NOK | http://autobuild.buildroot.net/results/a39a87c6547c9daa27e8a257c9e573d4c222fca4/
>> mips | libffi-3.2.1 | NOK | http://autobuild.buildroot.net/results/f09b5d6120203cd5ddc60951828f880905297bcb/
>> mips | libffi-3.2.1 | NOK | http://autobuild.buildroot.net/results/108cdfac94e88bfdc318e0689295a3799cc23069/
>> mips64el | libffi-3.2.1 | NOK | http://autobuild.buildroot.net/results/c14cabcc51f6870a0ab2381b32220d944590669f/
>> mips64el | libffi-3.2.1 | NOK | http://autobuild.buildroot.net/results/f05e78f97928c5da48678cdf2e465d413fd5feca/
>> mips | libffi-3.2.1 | NOK | http://autobuild.buildroot.net/results/0094b3f30f8815fa5ef10afb3b0e506549ee8674/
>> mips64el | libffi-3.2.1 | NOK | http://autobuild.buildroot.net/results/4de0087f2bf63612c4354970d8307be7fa8beefd/
>> mips64el | libffi-3.2.1 | NOK | http://autobuild.buildroot.net/results/5d9f963a30eea53dd22f0b0d6f0d63592114977a/
>> mips64el | libffi-3.2.1 | NOK | http://autobuild.buildroot.net/results/0616fba52db8793ea5ac1383c47a86a72aae682f/
>> mips64el | libffi-3.2.1 | NOK | http://autobuild.buildroot.net/results/e2d5f87095f877c9ff7807419014e4af8b43130b/
>> mips | libffi-3.2.1 | NOK | http://autobuild.buildroot.net/results/4dc9605b801518aa8075972e46e83d4df98cdbb5/
>> mips64el | libffi-3.2.1 | NOK | http://autobuild.buildroot.net/results/26dd14f492e4a544400f2d2c6800ee5cde4a0b1f/
>> mips | libffi-3.2.1 | NOK | http://autobuild.buildroot.net/results/8c668a64b6b9ed4ba7a77c3d3211a41de89c33b6/
>
> Vicente, we really need to solve this problem :)
>
>> arm | libnss-3.21 | NOK | http://autobuild.buildroot.net/results/9ba9e0c148110b69763c12e37a37738deab3f118/
>
> /home/buildroot/autobuild/run/instance-1/output/host/usr/arm-buildroot-linux-musleabihf/sysroot/usr/lib/libnspr4.so: undefined reference to `getprotobyname_r'
> /home/buildroot/autobuild/run/instance-1/output/host/usr/arm-buildroot-linux-musleabihf/sysroot/usr/lib/libnspr4.so: undefined reference to `getprotobynumber_r'
>
> Musl build issue.
>
>> powerpc | libnss-3.21 | NOK | http://autobuild.buildroot.net/results/cef2fe3d87b742743a54a2fdbc585771e175a9e6/
>
> In file included from secoid.c:1915:0:
> verref.h: In function 'SECOID_Init':
> verref.h:22:9: error: #pragma GCC diagnostic not allowed inside functions
> verref.h:23:9: error: #pragma GCC diagnostic not allowed inside functions
> cc1: warnings being treated as errors
>
> old compiler problem.
>
>> i686 | lighttpd-1.4.39 | NOK | http://autobuild.buildroot.net/results/13faa9ebce00359b8943775364a432ce422fe8b8/
>
> mod_magnet.c: In function 'magnet_status_set':
> mod_magnet.c:415:2: warning: implicit declaration of function 'luaL_checkint' [-Wimplicit-function-declaration]
> mod_magnet.c: In function 'magnet_copy_response_header':
> mod_magnet.c:692:2: warning: implicit declaration of function 'lua_getfenv' [-Wimplicit-function-declaration]
> mod_magnet.c: In function 'traceback':
> mod_magnet.c:839:18: error: 'LUA_GLOBALSINDEX' undeclared (first use in this function)
> mod_magnet.c:839:18: note: each undeclared identifier is reported only once for each function it appears in
> mod_magnet.c: In function 'magnet_attract':
> mod_magnet.c:987:19: error: 'LUA_GLOBALSINDEX' undeclared (first use in this function)
> mod_magnet.c:992:2: warning: implicit declaration of function 'lua_setfenv' [-Wimplicit-function-declaration]
>
> Fran?ois, this seems to be Lua related, can you have a look ?
>
>> arm | linux-firmware-bbe4917c054e... | TIM | http://autobuild.buildroot.net/results/fc6001a9fcaeab2a67d03d5809360de00c16392a/
>
> Ignore.
>
>> sparc | ltp-testsuite-20150903 | NOK | http://autobuild.buildroot.net/results/faa42138e2b5a07b965926e55b831cb6e8eb3c0c/
>
> `undefined__sig_stub 'reference
>
>> sparc64 | ltp-testsuite-20150903 | NOK | http://autobuild.buildroot.net/results/85e181c2f75037e0d9b9a7bd288d9fdaa828bb34/
>
> undefined toreference `to__rt_sig_stub '`
>
> Waldemar, can you have a look ?
>
>> arm | luabitop-1.0.2-1 | NOK | http://autobuild.buildroot.net/results/80d137d91e6f6173e29074cf12a38f192ce0d7ca/
>> xtensa | luabitop-1.0.2-1 | NOK | http://autobuild.buildroot.net/results/15a0e4c3879eb56604fa88c2e31be641e933afa7/
>> aarch64 | luabitop-1.0.2-1 | NOK | http://autobuild.buildroot.net/results/39d2bae1398bd17891a9d0d2f698340fc7dca591/
>> i686 | luabitop-1.0.2-1 | NOK | http://autobuild.buildroot.net/results/7ac0eb736ad264c59637059ce207989c392f00f7/
>> aarch64 | luabitop-1.0.2-1 | NOK | http://autobuild.buildroot.net/results/a95d9b6eee7b41a0ce4cf6456fde08291cd8b860/
>
> Fixed by https://git.busybox.net/buildroot/commit/?id=be5d265220f36df7e0b633fcc55e3a33b2e74035
>
>> microblazeel | make[3]: *** [code/CMakeFil... | TIM | http://autobuild.buildroot.net/results/8df9f0dd9cbc0446c0458d89cb182d0feb795774/
>
> Ignore.
>
>> arc | mesa3d-11.1.0 | NOK | http://autobuild.buildroot.net/results/7b3f5c0e3c59bd49614e8ad4eee3d89e3527a939/
>
> Compiler problem, issue is known by Synopsys.
>
>> sparc64 | moarvm-2015.10 | NOK | http://autobuild.buildroot.net/results/268e328e2d9ea951c0728ab6031d32e2b460d015/
>> sparc64 | moarvm-2015.10 | NOK | http://autobuild.buildroot.net/results/84847a9201244fce3e05e5e4e201f2e1848238de/
>
> ./libmoar.so: undefined reference to `AO_fetch_compare_and_swap_full'
>
> Waldemar, can you have a look ?
>
>> powerpc | nfs-utils-1.3.3 | NOK | http://autobuild.buildroot.net/results/948f81d7ed2c080a675ee9fec754f6fda1fd905f/
>
> Not sure:
>
> cache.c: In function 'same_path':
> cache.c:429:22: error: field 'fh' has incomplete type
> cache.c:436:2: warning: implicit declaration of function 'name_to_handle_at' [-Wimplicit-function-declaration]
> Makefile:613: recipe for target 'mountd-cache.o' failed
>
> Maxime, can you have a look ?
>
>> arm | nut-2.7.2 | NOK | http://autobuild.buildroot.net/results/8fb9cb823d723903f11d70325b0ea09e103504cf/
>
> checking whether to build SNMP drivers... yes
> configure: error: "neon libraries not found, required for neon based XML/HTTP driver"
>
> Most likely a static linking problem.
>
> Yann, you added the nut package, so ... :-)
>
>> sparc64 | opencv-2.4.10 | NOK | http://autobuild.buildroot.net/results/84cfdfa21205954cb8f0e5541332570ba5206add/
>
> Another atomic related problem. Waldemar ?
>
>> arm | openpgm-release-5-2-122 | NOK | http://autobuild.buildroot.net/results/aa2cf491dfb199a349afd107046f428107a583a0/
>
> Musl build issue:
>
> ./include/pgm/gsi.h:47:75: error: unknown type name 'ssize_t'
> bool pgm_gsi_create_from_string (pgm_gsi_t*restrict, const char*restrict, ssize_t);
>
> Anyone to look into this?
>
>> mipsel | pinentry-0.9.4 | NOK | http://autobuild.buildroot.net/results/d8d6414ae28d9ea84118dfa5c0f73d9334a1c417/
>
> error: member 'QChar std::__cxx11::basic_string<QChar, std::char_traits<QChar>, secmem::alloc<QChar> >::<anonymous union>::_M_local_buf [8]' with constructor not allowed in union
> _CharT _M_local_buf[_S_local_capacity + 1];
>
> Anyone understands this ?
>
>> arc | qt-4.8.7 | NOK | http://autobuild.buildroot.net/results/a85a1839a45fb6102e53131ecc8f6dadf92bcdc2/
>
> Static linking, I'm assuming this *could* be fixed by
> https://git.busybox.net/buildroot/commit/?id=12009bb92931b153823110f811632540044d3b02,
> though I am not sure. Alexey ?a
>
>> nios2 | qt-4.8.7 | NOK | http://autobuild.buildroot.net/results/199b8ed788e4ca3eca03b95710a3bb644d81d187/
>> nios2 | qt-4.8.7 | NOK | http://autobuild.buildroot.net/results/546f94ee09fcff27ea2d7c6cebb0b48aec1881f8/
>> nios2 | qt-4.8.7 | NOK | http://autobuild.buildroot.net/results/bb90227b6a18bde0cef45f82620de560d48866e7/
>
> Compiler problem. I don't remember if I reported it.
>
>> arm | rabbitmq-c-0.7.1 | NOK | http://autobuild.buildroot.net/results/2ef1ed958db8012224f9174334e9c58edace604a/
>
> Static linking problem. Joris, can you have a look ?
>
>> sh4 | rpm-5.2.0 | NOK | http://autobuild.buildroot.net/results/499f2a3204a6afab96322c431732541fefd622e8/
>
> Internal compiler error...
>
>> arc | ruby-2.3.0 | NOK | http://autobuild.buildroot.net/results/8e98934b066d4973d88e7d28b042b99550d68ae8/
>
> Compiler issue:
>
> /tmp/cctdImle.s: Assembler messages:
> /tmp/cctdImle.s:2253: Error: invalid register number `63'
> /tmp/cctdImle.s:2255: Error: invalid register number `63'
>
> Alexey ?
>
>> powerpc | ruby-2.3.0 | NOK | http://autobuild.buildroot.net/results/d0a77147cba429bb42f102141810a23e831a8bcb/
>
> Compiler issue:
>
> eval.c: In function 'rb_protect':
> eval.c:881:1: internal compiler error: in move_insn, at haifa-sched.c:3439
>
>> arc | ruby-2.3.0 | NOK | http://autobuild.buildroot.net/results/748771df79b8537d3f4baeb1f7d423dec1f8c519/
>
> Same ARC compiler issue as above.
>
>> arm | sane-backends-1.0.25 | NOK | http://autobuild.buildroot.net/results/9759238db294c0703e8c685f2adc41dba3fdb31f/
>
> ../backend/.libs/libsane.a(libepsonds_la-epsonds.o):(.bss+0x10): multiple definition of `source_list'
> ../backend/.libs/libsane.a(libepson2_la-epson2.o):(.data+0x40): first defined here
> ../backend/.libs/libsane.a(libepsonds_la-epsonds.o):(.data+0x10): multiple definition of `mode_params'
> ../backend/.libs/libsane.a(libepson2_la-epson2.o):(.data+0x0): first defined here
>
> Vicente, you bumped sane-backends recently, can you have a look ?
>
>> mips64el | sconeserver-3b886c3dda6eda3... | NOK | http://autobuild.buildroot.net/results/be8d1ad7c05b39f8ed65b86f938bc2d9530e3c6d/
>
> Static linking issue, most likely:
>
> checking for mysql_init in -lmysqlclient... no
> configure: error: library 'mysqlclient' is required for the mysql module
>
> Anyone interested ?
>
>> arc | trousers-0.3.13 | NOK | http://autobuild.buildroot.net/results/c3d3bedffe0f4ba40f33d18e90a4802f4a7bfffb/
>
> PIE problem, under discussion.
>
>> arm | tstools-08f6be304040e7b8476... | NOK | http://autobuild.buildroot.net/results/357de0b07b2104e0c94cb3d21ca2096df0796071/
>
> Tries to build a shared library, in a static linking scenario. Anyone ?
>
>> xtensa | uboot-tools-2015.10 | NOK | http://autobuild.buildroot.net/results/64ac87a2a4847a45fc96cfaa4ded7f0821f66701/
>> xtensa | uboot-tools-2015.10 | NOK | http://autobuild.buildroot.net/results/9ebc5e3a6f1dd3ceb90d6786a1c5455c965f819e/
>> microblazeel | uboot-tools-2015.10 | NOK | http://autobuild.buildroot.net/results/a197f03c1751a87c7f71e057f2c4619538b4b6c8/
>
> Patch pending to fix this.
>
>> xtensa | unknown | NOK | http://autobuild.buildroot.net/results/f913556517654f833bf17f141597ba41570b02b7/
>> arm | unknown | NOK | http://autobuild.buildroot.net/results/865ce538e3dc3ce8005a39b5400fc3f019d7a411/
>> arm | unknown | NOK | http://autobuild.buildroot.net/results/0581889edfb7bf5ca0f23e3111ac6eeffbee3376/
>> mips64el | unknown | NOK | http://autobuild.buildroot.net/results/1abb03babacacf13db33ae9fe89b5d52925b58b1/
>
> 2 different dependency problems.
>
>> arm | util-linux-2.27.1 | NOK | http://autobuild.buildroot.net/results/2ca06e6bb9b147a44400e26acdd41dcc3ab7d9e4/
>
> checking for prlimit... no
> configure: error: flock selected, but required timer_create function not available
>
> Static linking issue. Anyone ?
>
>> mips | valgrind-3.11.0 | NOK | http://autobuild.buildroot.net/results/a00f4856c4094508334477296d0ec203466fe56e/
>
> Vicente, this one is for you :)
>
>> arm | vpnc-0.5.3 | NOK | http://autobuild.buildroot.net/results/aacb5ae636e2ae2df67a91696b1d2af276777b22/
>
> Yet another static linking issue caused by libintl.
>
>> nios2 | zbar-854a5d97059e395807091a... | NOK | http://autobuild.buildroot.net/results/d4a9e291ad1b36bd268b4b850aa10be3ac00b6d9/
>> arm | zbar-854a5d97059e395807091a... | NOK | http://autobuild.buildroot.net/results/c9cdee9e5cd031e5927b7aa26d92c48dbe35c1e7/
>
> Really bogus code triggers a warning that is now an error. Volkov, you
> added the zbar package, can you have a look ?
>
> Thanks!
>
> Thomas
> --
> Thomas Petazzoni, CTO, Free Electrons
> Embedded Linux, Kernel and Android engineering
> http://free-electrons.com
^ permalink raw reply [flat|nested] 25+ messages in thread
* [Buildroot] Analysis of build failures
2016-01-17 1:42 ` Frank Hunleth
@ 2016-01-17 11:23 ` Thomas Petazzoni
2016-01-17 16:33 ` Frank Hunleth
0 siblings, 1 reply; 25+ messages in thread
From: Thomas Petazzoni @ 2016-01-17 11:23 UTC (permalink / raw)
To: buildroot
Hello,
On Sat, 16 Jan 2016 20:42:55 -0500, Frank Hunleth wrote:
> > Frank, can you investigate why it builds on x86_64 but not on aarch64 ?
>
> I looked into this a little. My suspicion is that the atomic intrinsic
> macros in the Erlang code have not been ported to aarch64, but I'm
> having trouble following the code. I've inquired on the Erlang mailing
> list and will report back.
Excellent, thanks a lot!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
^ permalink raw reply [flat|nested] 25+ messages in thread
* [Buildroot] Analysis of build failures
2016-01-16 23:11 ` [Buildroot] Analysis of build failures Thomas Petazzoni
2016-01-17 1:42 ` Frank Hunleth
@ 2016-01-17 15:06 ` Matthew Weber
2016-01-17 17:26 ` Thomas Petazzoni
2016-01-17 17:10 ` Maxime Hadjinlian
` (8 subsequent siblings)
10 siblings, 1 reply; 25+ messages in thread
From: Matthew Weber @ 2016-01-17 15:06 UTC (permalink / raw)
To: buildroot
Hi Thomas,
On Sat, Jan 16, 2016 at 5:11 PM, Thomas Petazzoni
<thomas.petazzoni@free-electrons.com> wrote:
> Hello,
>
> Gustavo, Vicente, J?rg, Frank, Bernd, Maxime, Carsten, Davide, Jeremy,
> VIcente, Gilles, Gary, Romain, Matt, Waldemar, Fran?ois, Alexey, Joris,
> Volkov: there are some specific build failures for which your help
> would be appreciated. See below. Thanks in advance for your help!
>
<snip>
>> x86_64 | iputils-s20121011 | NOK | http://autobuild.buildroot.net/results/12cb73f3def95efe706bcd957bc2c091e7931d5a/
>
> Musl build issue. Matt, can you have a look ?
Looks like the development was moved to github and there have been
updates to support uClibc and musl-libc. I'll work on a patch to
update the upstream location and hopefully also remove the one patch
that package has for a ping issue.
Thanks,
Matt
^ permalink raw reply [flat|nested] 25+ messages in thread
* [Buildroot] Analysis of build failures
2016-01-17 11:23 ` Thomas Petazzoni
@ 2016-01-17 16:33 ` Frank Hunleth
2016-01-23 1:05 ` Frank Hunleth
0 siblings, 1 reply; 25+ messages in thread
From: Frank Hunleth @ 2016-01-17 16:33 UTC (permalink / raw)
To: buildroot
Hi Thomas,
On Sun, Jan 17, 2016 at 6:23 AM, Thomas Petazzoni
<thomas.petazzoni@free-electrons.com> wrote:
> Hello,
>
> On Sat, 16 Jan 2016 20:42:55 -0500, Frank Hunleth wrote:
>
>> > Frank, can you investigate why it builds on x86_64 but not on aarch64 ?
>>
>> I looked into this a little. My suspicion is that the atomic intrinsic
>> macros in the Erlang code have not been ported to aarch64, but I'm
>> having trouble following the code. I've inquired on the Erlang mailing
>> list and will report back.
It turns out that other people have gotten Erlang to work on aarch64
without libatomic_ops installed. That doesn't work for Buildroot since
other programs could depend on libatomic_ops. I've filed a bug against
Erlang to track this at http://bugs.erlang.org/browse/ERL-78.
Specifying '--disable-native-ethr-impls' to ./configure seems to
workaround the issue, but I don't know if it has other consequences.
Hopefully the Erlang maintainers will get to this sooner rather than
later, but they're a pretty busy group.
Regards,
Frank
>
> Excellent, thanks a lot!
>
> Thomas
> --
> Thomas Petazzoni, CTO, Free Electrons
> Embedded Linux, Kernel and Android engineering
> http://free-electrons.com
^ permalink raw reply [flat|nested] 25+ messages in thread
* [Buildroot] Analysis of build failures
2016-01-16 23:11 ` [Buildroot] Analysis of build failures Thomas Petazzoni
2016-01-17 1:42 ` Frank Hunleth
2016-01-17 15:06 ` Matthew Weber
@ 2016-01-17 17:10 ` Maxime Hadjinlian
2016-01-18 22:10 ` Thomas Petazzoni
2016-01-17 17:36 ` Jörg Krause
` (7 subsequent siblings)
10 siblings, 1 reply; 25+ messages in thread
From: Maxime Hadjinlian @ 2016-01-17 17:10 UTC (permalink / raw)
To: buildroot
Hi Thomas, all
On Sun, Jan 17, 2016 at 12:11 AM, Thomas Petazzoni
<thomas.petazzoni@free-electrons.com> wrote:
> Hello,
>
> Gustavo, Vicente, J?rg, Frank, Bernd, Maxime, Carsten, Davide, Jeremy,
> VIcente, Gilles, Gary, Romain, Matt, Waldemar, Fran?ois, Alexey, Joris,
> Volkov: there are some specific build failures for which your help
> would be appreciated. See below. Thanks in advance for your help!
>
> On Sat, 16 Jan 2016 08:30:21 +0100 (CET), Thomas Petazzoni wrote:
>
>> xtensa | alsa-utils-1.1.0 | NOK | http://autobuild.buildroot.net/results/1bf954501960db802c3e2280b30b70d6813bdb32/
>> arm | alsa-utils-1.1.0 | NOK | http://autobuild.buildroot.net/results/7ba954e03822d758e25356935b0dfc2c91d3712a/
>
> <dlfcn.h> needed by the topology code. Fixed in
> https://git.busybox.net/buildroot/commit/?id=4707383c5d501a9ad7698579e5d0a4e2ab758c7e.
>
>> bfin | assimp-v3.2 | NOK | http://autobuild.buildroot.net/results/a5558d054ab19f078d0992f8b691f35f3f1323c0/
>
> Compiler error, in FLAT mode. Not sure what's going on, as I was able
> to build assimp properly in a minimal Blackfin FLAT configuration.
>
>> bfin | assimp-v3.2 | NOK | http://autobuild.buildroot.net/results/f0d25c8b08ba32361d47bd6bc344695f168396de/
>> bfin | assimp-v3.2 | NOK | http://autobuild.buildroot.net/results/3f143ea946ad98176d8e5eaddecfa0bda11c0439/
>> sparc64 | assimp-v3.2 | NOK | http://autobuild.buildroot.net/results/510c59e13f1412ffb831801e6389a32a76b543b6/
>> sparc | assimp-v3.2 | NOK | http://autobuild.buildroot.net/results/3f6f7a72bec601688991111f21e897306b1d76ca/
>> xtensa | assimp-v3.2 | NOK | http://autobuild.buildroot.net/results/5eab445d66a977cdfb73a6b5dede6af692c28b16/
>> xtensa | assimp-v3.2 | NOK | http://autobuild.buildroot.net/results/a511687d937c2575d8edffe9235b1507be1c9442/
>> bfin | assimp-v3.2 | NOK | http://autobuild.buildroot.net/results/eb659085949c6b62108b8c46c50e8abd01681f23/
>> bfin | assimp-v3.2 | NOK | http://autobuild.buildroot.net/results/4f3c001e8fa6781c4a2ca9d82023f959b7897035/
>> powerpc | assimp-v3.2 | NOK | http://autobuild.buildroot.net/results/5a90ba61c5ac863a7779af7783c7b0584a0c79e3/
>> powerpc | assimp-v3.2 | NOK | http://autobuild.buildroot.net/results/a70ec3a94a18db77f094c71d8be055ae0d99862b/
>> xtensa | assimp-v3.2 | NOK | http://autobuild.buildroot.net/results/c0a57f9a03c308dcf8129d300d12f4a7d6d999de/
>> powerpc | assimp-v3.2 | NOK | http://autobuild.buildroot.net/results/d37761e95f2f45e92ef641e7117ff6d02f2865d1/
>> xtensa | assimp-v3.2 | NOK | http://autobuild.buildroot.net/results/651efb92cd38569a1c53000c642b37a5c4b21115/
>> powerpc | assimp-v3.2 | NOK | http://autobuild.buildroot.net/results/498380d65b3e3d604a36facec894fc60a30a5d74/
>> mips | assimp-v3.2 | NOK | http://autobuild.buildroot.net/results/37ce98706477b259da4e9527878aeada2d52366c/
>> powerpc | assimp-v3.2 | NOK | http://autobuild.buildroot.net/results/686755f4f925811fccbdadbe28ba7561af8c51ad/
>> bfin | assimp-v3.2 | NOK | http://autobuild.buildroot.net/results/2f46b77f27ca7df9ae80ecaa6fdca6d981eeb8ff/
>> powerpc | assimp-v3.2 | NOK | http://autobuild.buildroot.net/results/7be9e4860ca47f8906c355577d71c0c6e8d597be/
>> powerpc | assimp-v3.2 | NOK | http://autobuild.buildroot.net/results/c0bc9693cfbac282599c73e7f0b6dd19e41bbfa3/
>> xtensa | assimp-v3.2 | NOK | http://autobuild.buildroot.net/results/23b6e683aa3db28d2103e47fd263dc9c5afd99b8/
>> xtensa | assimp-v3.2 | NOK | http://autobuild.buildroot.net/results/903515ab22c112dacf1583fff77c859c6f68985d/
>> powerpc | assimp-v3.2 | NOK | http://autobuild.buildroot.net/results/23e03277f61490b6f48035075df0fc5e5474168f/
>
> I guess most if not all of these are fixed by
> https://git.busybox.net/buildroot/commit/?id=25ba49518a93265ecb3146e6eb21a2a138989100
> and
> https://git.busybox.net/buildroot/commit/?id=9ebac3bd050ee57cdd8a5ede053aed5522f5e8dc.
>
>> mipsel | bind-9.10.3-P2 | NOK | http://autobuild.buildroot.net/results/c4f88c724829e1a2ff152c756ea3dae80fef149c/
>> mips64el | bind-9.10.3-P2 | NOK | http://autobuild.buildroot.net/results/870879c3d20dcfb327329fab0d8c13f320fd5788/
>> mipsel | bind-9.10.3-P2 | NOK | http://autobuild.buildroot.net/results/1d1889f407adce09f313e8660f8b660f256ea277/
>
> Vicente, Gustavo, can you have a look at those issues? It seems to be
> limited to MIPS, and I don't think it was happening before the recent
> bump of the bind package.
>
>> arm | bluez5_utils-5.37 | NOK | http://autobuild.buildroot.net/results/83112559d84dc156141339a31e3e02f1a2af5155/
>
> Fixed by
> https://git.busybox.net/buildroot/commit/?id=d7c54cb0c0cf8cb013d88ad3c2989ec323323235.
>
>> powerpc | boost-1.60.0 | NOK | http://autobuild.buildroot.net/results/e92fc7bac808e708e1aadd1b8e6677d003e5bbe4/
>> arm | boost-1.60.0 | NOK | http://autobuild.buildroot.net/results/46d0907fe06a7b93bb092ad4bf869a2e0030cf32/
>> x86_64 | boost-1.60.0 | NOK | http://autobuild.buildroot.net/results/9ef4d4f5d793f9a854d3a398d00eec6ce9b59178/
>> x86_64 | boost-1.60.0 | NOK | http://autobuild.buildroot.net/results/74e22545f50c9f9e7f12208a1cb9cbb9154a6150/
>> powerpc | boost-1.60.0 | NOK | http://autobuild.buildroot.net/results/5438729ded4bf9887a1dc080366aee9abf27fb19/
>> x86_64 | boost-1.60.0 | NOK | http://autobuild.buildroot.net/results/99ef4325d424569bbd900d6590b8a3a5e445c140/
>> arc | boost-1.60.0 | NOK | http://autobuild.buildroot.net/results/caded0b9ff89ba69cb3775d5fef18565a85a398a/
>> x86_64 | boost-1.60.0 | NOK | http://autobuild.buildroot.net/results/b81bcc845a091ff1182df7dec306492b67db10ea/
>> xtensa | boost-1.60.0 | NOK | http://autobuild.buildroot.net/results/29241cbf4791947e8bd990253716d8d43e219c23/
>> mips64el | boost-1.60.0 | NOK | http://autobuild.buildroot.net/results/648507a680fa0360622ad1fdd47fdf30d3c54091/
>> x86_64 | boost-1.60.0 | NOK | http://autobuild.buildroot.net/results/dea9364e8d8276bbcf42847822ef5da905cd7007/
>> x86_64 | boost-1.60.0 | NOK | http://autobuild.buildroot.net/results/adcea53d916e0825cb5963768304dfe883d5d379/
>> microblazeel | boost-1.60.0 | NOK | http://autobuild.buildroot.net/results/41ee80a733bc676d07d8296b262125b616070835/
>> xtensa | boost-1.60.0 | NOK | http://autobuild.buildroot.net/results/2c555d574540caf3a3b1ed64502274d3ba1f551b/
>> arc | boost-1.60.0 | NOK | http://autobuild.buildroot.net/results/316dc6221a50537234e4b3e88268363d61b9bf59/
>> arc | boost-1.60.0 | NOK | http://autobuild.buildroot.net/results/d4eb7cdbfd1152bb5a2a80f832c5edf524852701/
>> sh4 | boost-1.60.0 | NOK | http://autobuild.buildroot.net/results/3bb3e2b683eabe7a6a9626f083b761b158a418ba/
>> x86_64 | boost-1.60.0 | NOK | http://autobuild.buildroot.net/results/0e2f3f4e4fa9dca521206d52fc061709534be12b/
>> x86_64 | boost-1.60.0 | NOK | http://autobuild.buildroot.net/results/84f5d3417ef5cdb826435b0029ddc8d2e9e4ec44/
>> x86_64 | boost-1.60.0 | NOK | http://autobuild.buildroot.net/results/428cb84d3bde356050b04647a599aea0fae6aeff/
>
> Some of these are the isnan() declaration issue, which is now fixed
> thanks to
> https://git.busybox.net/buildroot/commit/?id=640b75c8d73d713c908d6b288802c9e6bffe76ed.
>
> However, there is still the FE_* definition problem. J?rg, do you have
> something in the works to fix this ?
>
>> arm | canfestival-7740ac6fdedc23e... | NOK | http://autobuild.buildroot.net/results/5c5a48b050223d5f4f66a3a5ddde12cb17e310d7/
>
> musl build issue. There was a thread in August between Yann and Brendan
> about this. I pinged the thread.
>
>> arm | chocolate-doom-2.2.1 | NOK | http://autobuild.buildroot.net/results/20019b0daebf1aaf44e0802603108ff712f60513/
>
> In static linking configurations, when SDL_mixer is linked against
> libmad, chocolate-doom doesn't pass -lmad. To fix this, we need to:
>
> * Fix SDL_mixer.pc so that it references libmad in Libs.private (or
> Requires.private ?)
>
> * Either use pkg-config directly in chocolate-doom.mk to pass the
> appropriate flags, or change the chocolate-doom build system itself.
>
> Note that a similar problem might appear when SDL_mixer is linked
> against vorbis.
>
> Rodrigo, since you added the chocolate-doom package, can you look into
> fixing this ?
>
>> microblazeel | code/CMakeFiles/assimp.dir/... | TIM | http://autobuild.buildroot.net/results/50b9c93c0ee080c42362fd6d210745446077d7f5/
>
> Don't care.
>
>> arm | dvbsnoop-1.4.50 | NOK | http://autobuild.buildroot.net/results/2040d919e9d2564cf283ab815bea5ef34840ee61/
>
> musl build issue. Carsten, you added this package back in 2013, can you
> have a look ?
>
>> aarch64 | erlang-17.5 | NOK | http://autobuild.buildroot.net/results/0cd22eb74fa29e5a85bf897762e16ab3daf33962/
>
> Build problem due to atomic intrinsics:
>
> more undefined references to `__atomic_store_16' follow
>
> Frank, can you investigate why it builds on x86_64 but not on aarch64 ?
>
>> x86_64 | faifa-v0.1 | NOK | http://autobuild.buildroot.net/results/617e5635e0c508f82043f21886b6ce9a30549ad2/
>
> Classical musl build issue. Maxime, you added this package, so can you
> fix it ? :-)
Yep, I'll cook up some patch for this.
>
>> mips64el | ffmpeg-2.8.4 | NOK | http://autobuild.buildroot.net/results/12ef8ee60b3c016e8998ff240a6dc51e682f3058/
>> mips64el | ffmpeg-2.8.4 | NOK | http://autobuild.buildroot.net/results/a964ce679fed3eaaebd0ee2f39639d8243e227ef/
>
> ERROR: fontconfig not found using pkg-config
>
> Bernd, Vicente ?
>
>> microblazeel | flann-04b4a56533faf8c8228d0... | NOK | http://autobuild.buildroot.net/results/6126357850f15fb97828cd1b186e71ced83716eb/
>
> internal compiler error: in gen_reg_rtx, at emit-rtl.c:838
>
> To be tested with the latest gcc version, and potentially report a gcc
> bug.
>
> Davide, you added this package back in 2014. Can you have a look ?
>
>> microblazeel | fxload-2008_10_13 | NOK | http://autobuild.buildroot.net/results/4fa96981077c61599cc04b7c0f96b9f430f17f85/
>
> Binutils issue this time:
>
> /tmp/ccQKhnE1.s: Assembler messages:
> /tmp/ccQKhnE1.s: Error: PC relative branch to label logerror which is not in the instruction space
> /tmp/ccQKhnE1.s: Error: PC relative branch to label logerror which is not in the instruction space
>
> Same deal: test with the latest binutils version, and report a bug if
> the problem still exists.
>
> Jeremy, you added the fxload package, can you have a look ?
>
>
>> i686 | gst1-plugins-bad-1.6.2 | NOK | http://autobuild.buildroot.net/results/fab7afc3490d77a6b29760394337298f2fd55d51/
>> x86_64 | gst1-plugins-bad-1.6.2 | NOK | http://autobuild.buildroot.net/results/4da1b0454fe7bf028a62058d28dafda104fb75f4/
>
> gstdvbsrc.c: In function 'gst_dvbsrc_code_rate_get_type':
> gstdvbsrc.c:273:6: error: 'FEC_2_5' undeclared (first use in this function)
> gstdvbsrc.c:273:6: note: each undeclared identifier is reported only once for each function it appears in
> gstdvbsrc.c: In function 'gst_dvbsrc_modulation_get_type':
> gstdvbsrc.c:303:6: error: 'QAM_4_NR' undeclared (first use in this function)
> gstdvbsrc.c:303:5: error: initializer element is not constant
> gstdvbsrc.c:303:5: error: (near initialization for 'modulation_types[13].value')
>
> Not sure. Peter, Gustavo ?
>
>> sparc | harfbuzz-1.1.3 | NOK | http://autobuild.buildroot.net/results/30dec74537539dcbfa97eb9f90f40b2a814830d1/
>
> hb-warning.cc:32:2: error: #error "Could not find any system to define atomic_int macros, library WILL NOT be thread-safe"
> #error "Could not find any system to define atomic_int macros, library WILL NOT be thread-safe"
> ^
> hb-warning.cc:33:2: error: #error "Check hb-atomic-private.hh for possible resolutions."
> #error "Check hb-atomic-private.hh for possible resolutions."
>
> Gustavo, maybe we simply should disable this package on Sparc ? Only
> annoyance is that it is selected by Pango, which means that all reverse
> dependencies of Pango would have to be fixed :-/
>
> Another idea ?
>
>> aarch64 | hidapi-d17db57b9d4354752e0a... | NOK | http://autobuild.buildroot.net/results/7d70b7dac91209d1a63c131e9eb098bd8be3e84c/
>
> make[3]: *** No rule to make target `hidtest.o', needed by `hidtest-libusb'. Stop.
>
> Vicente, you added this package, can you have a look ?
>
>> powerpc | host-python3-3.4.3 | NOK | http://autobuild.buildroot.net/results/49d02998eeb5817d92574f61f6786a4f5c71d131/
>
> Modules/getbuildinfo.o: file not recognized: File truncated
> collect2: error: ld returned 1 exit status
>
> Ooch, smells like a parallel build issue... but building Python with
> make -j1 would really be horrible :-/
>
>> nios2 | host-vboot-utils-bbdd62f9b0... | NOK | http://autobuild.buildroot.net/results/e8e730f90357fd9818d19ae48b7533c8c5dcbc49/
>> arm | host-vboot-utils-bbdd62f9b0... | NOK | http://autobuild.buildroot.net/results/3c673e550535d741d2773e359ed2bebaebad6ad2/
>> bfin | host-vboot-utils-bbdd62f9b0... | NOK | http://autobuild.buildroot.net/results/5d526c4348a0ab3d802a9ef795096b2bfd1b3515/
>> arm | host-vboot-utils-bbdd62f9b0... | NOK | http://autobuild.buildroot.net/results/e64262b0045195892b2c7ed08cfef8f5682b9793/
>> x86_64 | host-vboot-utils-bbdd62f9b0... | NOK | http://autobuild.buildroot.net/results/844424b9db5ced38f90936fdc96eba480de34459/
>> bfin | host-vboot-utils-bbdd62f9b0... | NOK | http://autobuild.buildroot.net/results/3ef4945e7c51f354eb4444fc40f50ba0e86929e9/
>> arc | host-vboot-utils-bbdd62f9b0... | NOK | http://autobuild.buildroot.net/results/cec1c9d0723d72693d526dcfc3e9432b7694911f/
>
> Issue specific to this autobuilder instance, I'll have a look at this
> one.
>
>> arm | httping-2.4 | NOK | http://autobuild.buildroot.net/results/f88f0dd592a52128d250b2c8668a524d6ca35d24/
>
> Improper libintl handling. Gustavo, you bumped this package last year,
> can you have a look ?
>
>> arm | imx-kobs-3.14.28-1.0.0 | NOK | http://autobuild.buildroot.net/results/05a159c7f8382237d4c941b1bb6de7dad72708f3/
>
> Gary, can you have a look ?
>
>> arm | iprutils-2.4.5 | NOK | http://autobuild.buildroot.net/results/61e121c25fc07083bcccedfcb4f938d18f5c5456/
>
> Musl build issue:
>
> iprlib.h:49:27: fatal error: bits/sockaddr.h: No such file or directory
> #include <bits/sockaddr.h>
>
> Romain, you bumped this package recently, can you have a look ?
>
>> arm | ipsec-tools-0.8.2 | NOK | http://autobuild.buildroot.net/results/ce0bb96971147669c1bb253ce259eb5756f1d85e/
>
> Musl build issue. Gustavo, can you have a look ?
>
>> x86_64 | iputils-s20121011 | NOK | http://autobuild.buildroot.net/results/12cb73f3def95efe706bcd957bc2c091e7931d5a/
>
> Musl build issue. Matt, can you have a look ?
>
>> nios2 | libcap-ng-0.7.4 | NOK | http://autobuild.buildroot.net/results/ae9eca750d27f80cf8b0743f41cdfcc50ea476f1/
>> nios2 | libcap-ng-0.7.4 | NOK | http://autobuild.buildroot.net/results/dca1ba4a15cd9326a43e99d78bd13021bc87d9a2/
>
> Romain, I don't remember what was the conclusion about this issue. I
> remember we discussed it at some point.
>
>> sparc | libdrm-2.4.66 | NOK | http://autobuild.buildroot.net/results/fa0ac44d3c7953b2e2afa03cd7570d8a5d49fcc4/
>
> Waldemar, this is a sparc problem, can you look into it ?
>
>> mips | libffi-3.2.1 | NOK | http://autobuild.buildroot.net/results/cf7fd3dc8a1373c6c963a83e55d093b945f90f1a/
>> mips64el | libffi-3.2.1 | NOK | http://autobuild.buildroot.net/results/a7dd03a12c06a1f01826f01f91b39af396dca0d8/
>> mips64el | libffi-3.2.1 | NOK | http://autobuild.buildroot.net/results/a39a87c6547c9daa27e8a257c9e573d4c222fca4/
>> mips | libffi-3.2.1 | NOK | http://autobuild.buildroot.net/results/f09b5d6120203cd5ddc60951828f880905297bcb/
>> mips | libffi-3.2.1 | NOK | http://autobuild.buildroot.net/results/108cdfac94e88bfdc318e0689295a3799cc23069/
>> mips64el | libffi-3.2.1 | NOK | http://autobuild.buildroot.net/results/c14cabcc51f6870a0ab2381b32220d944590669f/
>> mips64el | libffi-3.2.1 | NOK | http://autobuild.buildroot.net/results/f05e78f97928c5da48678cdf2e465d413fd5feca/
>> mips | libffi-3.2.1 | NOK | http://autobuild.buildroot.net/results/0094b3f30f8815fa5ef10afb3b0e506549ee8674/
>> mips64el | libffi-3.2.1 | NOK | http://autobuild.buildroot.net/results/4de0087f2bf63612c4354970d8307be7fa8beefd/
>> mips64el | libffi-3.2.1 | NOK | http://autobuild.buildroot.net/results/5d9f963a30eea53dd22f0b0d6f0d63592114977a/
>> mips64el | libffi-3.2.1 | NOK | http://autobuild.buildroot.net/results/0616fba52db8793ea5ac1383c47a86a72aae682f/
>> mips64el | libffi-3.2.1 | NOK | http://autobuild.buildroot.net/results/e2d5f87095f877c9ff7807419014e4af8b43130b/
>> mips | libffi-3.2.1 | NOK | http://autobuild.buildroot.net/results/4dc9605b801518aa8075972e46e83d4df98cdbb5/
>> mips64el | libffi-3.2.1 | NOK | http://autobuild.buildroot.net/results/26dd14f492e4a544400f2d2c6800ee5cde4a0b1f/
>> mips | libffi-3.2.1 | NOK | http://autobuild.buildroot.net/results/8c668a64b6b9ed4ba7a77c3d3211a41de89c33b6/
>
> Vicente, we really need to solve this problem :)
>
>> arm | libnss-3.21 | NOK | http://autobuild.buildroot.net/results/9ba9e0c148110b69763c12e37a37738deab3f118/
>
> /home/buildroot/autobuild/run/instance-1/output/host/usr/arm-buildroot-linux-musleabihf/sysroot/usr/lib/libnspr4.so: undefined reference to `getprotobyname_r'
> /home/buildroot/autobuild/run/instance-1/output/host/usr/arm-buildroot-linux-musleabihf/sysroot/usr/lib/libnspr4.so: undefined reference to `getprotobynumber_r'
>
> Musl build issue.
>
>> powerpc | libnss-3.21 | NOK | http://autobuild.buildroot.net/results/cef2fe3d87b742743a54a2fdbc585771e175a9e6/
>
> In file included from secoid.c:1915:0:
> verref.h: In function 'SECOID_Init':
> verref.h:22:9: error: #pragma GCC diagnostic not allowed inside functions
> verref.h:23:9: error: #pragma GCC diagnostic not allowed inside functions
> cc1: warnings being treated as errors
>
> old compiler problem.
>
>> i686 | lighttpd-1.4.39 | NOK | http://autobuild.buildroot.net/results/13faa9ebce00359b8943775364a432ce422fe8b8/
>
> mod_magnet.c: In function 'magnet_status_set':
> mod_magnet.c:415:2: warning: implicit declaration of function 'luaL_checkint' [-Wimplicit-function-declaration]
> mod_magnet.c: In function 'magnet_copy_response_header':
> mod_magnet.c:692:2: warning: implicit declaration of function 'lua_getfenv' [-Wimplicit-function-declaration]
> mod_magnet.c: In function 'traceback':
> mod_magnet.c:839:18: error: 'LUA_GLOBALSINDEX' undeclared (first use in this function)
> mod_magnet.c:839:18: note: each undeclared identifier is reported only once for each function it appears in
> mod_magnet.c: In function 'magnet_attract':
> mod_magnet.c:987:19: error: 'LUA_GLOBALSINDEX' undeclared (first use in this function)
> mod_magnet.c:992:2: warning: implicit declaration of function 'lua_setfenv' [-Wimplicit-function-declaration]
>
> Fran?ois, this seems to be Lua related, can you have a look ?
>
>> arm | linux-firmware-bbe4917c054e... | TIM | http://autobuild.buildroot.net/results/fc6001a9fcaeab2a67d03d5809360de00c16392a/
>
> Ignore.
>
>> sparc | ltp-testsuite-20150903 | NOK | http://autobuild.buildroot.net/results/faa42138e2b5a07b965926e55b831cb6e8eb3c0c/
>
> `undefined__sig_stub 'reference
>
>> sparc64 | ltp-testsuite-20150903 | NOK | http://autobuild.buildroot.net/results/85e181c2f75037e0d9b9a7bd288d9fdaa828bb34/
>
> undefined toreference `to__rt_sig_stub '`
>
> Waldemar, can you have a look ?
>
>> arm | luabitop-1.0.2-1 | NOK | http://autobuild.buildroot.net/results/80d137d91e6f6173e29074cf12a38f192ce0d7ca/
>> xtensa | luabitop-1.0.2-1 | NOK | http://autobuild.buildroot.net/results/15a0e4c3879eb56604fa88c2e31be641e933afa7/
>> aarch64 | luabitop-1.0.2-1 | NOK | http://autobuild.buildroot.net/results/39d2bae1398bd17891a9d0d2f698340fc7dca591/
>> i686 | luabitop-1.0.2-1 | NOK | http://autobuild.buildroot.net/results/7ac0eb736ad264c59637059ce207989c392f00f7/
>> aarch64 | luabitop-1.0.2-1 | NOK | http://autobuild.buildroot.net/results/a95d9b6eee7b41a0ce4cf6456fde08291cd8b860/
>
> Fixed by https://git.busybox.net/buildroot/commit/?id=be5d265220f36df7e0b633fcc55e3a33b2e74035
>
>> microblazeel | make[3]: *** [code/CMakeFil... | TIM | http://autobuild.buildroot.net/results/8df9f0dd9cbc0446c0458d89cb182d0feb795774/
>
> Ignore.
>
>> arc | mesa3d-11.1.0 | NOK | http://autobuild.buildroot.net/results/7b3f5c0e3c59bd49614e8ad4eee3d89e3527a939/
>
> Compiler problem, issue is known by Synopsys.
>
>> sparc64 | moarvm-2015.10 | NOK | http://autobuild.buildroot.net/results/268e328e2d9ea951c0728ab6031d32e2b460d015/
>> sparc64 | moarvm-2015.10 | NOK | http://autobuild.buildroot.net/results/84847a9201244fce3e05e5e4e201f2e1848238de/
>
> ./libmoar.so: undefined reference to `AO_fetch_compare_and_swap_full'
>
> Waldemar, can you have a look ?
>
>> powerpc | nfs-utils-1.3.3 | NOK | http://autobuild.buildroot.net/results/948f81d7ed2c080a675ee9fec754f6fda1fd905f/
>
> Not sure:
>
> cache.c: In function 'same_path':
> cache.c:429:22: error: field 'fh' has incomplete type
> cache.c:436:2: warning: implicit declaration of function 'name_to_handle_at' [-Wimplicit-function-declaration]
> Makefile:613: recipe for target 'mountd-cache.o' failed
>
> Maxime, can you have a look ?
I will look at it, the errors is a bit puzzling but I only glanced at
it for now.
>
>> arm | nut-2.7.2 | NOK | http://autobuild.buildroot.net/results/8fb9cb823d723903f11d70325b0ea09e103504cf/
>
> checking whether to build SNMP drivers... yes
> configure: error: "neon libraries not found, required for neon based XML/HTTP driver"
>
> Most likely a static linking problem.
>
> Yann, you added the nut package, so ... :-)
>
>> sparc64 | opencv-2.4.10 | NOK | http://autobuild.buildroot.net/results/84cfdfa21205954cb8f0e5541332570ba5206add/
>
> Another atomic related problem. Waldemar ?
>
>> arm | openpgm-release-5-2-122 | NOK | http://autobuild.buildroot.net/results/aa2cf491dfb199a349afd107046f428107a583a0/
>
> Musl build issue:
>
> ./include/pgm/gsi.h:47:75: error: unknown type name 'ssize_t'
> bool pgm_gsi_create_from_string (pgm_gsi_t*restrict, const char*restrict, ssize_t);
>
> Anyone to look into this?
>
>> mipsel | pinentry-0.9.4 | NOK | http://autobuild.buildroot.net/results/d8d6414ae28d9ea84118dfa5c0f73d9334a1c417/
>
> error: member 'QChar std::__cxx11::basic_string<QChar, std::char_traits<QChar>, secmem::alloc<QChar> >::<anonymous union>::_M_local_buf [8]' with constructor not allowed in union
> _CharT _M_local_buf[_S_local_capacity + 1];
>
> Anyone understands this ?
>
>> arc | qt-4.8.7 | NOK | http://autobuild.buildroot.net/results/a85a1839a45fb6102e53131ecc8f6dadf92bcdc2/
>
> Static linking, I'm assuming this *could* be fixed by
> https://git.busybox.net/buildroot/commit/?id=12009bb92931b153823110f811632540044d3b02,
> though I am not sure. Alexey ?a
>
>> nios2 | qt-4.8.7 | NOK | http://autobuild.buildroot.net/results/199b8ed788e4ca3eca03b95710a3bb644d81d187/
>> nios2 | qt-4.8.7 | NOK | http://autobuild.buildroot.net/results/546f94ee09fcff27ea2d7c6cebb0b48aec1881f8/
>> nios2 | qt-4.8.7 | NOK | http://autobuild.buildroot.net/results/bb90227b6a18bde0cef45f82620de560d48866e7/
>
> Compiler problem. I don't remember if I reported it.
>
>> arm | rabbitmq-c-0.7.1 | NOK | http://autobuild.buildroot.net/results/2ef1ed958db8012224f9174334e9c58edace604a/
>
> Static linking problem. Joris, can you have a look ?
>
>> sh4 | rpm-5.2.0 | NOK | http://autobuild.buildroot.net/results/499f2a3204a6afab96322c431732541fefd622e8/
>
> Internal compiler error...
>
>> arc | ruby-2.3.0 | NOK | http://autobuild.buildroot.net/results/8e98934b066d4973d88e7d28b042b99550d68ae8/
>
> Compiler issue:
>
> /tmp/cctdImle.s: Assembler messages:
> /tmp/cctdImle.s:2253: Error: invalid register number `63'
> /tmp/cctdImle.s:2255: Error: invalid register number `63'
>
> Alexey ?
>
>> powerpc | ruby-2.3.0 | NOK | http://autobuild.buildroot.net/results/d0a77147cba429bb42f102141810a23e831a8bcb/
>
> Compiler issue:
>
> eval.c: In function 'rb_protect':
> eval.c:881:1: internal compiler error: in move_insn, at haifa-sched.c:3439
>
>> arc | ruby-2.3.0 | NOK | http://autobuild.buildroot.net/results/748771df79b8537d3f4baeb1f7d423dec1f8c519/
>
> Same ARC compiler issue as above.
>
>> arm | sane-backends-1.0.25 | NOK | http://autobuild.buildroot.net/results/9759238db294c0703e8c685f2adc41dba3fdb31f/
>
> ../backend/.libs/libsane.a(libepsonds_la-epsonds.o):(.bss+0x10): multiple definition of `source_list'
> ../backend/.libs/libsane.a(libepson2_la-epson2.o):(.data+0x40): first defined here
> ../backend/.libs/libsane.a(libepsonds_la-epsonds.o):(.data+0x10): multiple definition of `mode_params'
> ../backend/.libs/libsane.a(libepson2_la-epson2.o):(.data+0x0): first defined here
>
> Vicente, you bumped sane-backends recently, can you have a look ?
>
>> mips64el | sconeserver-3b886c3dda6eda3... | NOK | http://autobuild.buildroot.net/results/be8d1ad7c05b39f8ed65b86f938bc2d9530e3c6d/
>
> Static linking issue, most likely:
>
> checking for mysql_init in -lmysqlclient... no
> configure: error: library 'mysqlclient' is required for the mysql module
>
> Anyone interested ?
>
>> arc | trousers-0.3.13 | NOK | http://autobuild.buildroot.net/results/c3d3bedffe0f4ba40f33d18e90a4802f4a7bfffb/
>
> PIE problem, under discussion.
>
>> arm | tstools-08f6be304040e7b8476... | NOK | http://autobuild.buildroot.net/results/357de0b07b2104e0c94cb3d21ca2096df0796071/
>
> Tries to build a shared library, in a static linking scenario. Anyone ?
>
>> xtensa | uboot-tools-2015.10 | NOK | http://autobuild.buildroot.net/results/64ac87a2a4847a45fc96cfaa4ded7f0821f66701/
>> xtensa | uboot-tools-2015.10 | NOK | http://autobuild.buildroot.net/results/9ebc5e3a6f1dd3ceb90d6786a1c5455c965f819e/
>> microblazeel | uboot-tools-2015.10 | NOK | http://autobuild.buildroot.net/results/a197f03c1751a87c7f71e057f2c4619538b4b6c8/
>
> Patch pending to fix this.
>
>> xtensa | unknown | NOK | http://autobuild.buildroot.net/results/f913556517654f833bf17f141597ba41570b02b7/
>> arm | unknown | NOK | http://autobuild.buildroot.net/results/865ce538e3dc3ce8005a39b5400fc3f019d7a411/
>> arm | unknown | NOK | http://autobuild.buildroot.net/results/0581889edfb7bf5ca0f23e3111ac6eeffbee3376/
>> mips64el | unknown | NOK | http://autobuild.buildroot.net/results/1abb03babacacf13db33ae9fe89b5d52925b58b1/
>
> 2 different dependency problems.
>
>> arm | util-linux-2.27.1 | NOK | http://autobuild.buildroot.net/results/2ca06e6bb9b147a44400e26acdd41dcc3ab7d9e4/
>
> checking for prlimit... no
> configure: error: flock selected, but required timer_create function not available
>
> Static linking issue. Anyone ?
>
>> mips | valgrind-3.11.0 | NOK | http://autobuild.buildroot.net/results/a00f4856c4094508334477296d0ec203466fe56e/
>
> Vicente, this one is for you :)
>
>> arm | vpnc-0.5.3 | NOK | http://autobuild.buildroot.net/results/aacb5ae636e2ae2df67a91696b1d2af276777b22/
>
> Yet another static linking issue caused by libintl.
>
>> nios2 | zbar-854a5d97059e395807091a... | NOK | http://autobuild.buildroot.net/results/d4a9e291ad1b36bd268b4b850aa10be3ac00b6d9/
>> arm | zbar-854a5d97059e395807091a... | NOK | http://autobuild.buildroot.net/results/c9cdee9e5cd031e5927b7aa26d92c48dbe35c1e7/
>
> Really bogus code triggers a warning that is now an error. Volkov, you
> added the zbar package, can you have a look ?
>
> Thanks!
>
> Thomas
> --
> Thomas Petazzoni, CTO, Free Electrons
> Embedded Linux, Kernel and Android engineering
> http://free-electrons.com
^ permalink raw reply [flat|nested] 25+ messages in thread
* [Buildroot] Analysis of build failures
2016-01-17 15:06 ` Matthew Weber
@ 2016-01-17 17:26 ` Thomas Petazzoni
0 siblings, 0 replies; 25+ messages in thread
From: Thomas Petazzoni @ 2016-01-17 17:26 UTC (permalink / raw)
To: buildroot
Matt,
On Sun, 17 Jan 2016 09:06:57 -0600, Matthew Weber wrote:
> > Musl build issue. Matt, can you have a look ?
>
> Looks like the development was moved to github and there have been
> updates to support uClibc and musl-libc. I'll work on a patch to
> update the upstream location and hopefully also remove the one patch
> that package has for a ping issue.
Great, thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
^ permalink raw reply [flat|nested] 25+ messages in thread
* [Buildroot] Analysis of build failures
2016-01-16 23:11 ` [Buildroot] Analysis of build failures Thomas Petazzoni
` (2 preceding siblings ...)
2016-01-17 17:10 ` Maxime Hadjinlian
@ 2016-01-17 17:36 ` Jörg Krause
2016-01-17 18:22 ` Rodrigo Rebello
` (6 subsequent siblings)
10 siblings, 0 replies; 25+ messages in thread
From: Jörg Krause @ 2016-01-17 17:36 UTC (permalink / raw)
To: buildroot
Hi,
On So, 2016-01-17 at 00:11 +0100, Thomas Petazzoni wrote:
> Hello,
>
> Gustavo, Vicente, J?rg, Frank, Bernd, Maxime, Carsten, Davide,
> Jeremy,
> VIcente, Gilles, Gary, Romain, Matt, Waldemar, Fran?ois, Alexey,
> Joris,
> Volkov: there are some specific build failures for which your help
> would be appreciated. See below. Thanks in advance for your help!
>
> On Sat, 16 Jan 2016 08:30:21 +0100 (CET), Thomas Petazzoni wrote:
>
> > ?????powerpc |???????????????????boost-1.60.0 | NOK | http://autobu
> > ild.buildroot.net/results/e92fc7bac808e708e1aadd1b8e6677d003e5bbe4/
> > ?????????arm |???????????????????boost-1.60.0 | NOK | http://autobu
> > ild.buildroot.net/results/46d0907fe06a7b93bb092ad4bf869a2e0030cf32/
> > ??????x86_64 |???????????????????boost-1.60.0 | NOK | http://autobu
> > ild.buildroot.net/results/9ef4d4f5d793f9a854d3a398d00eec6ce9b59178/
> > ??????x86_64 |???????????????????boost-1.60.0 | NOK | http://autobu
> > ild.buildroot.net/results/74e22545f50c9f9e7f12208a1cb9cbb9154a6150/
> > ?????powerpc |???????????????????boost-1.60.0 | NOK | http://autobu
> > ild.buildroot.net/results/5438729ded4bf9887a1dc080366aee9abf27fb19/
> > ??????x86_64 |???????????????????boost-1.60.0 | NOK | http://autobu
> > ild.buildroot.net/results/99ef4325d424569bbd900d6590b8a3a5e445c140/
> > ?????????arc |???????????????????boost-1.60.0 | NOK | http://autobu
> > ild.buildroot.net/results/caded0b9ff89ba69cb3775d5fef18565a85a398a/
> > ??????x86_64 |???????????????????boost-1.60.0 | NOK | http://autobu
> > ild.buildroot.net/results/b81bcc845a091ff1182df7dec306492b67db10ea/
> > ??????xtensa |???????????????????boost-1.60.0 | NOK | http://autobu
> > ild.buildroot.net/results/29241cbf4791947e8bd990253716d8d43e219c23/
> > ????mips64el |???????????????????boost-1.60.0 | NOK | http://autobu
> > ild.buildroot.net/results/648507a680fa0360622ad1fdd47fdf30d3c54091/
> > ??????x86_64 |???????????????????boost-1.60.0 | NOK | http://autobu
> > ild.buildroot.net/results/dea9364e8d8276bbcf42847822ef5da905cd7007/
> > ??????x86_64 |???????????????????boost-1.60.0 | NOK | http://autobu
> > ild.buildroot.net/results/adcea53d916e0825cb5963768304dfe883d5d379/
> > microblazeel |???????????????????boost-1.60.0 | NOK | http://autobu
> > ild.buildroot.net/results/41ee80a733bc676d07d8296b262125b616070835/
> > ??????xtensa |???????????????????boost-1.60.0 | NOK | http://autobu
> > ild.buildroot.net/results/2c555d574540caf3a3b1ed64502274d3ba1f551b/
> > ?????????arc |???????????????????boost-1.60.0 | NOK | http://autobu
> > ild.buildroot.net/results/316dc6221a50537234e4b3e88268363d61b9bf59/
> > ?????????arc |???????????????????boost-1.60.0 | NOK | http://autobu
> > ild.buildroot.net/results/d4eb7cdbfd1152bb5a2a80f832c5edf524852701/
> > ?????????sh4 |???????????????????boost-1.60.0 | NOK | http://autobu
> > ild.buildroot.net/results/3bb3e2b683eabe7a6a9626f083b761b158a418ba/
> > ??????x86_64 |???????????????????boost-1.60.0 | NOK | http://autobu
> > ild.buildroot.net/results/0e2f3f4e4fa9dca521206d52fc061709534be12b/
> > ??????x86_64 |???????????????????boost-1.60.0 | NOK | http://autobu
> > ild.buildroot.net/results/84f5d3417ef5cdb826435b0029ddc8d2e9e4ec44/
> > ??????x86_64 |???????????????????boost-1.60.0 | NOK | http://autobu
> > ild.buildroot.net/results/428cb84d3bde356050b04647a599aea0fae6aeff/
>
> Some of these are the isnan() declaration issue, which is now fixed
> thanks to
> https://git.busybox.net/buildroot/commit/?id=640b75c8d73d713c908d6b28
> 8802c9e6bffe76ed.
>
> However, there is still the FE_* definition problem. J?rg, do you
> have
> something in the works to fix this ?
Not really, someone from OpenWRT reported this issue upstream [1]. I
added a comment to the ticket that it affects Buildroot, too.
My guess is that Boost check for fenv.h implies that FE_* is defined
too, which is wrong for those toolchains.
[1]?https://svn.boost.org/trac/boost/ticket/11756
J?rg
^ permalink raw reply [flat|nested] 25+ messages in thread
* [Buildroot] Analysis of build failures
2016-01-16 23:11 ` [Buildroot] Analysis of build failures Thomas Petazzoni
` (3 preceding siblings ...)
2016-01-17 17:36 ` Jörg Krause
@ 2016-01-17 18:22 ` Rodrigo Rebello
2016-01-17 19:02 ` Gary Bisson
` (5 subsequent siblings)
10 siblings, 0 replies; 25+ messages in thread
From: Rodrigo Rebello @ 2016-01-17 18:22 UTC (permalink / raw)
To: buildroot
Thomas,
2016-01-16 21:11 GMT-02:00 Thomas Petazzoni
<thomas.petazzoni@free-electrons.com>:
[snip]
>> arm | chocolate-doom-2.2.1 | NOK | http://autobuild.buildroot.net/results/20019b0daebf1aaf44e0802603108ff712f60513/
>
> In static linking configurations, when SDL_mixer is linked against
> libmad, chocolate-doom doesn't pass -lmad. To fix this, we need to:
>
> * Fix SDL_mixer.pc so that it references libmad in Libs.private (or
> Requires.private ?)
>
> * Either use pkg-config directly in chocolate-doom.mk to pass the
> appropriate flags, or change the chocolate-doom build system itself.
>
> Note that a similar problem might appear when SDL_mixer is linked
> against vorbis.
>
> Rodrigo, since you added the chocolate-doom package, can you look into
> fixing this ?
>
No problem, I'll look into that in the next few days.
Regards,
Rodrigo
^ permalink raw reply [flat|nested] 25+ messages in thread
* [Buildroot] Analysis of build failures
2016-01-16 23:11 ` [Buildroot] Analysis of build failures Thomas Petazzoni
` (4 preceding siblings ...)
2016-01-17 18:22 ` Rodrigo Rebello
@ 2016-01-17 19:02 ` Gary Bisson
2016-01-17 19:06 ` Romain Naour
` (4 subsequent siblings)
10 siblings, 0 replies; 25+ messages in thread
From: Gary Bisson @ 2016-01-17 19:02 UTC (permalink / raw)
To: buildroot
Hi Thomas,
On Sun, Jan 17, 2016 at 12:11 AM, Thomas Petazzoni
<thomas.petazzoni@free-electrons.com> wrote:
> <snip>
>> arm | imx-kobs-3.14.28-1.0.0 | NOK | http://autobuild.buildroot.net/results/05a159c7f8382237d4c941b1bb6de7dad72708f3/
>
> Gary, can you have a look ?
This comes from the fact the mtd-user.h header used to include
stdint.h but it's no longer the case since linux 4.4.
http://lxr.free-electrons.com/source/include/uapi/mtd/mtd-user.h?v=4.3
http://lxr.free-electrons.com/source/include/uapi/mtd/mtd-user.h?v=4.4
So I guess I'll offer a patch that adds the stdint inclusion, plus
I'll update the package.
Regards,
Gary
^ permalink raw reply [flat|nested] 25+ messages in thread
* [Buildroot] Analysis of build failures
2016-01-16 23:11 ` [Buildroot] Analysis of build failures Thomas Petazzoni
` (5 preceding siblings ...)
2016-01-17 19:02 ` Gary Bisson
@ 2016-01-17 19:06 ` Romain Naour
2016-01-18 7:06 ` Alexey Brodkin
` (3 subsequent siblings)
10 siblings, 0 replies; 25+ messages in thread
From: Romain Naour @ 2016-01-17 19:06 UTC (permalink / raw)
To: buildroot
Hi Thomas, All,
Le 17/01/2016 00:11, Thomas Petazzoni a ?crit :
> Hello,
>
> Gustavo, Vicente, J?rg, Frank, Bernd, Maxime, Carsten, Davide, Jeremy,
> VIcente, Gilles, Gary, Romain, Matt, Waldemar, Fran?ois, Alexey, Joris,
> Volkov: there are some specific build failures for which your help
> would be appreciated. See below. Thanks in advance for your help!
>
> On Sat, 16 Jan 2016 08:30:21 +0100 (CET), Thomas Petazzoni wrote:
>
>> arm | iprutils-2.4.5 | NOK | http://autobuild.buildroot.net/results/61e121c25fc07083bcccedfcb4f938d18f5c5456/
>
> Musl build issue:
>
> iprlib.h:49:27: fatal error: bits/sockaddr.h: No such file or directory
> #include <bits/sockaddr.h>
>
> Romain, you bumped this package recently, can you have a look ?
>
I would suggest to remove bits/sockaddr.h since it's specific to glibc and add
limits.h to define PATH_MAX or disable for musl. At least iprutils build with
these fixes.
Note that iprutils switched to autotools buildsystem recently (since 2.4.6), so
if we bump to the latest version we can remove the two patches :
0002-Allow-CFLAGS-to-be-extended-from-the-enviro.patch
0003-Fix-static-build-by-passing-the-libraries-i.patch
>
>> nios2 | libcap-ng-0.7.4 | NOK | http://autobuild.buildroot.net/results/ae9eca750d27f80cf8b0743f41cdfcc50ea476f1/
>> nios2 | libcap-ng-0.7.4 | NOK | http://autobuild.buildroot.net/results/dca1ba4a15cd9326a43e99d78bd13021bc87d9a2/
>
> Romain, I don't remember what was the conclusion about this issue. I
> remember we discussed it at some point.
>
It's an issue with gcc <= 5.2 see:
http://lists.busybox.net/pipermail/buildroot/2015-December/146308.html
I think we should rebuild the prebuild nios2 toolchain with gcc 5.3 and the
upcoming binutils 2.26.
>
>> nios2 | qt-4.8.7 | NOK | http://autobuild.buildroot.net/results/199b8ed788e4ca3eca03b95710a3bb644d81d187/
>> nios2 | qt-4.8.7 | NOK | http://autobuild.buildroot.net/results/546f94ee09fcff27ea2d7c6cebb0b48aec1881f8/
>> nios2 | qt-4.8.7 | NOK | http://autobuild.buildroot.net/results/bb90227b6a18bde0cef45f82620de560d48866e7/
>
> Compiler problem. I don't remember if I reported it.
>
Qt-GUI issue with Binutils 2.25.1 (CS NIOSII 2015.11 and prebuild one).
http://patchwork.ozlabs.org/patch/561414/
>
>> xtensa | unknown | NOK | http://autobuild.buildroot.net/results/f913556517654f833bf17f141597ba41570b02b7/
>> arm | unknown | NOK | http://autobuild.buildroot.net/results/865ce538e3dc3ce8005a39b5400fc3f019d7a411/
>> arm | unknown | NOK | http://autobuild.buildroot.net/results/0581889edfb7bf5ca0f23e3111ac6eeffbee3376/
>> mips64el | unknown | NOK | http://autobuild.buildroot.net/results/1abb03babacacf13db33ae9fe89b5d52925b58b1/
>
> 2 different dependency problems.
>
There is also a similar issue with xlib_libfontenc:
http://patchwork.ozlabs.org/patch/564098/
Best regards,
Romain
>
> Thanks!
>
> Thomas
>
^ permalink raw reply [flat|nested] 25+ messages in thread
* [Buildroot] Analysis of build failures
2016-01-16 23:11 ` [Buildroot] Analysis of build failures Thomas Petazzoni
` (6 preceding siblings ...)
2016-01-17 19:06 ` Romain Naour
@ 2016-01-18 7:06 ` Alexey Brodkin
2016-01-18 12:22 ` Gustavo Zacarias
` (2 subsequent siblings)
10 siblings, 0 replies; 25+ messages in thread
From: Alexey Brodkin @ 2016-01-18 7:06 UTC (permalink / raw)
To: buildroot
Hi Thomas,
On Sun, 2016-01-17 at 00:11 +0100, Thomas Petazzoni wrote:
> Hello,
>
> Gustavo, Vicente, J?rg, Frank, Bernd, Maxime, Carsten, Davide, Jeremy,
> VIcente, Gilles, Gary, Romain, Matt, Waldemar, Fran?ois, Alexey, Joris,
> Volkov: there are some specific build failures for which your help
> would be appreciated. See below. Thanks in advance for your help!
>
> On Sat, 16 Jan 2016 08:30:21 +0100 (CET), Thomas Petazzoni wrote:
> > arc | mesa3d-11.1.0 | NOK |
> > http://autobuild.buildroot.net/results/7b3f5c0e3c59bd49614e8ad4eee3d89e3527a939/
>
> Compiler problem, issue is known by Synopsys.
Indeed that's a known problem for us and it's me to blame for seeing no progress here.
Still we already have newer toolchain in its RC1, let's see it problem still happens.
And anyways I'll send a patch with new tools support today.
> > arc | qt-4.8.7 | NOK |
> > http://autobuild.buildroot.net/results/a85a1839a45fb6102e53131ecc8f6dadf92bcdc2/
>
> Static linking, I'm assuming this *could* be fixed by
> https://git.busybox.net/buildroot/commit/?id=12009bb92931b153823110f811632540044d3b02,
> though I am not sure. Alexey?
Well unfortunately mentioned patch doesn't help here, see it's being applied already:
------------------->8------------------
Applying 0009-Fix-library-inclusion-order-when-building-statically.patch using patch:
patching file config.tests/unix/compile.test
^[[3m>>> qt 4.8.7 Configuring^[[23m
------------------->8------------------
So there's something else. I have 1 idea to try here.
>
> > arc | ruby-2.3.0 | NOK |
> > http://autobuild.buildroot.net/results/8e98934b066d4973d88e7d28b042b99550d68ae8/
>
> Compiler issue:
>
> /tmp/cctdImle.s: Assembler messages:
> /tmp/cctdImle.s:2253: Error: invalid register number `63'
> /tmp/cctdImle.s:2255: Error: invalid register number `63'
>
> Alexey ?
Good catch. Again let us try newer tools and if it doesn't help we'll be
bugging our toolchain developers.
> > arc | trousers-0.3.13 | NOK |
> > http://autobuild.buildroot.net/results/c3d3bedffe0f4ba40f33d18e90a4802f4a7bfffb/
>
> PIE problem, under discussion.
Indeed, Lada is busy with that.
Regards,
Alexey
^ permalink raw reply [flat|nested] 25+ messages in thread
* [Buildroot] Analysis of build failures
2016-01-16 23:11 ` [Buildroot] Analysis of build failures Thomas Petazzoni
` (7 preceding siblings ...)
2016-01-18 7:06 ` Alexey Brodkin
@ 2016-01-18 12:22 ` Gustavo Zacarias
2016-01-18 20:53 ` Peter Seiderer
2016-01-19 9:54 ` [Buildroot] [PATCH] zbar: Fix gcc5 logical-not-parentheses error Viacheslav Volkov
10 siblings, 0 replies; 25+ messages in thread
From: Gustavo Zacarias @ 2016-01-18 12:22 UTC (permalink / raw)
To: buildroot
On 16/01/16 20:11, Thomas Petazzoni wrote:
>> powerpc | libnss-3.21 | NOK | http://autobuild.buildroot.net/results/cef2fe3d87b742743a54a2fdbc585771e175a9e6/
>
> In file included from secoid.c:1915:0:
> verref.h: In function 'SECOID_Init':
> verref.h:22:9: error: #pragma GCC diagnostic not allowed inside functions
> verref.h:23:9: error: #pragma GCC diagnostic not allowed inside functions
> cc1: warnings being treated as errors
>
> old compiler problem.
This one is fixed via http://patchwork.ozlabs.org/patch/563960/
>> arm | unknown | NOK | http://autobuild.buildroot.net/results/0581889edfb7bf5ca0f23e3111ac6eeffbee3376/
>> mips64el | unknown | NOK | http://autobuild.buildroot.net/results/1abb03babacacf13db33ae9fe89b5d52925b58b1/
>
> 2 different dependency problems.
Fixed via http://patchwork.ozlabs.org/patch/564312/
(more a backport of 2.10.x features than really trying to fix that
particular failure).
I'll look at the others time allowing.
Regards.
^ permalink raw reply [flat|nested] 25+ messages in thread
* [Buildroot] Analysis of build failures
2016-01-16 23:11 ` [Buildroot] Analysis of build failures Thomas Petazzoni
` (8 preceding siblings ...)
2016-01-18 12:22 ` Gustavo Zacarias
@ 2016-01-18 20:53 ` Peter Seiderer
2016-01-18 21:03 ` Thomas Petazzoni
2016-01-19 9:54 ` [Buildroot] [PATCH] zbar: Fix gcc5 logical-not-parentheses error Viacheslav Volkov
10 siblings, 1 reply; 25+ messages in thread
From: Peter Seiderer @ 2016-01-18 20:53 UTC (permalink / raw)
To: buildroot
Hello Thomas,
On Sun, 17 Jan 2016 00:11:17 +0100, Thomas Petazzoni <thomas.petazzoni@free-electrons.com> wrote:
>
> > i686 | gst1-plugins-bad-1.6.2 | NOK | http://autobuild.buildroot.net/results/fab7afc3490d77a6b29760394337298f2fd55d51/
> > x86_64 | gst1-plugins-bad-1.6.2 | NOK | http://autobuild.buildroot.net/results/4da1b0454fe7bf028a62058d28dafda104fb75f4/
>
> gstdvbsrc.c: In function 'gst_dvbsrc_code_rate_get_type':
> gstdvbsrc.c:273:6: error: 'FEC_2_5' undeclared (first use in this function)
> gstdvbsrc.c:273:6: note: each undeclared identifier is reported only once for each function it appears in
> gstdvbsrc.c: In function 'gst_dvbsrc_modulation_get_type':
> gstdvbsrc.c:303:6: error: 'QAM_4_NR' undeclared (first use in this function)
> gstdvbsrc.c:303:5: error: initializer element is not constant
> gstdvbsrc.c:303:5: error: (near initialization for 'modulation_types[13].value')
>
> Not sure. Peter, Gustavo ?
>
This two enums entered the linux kernel with commit '[media] add DTMB support for DVB API' [1], at least
since linux-3.10 (did no exact search)...., may be depend GST1_PLUGINS_BAD_PLUGIN_DVB on
TOOLCHAIN_HEADERS_AT_LEAST_3_10 ?
Regards,
Peter
[1] https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/include/linux/dvb/frontend.h?id=224b6642f5e82a1b21f6b552c799fa02e527d542
^ permalink raw reply [flat|nested] 25+ messages in thread
* [Buildroot] Analysis of build failures
2016-01-18 20:53 ` Peter Seiderer
@ 2016-01-18 21:03 ` Thomas Petazzoni
0 siblings, 0 replies; 25+ messages in thread
From: Thomas Petazzoni @ 2016-01-18 21:03 UTC (permalink / raw)
To: buildroot
Peter,
On Mon, 18 Jan 2016 21:53:47 +0100, Peter Seiderer wrote:
> This two enums entered the linux kernel with commit '[media] add DTMB support for DVB API' [1], at least
> since linux-3.10 (did no exact search)...., may be depend GST1_PLUGINS_BAD_PLUGIN_DVB on
> TOOLCHAIN_HEADERS_AT_LEAST_3_10 ?
Thanks for the research. This commit dates back from v3.7:
$ git tag --contains 224b6642f5e82a1b21f6b552c799fa02e527d542 | grep ^v | sort -V | head -1
v3.7
I've committed a patch that fixes this. Many thanks for your
investigation!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
^ permalink raw reply [flat|nested] 25+ messages in thread
* [Buildroot] Analysis of build failures
2016-01-17 17:10 ` Maxime Hadjinlian
@ 2016-01-18 22:10 ` Thomas Petazzoni
0 siblings, 0 replies; 25+ messages in thread
From: Thomas Petazzoni @ 2016-01-18 22:10 UTC (permalink / raw)
To: buildroot
Maxime,
I know you're using GMail, but please learn to strip long e-mails when
you're just replying to one specific of it :-)
On Sun, 17 Jan 2016 18:10:58 +0100, Maxime Hadjinlian wrote:
> > Not sure:
> >
> > cache.c: In function 'same_path':
> > cache.c:429:22: error: field 'fh' has incomplete type
> > cache.c:436:2: warning: implicit declaration of function 'name_to_handle_at' [-Wimplicit-function-declaration]
> > Makefile:613: recipe for target 'mountd-cache.o' failed
> >
> > Maxime, can you have a look ?
> I will look at it, the errors is a bit puzzling but I only glanced at
> it for now.
I had a look: nfs-utils does have some code to detect if
name_to_handle_at() is implemented. Unfortunately, as can be seen here,
using this function only triggers a warning (because its prototype is
not defined in any headers of the C library), but doesn't fail to link
(because for some reason the function is implemented). However the
"struct file_handle" type is not available.
So, I suggest to add:
AC_CHECK_TYPES([struct file_handle])
to configure.ac, and then change cache.c from
#if HAVE_NAME_TO_HANDLE_AT
to:
#if defined(HAVE_NAME_TO_HANDLE_AT) && defined(HAVE_STRUCT_FILE_HANDLE)
It works with the problematic PowerPC toolchains (i.e it properly
detects that struct file_handle is not available), but it remains to be
tested on another toolchain. Also, this fix should be submitted
upstream, obviously :-)
Care to do it ? :-)
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
^ permalink raw reply [flat|nested] 25+ messages in thread
* [Buildroot] [PATCH] zbar: Fix gcc5 logical-not-parentheses error
2016-01-16 23:11 ` [Buildroot] Analysis of build failures Thomas Petazzoni
` (9 preceding siblings ...)
2016-01-18 20:53 ` Peter Seiderer
@ 2016-01-19 9:54 ` Viacheslav Volkov
2016-01-19 10:16 ` Thomas Petazzoni
10 siblings, 1 reply; 25+ messages in thread
From: Viacheslav Volkov @ 2016-01-19 9:54 UTC (permalink / raw)
To: buildroot
^ permalink raw reply [flat|nested] 25+ messages in thread
* [Buildroot] [PATCH] zbar: Fix gcc5 logical-not-parentheses error
2016-01-19 9:54 ` [Buildroot] [PATCH] zbar: Fix gcc5 logical-not-parentheses error Viacheslav Volkov
@ 2016-01-19 10:16 ` Thomas Petazzoni
0 siblings, 0 replies; 25+ messages in thread
From: Thomas Petazzoni @ 2016-01-19 10:16 UTC (permalink / raw)
To: buildroot
Viacheslav,
Thanks for your patch!
On Tue, 19 Jan 2016 12:54:02 +0300, Viacheslav Volkov wrote:
> From b9dd5d73c19d2b7170f722dba61a99655487fe9c Mon Sep 17 00:00:00 2001
> From: Viacheslav Volkov <sv99@inbox.ru>
> Date: Tue, 19 Jan 2016 12:19:29 +0300
> Subject: [PATCH] zbar: Fix gcc5 logical-not-parentheses error
>
> Fix error: logical not is only applied to the left hand side of comparison
> [-Werror=logical-not-parentheses]
>
> Signed-off-by: Viacheslav Volkov <sv99@inbox.ru>
Are you sure this is the correct fix? Yes, it fixes the build issue,
but is it what the code intended to do?
> ---
> zbar/decoder/ean.c | 4 ++--
> zbar/qrcode/qrdec.c | 8 ++++----
> 2 files changed, 6 insertions(+), 6 deletions(-)
>
> diff --git a/zbar/decoder/ean.c b/zbar/decoder/ean.c
> index c20f538..fe38eaa 100644
> --- a/zbar/decoder/ean.c
> +++ b/zbar/decoder/ean.c
> @@ -294,7 +294,7 @@ static inline zbar_symbol_type_t ean_part_end4
> (ean_pass_t *pass,
> /* invalid parity combination */
> return(ZBAR_NONE);
>
> - if(!par == fwd) {
> + if(!(par == fwd)) {
Then par != fwd would be a lot simpler (and ditto below).
But did you analyze the code to make sure that this is actually the
right change?
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
^ permalink raw reply [flat|nested] 25+ messages in thread
* [Buildroot] Analysis of build failures
2016-01-17 16:33 ` Frank Hunleth
@ 2016-01-23 1:05 ` Frank Hunleth
2016-01-23 8:01 ` Thomas Petazzoni
0 siblings, 1 reply; 25+ messages in thread
From: Frank Hunleth @ 2016-01-23 1:05 UTC (permalink / raw)
To: buildroot
Hi Thomas and Johan,
On Sun, Jan 17, 2016 at 11:33 AM, Frank Hunleth
<fhunleth@troodon-software.com> wrote:
> Hi Thomas,
>
> On Sun, Jan 17, 2016 at 6:23 AM, Thomas Petazzoni
> <thomas.petazzoni@free-electrons.com> wrote:
>> Hello,
>>
>> On Sat, 16 Jan 2016 20:42:55 -0500, Frank Hunleth wrote:
>>
>>> > Frank, can you investigate why it builds on x86_64 but not on aarch64 ?
>>>
>>> I looked into this a little. My suspicion is that the atomic intrinsic
>>> macros in the Erlang code have not been ported to aarch64, but I'm
>>> having trouble following the code. I've inquired on the Erlang mailing
>>> list and will report back.
>
> It turns out that other people have gotten Erlang to work on aarch64
> without libatomic_ops installed. That doesn't work for Buildroot since
> other programs could depend on libatomic_ops. I've filed a bug against
> Erlang to track this at http://bugs.erlang.org/browse/ERL-78.
> Specifying '--disable-native-ethr-impls' to ./configure seems to
> workaround the issue, but I don't know if it has other consequences.
> Hopefully the Erlang maintainers will get to this sooner rather than
> later, but they're a pretty busy group.
I received further advice from the Erlang mailing list. The summary is:
1. Upgrade to Erlang 18 (BR is currently using 17.5)
2. Prefer the use of Erlang 18's native atomics implementation over
libatomic_ops.
I verified that upgrading to Erlang 18 and not using libatomic_ops
works for all qemu_*_defconfigs (with Erlang enabled), the aarch64
autobuilder failure, and a couple other configs. It does not work with
sparc_v8 as recently found with Erlang 17.5. I also tested whether
Erlang 18's configure scripts would choose libatomic_ops if it were
present, and they do not. This was tedious, so I am quite open to
others repeating the tests (or telling me to do so) if this does not
sound right. As a result of this testing, I disabled the use of
libatomic_ops for Erlang as you will see in a subsequent patch set.
Unfortunately, the upgrade to Erlang 18 was nontrivial due to a couple
major changes to the language and APIs. I had to bump the versions of
ejabberd and nearly all Erlang packages to fix this. While Erlang is
very important to me, I have never used the rebar infrastructure or
ejabberd. I verified that the new version of ejabberd compiles across
all qemu_*_defconfigs except the sparc_v8 one. I do not know if it
runs correctly, though. Johan - I cc'd you since I saw that you are
using ejabberd. Hopefully you can review too.
The patch set will follow shortly.
Frank
^ permalink raw reply [flat|nested] 25+ messages in thread
* [Buildroot] Analysis of build failures
2016-01-23 1:05 ` Frank Hunleth
@ 2016-01-23 8:01 ` Thomas Petazzoni
2016-01-25 9:06 ` Joris Lijssens
0 siblings, 1 reply; 25+ messages in thread
From: Thomas Petazzoni @ 2016-01-23 8:01 UTC (permalink / raw)
To: buildroot
Frank,
On Fri, 22 Jan 2016 20:05:01 -0500, Frank Hunleth wrote:
> I received further advice from the Erlang mailing list. The summary is:
>
> 1. Upgrade to Erlang 18 (BR is currently using 17.5)
> 2. Prefer the use of Erlang 18's native atomics implementation over
> libatomic_ops.
>
> I verified that upgrading to Erlang 18 and not using libatomic_ops
> works for all qemu_*_defconfigs (with Erlang enabled), the aarch64
> autobuilder failure, and a couple other configs. It does not work with
> sparc_v8 as recently found with Erlang 17.5. I also tested whether
> Erlang 18's configure scripts would choose libatomic_ops if it were
> present, and they do not. This was tedious, so I am quite open to
> others repeating the tests (or telling me to do so) if this does not
> sound right. As a result of this testing, I disabled the use of
> libatomic_ops for Erlang as you will see in a subsequent patch set.
>
> Unfortunately, the upgrade to Erlang 18 was nontrivial due to a couple
> major changes to the language and APIs. I had to bump the versions of
> ejabberd and nearly all Erlang packages to fix this. While Erlang is
> very important to me, I have never used the rebar infrastructure or
> ejabberd. I verified that the new version of ejabberd compiles across
> all qemu_*_defconfigs except the sparc_v8 one. I do not know if it
> runs correctly, though. Johan - I cc'd you since I saw that you are
> using ejabberd. Hopefully you can review too.
>
> The patch set will follow shortly.
Thanks a lot for working on this. Upgrading to Erlang 18 definitely
looks like a good thing.
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
^ permalink raw reply [flat|nested] 25+ messages in thread
* [Buildroot] Analysis of build failures
2016-01-23 8:01 ` Thomas Petazzoni
@ 2016-01-25 9:06 ` Joris Lijssens
2016-01-25 9:09 ` Thomas Petazzoni
0 siblings, 1 reply; 25+ messages in thread
From: Joris Lijssens @ 2016-01-25 9:06 UTC (permalink / raw)
To: buildroot
Hello thomas,
I had another look at the rabbitmq-c build issue this morning, but with the
latest buildroot version of this morning it builds just fine. Any idea what
has changed?
regards,
Joris
On 23 January 2016 at 09:01, Thomas Petazzoni <
thomas.petazzoni@free-electrons.com> wrote:
> Frank,
>
> On Fri, 22 Jan 2016 20:05:01 -0500, Frank Hunleth wrote:
>
> > I received further advice from the Erlang mailing list. The summary is:
> >
> > 1. Upgrade to Erlang 18 (BR is currently using 17.5)
> > 2. Prefer the use of Erlang 18's native atomics implementation over
> > libatomic_ops.
> >
> > I verified that upgrading to Erlang 18 and not using libatomic_ops
> > works for all qemu_*_defconfigs (with Erlang enabled), the aarch64
> > autobuilder failure, and a couple other configs. It does not work with
> > sparc_v8 as recently found with Erlang 17.5. I also tested whether
> > Erlang 18's configure scripts would choose libatomic_ops if it were
> > present, and they do not. This was tedious, so I am quite open to
> > others repeating the tests (or telling me to do so) if this does not
> > sound right. As a result of this testing, I disabled the use of
> > libatomic_ops for Erlang as you will see in a subsequent patch set.
> >
> > Unfortunately, the upgrade to Erlang 18 was nontrivial due to a couple
> > major changes to the language and APIs. I had to bump the versions of
> > ejabberd and nearly all Erlang packages to fix this. While Erlang is
> > very important to me, I have never used the rebar infrastructure or
> > ejabberd. I verified that the new version of ejabberd compiles across
> > all qemu_*_defconfigs except the sparc_v8 one. I do not know if it
> > runs correctly, though. Johan - I cc'd you since I saw that you are
> > using ejabberd. Hopefully you can review too.
> >
> > The patch set will follow shortly.
>
> Thanks a lot for working on this. Upgrading to Erlang 18 definitely
> looks like a good thing.
>
> Thanks,
>
> Thomas
> --
> Thomas Petazzoni, CTO, Free Electrons
> Embedded Linux, Kernel and Android engineering
> http://free-electrons.com
> _______________________________________________
> 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/20160125/baa12787/attachment.html>
^ permalink raw reply [flat|nested] 25+ messages in thread
* [Buildroot] Analysis of build failures
2016-01-25 9:06 ` Joris Lijssens
@ 2016-01-25 9:09 ` Thomas Petazzoni
2016-01-25 9:10 ` Joris Lijssens
0 siblings, 1 reply; 25+ messages in thread
From: Thomas Petazzoni @ 2016-01-25 9:09 UTC (permalink / raw)
To: buildroot
Joris,
On Mon, 25 Jan 2016 10:06:25 +0100, Joris Lijssens wrote:
> I had another look at the rabbitmq-c build issue this morning, but with the
> latest buildroot version of this morning it builds just fine. Any idea what
> has changed?
Can you remind me which rabbitmq-c failure you are investigating ?
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
^ permalink raw reply [flat|nested] 25+ messages in thread
* [Buildroot] Analysis of build failures
2016-01-25 9:09 ` Thomas Petazzoni
@ 2016-01-25 9:10 ` Joris Lijssens
2016-01-25 9:30 ` Joris Lijssens
0 siblings, 1 reply; 25+ messages in thread
From: Joris Lijssens @ 2016-01-25 9:10 UTC (permalink / raw)
To: buildroot
http://autobuild.buildroot.net/results/2ef/2ef1ed958db8012224f9174334e9c58edace604a/
On 25 January 2016 at 10:09, Thomas Petazzoni <
thomas.petazzoni@free-electrons.com> wrote:
> Joris,
>
> On Mon, 25 Jan 2016 10:06:25 +0100, Joris Lijssens wrote:
>
> > I had another look at the rabbitmq-c build issue this morning, but with
> the
> > latest buildroot version of this morning it builds just fine. Any idea
> what
> > has changed?
>
> Can you remind me which rabbitmq-c failure you are investigating ?
>
> Thanks,
>
> Thomas
> --
> Thomas Petazzoni, CTO, Free Electrons
> Embedded Linux, Kernel and Android engineering
> http://free-electrons.com
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20160125/1e31e53f/attachment.html>
^ permalink raw reply [flat|nested] 25+ messages in thread
* [Buildroot] Analysis of build failures
2016-01-25 9:10 ` Joris Lijssens
@ 2016-01-25 9:30 ` Joris Lijssens
0 siblings, 0 replies; 25+ messages in thread
From: Joris Lijssens @ 2016-01-25 9:30 UTC (permalink / raw)
To: buildroot
hey thomas,
used the wrong config file, sorry for that.
regards,
Joris
On 25 January 2016 at 10:10, Joris Lijssens <joris.lijssens@gmail.com>
wrote:
>
> http://autobuild.buildroot.net/results/2ef/2ef1ed958db8012224f9174334e9c58edace604a/
>
>
> On 25 January 2016 at 10:09, Thomas Petazzoni <
> thomas.petazzoni at free-electrons.com> wrote:
>
>> Joris,
>>
>> On Mon, 25 Jan 2016 10:06:25 +0100, Joris Lijssens wrote:
>>
>> > I had another look at the rabbitmq-c build issue this morning, but with
>> the
>> > latest buildroot version of this morning it builds just fine. Any idea
>> what
>> > has changed?
>>
>> Can you remind me which rabbitmq-c failure you are investigating ?
>>
>> Thanks,
>>
>> Thomas
>> --
>> Thomas Petazzoni, CTO, Free Electrons
>> Embedded Linux, Kernel and Android engineering
>> http://free-electrons.com
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20160125/9b23afe1/attachment.html>
^ permalink raw reply [flat|nested] 25+ messages in thread
end of thread, other threads:[~2016-01-25 9:30 UTC | newest]
Thread overview: 25+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2016-01-16 7:30 [Buildroot] [autobuild.buildroot.net] Build results for 2016-01-15 Thomas Petazzoni
2016-01-16 23:11 ` [Buildroot] Analysis of build failures Thomas Petazzoni
2016-01-17 1:42 ` Frank Hunleth
2016-01-17 11:23 ` Thomas Petazzoni
2016-01-17 16:33 ` Frank Hunleth
2016-01-23 1:05 ` Frank Hunleth
2016-01-23 8:01 ` Thomas Petazzoni
2016-01-25 9:06 ` Joris Lijssens
2016-01-25 9:09 ` Thomas Petazzoni
2016-01-25 9:10 ` Joris Lijssens
2016-01-25 9:30 ` Joris Lijssens
2016-01-17 15:06 ` Matthew Weber
2016-01-17 17:26 ` Thomas Petazzoni
2016-01-17 17:10 ` Maxime Hadjinlian
2016-01-18 22:10 ` Thomas Petazzoni
2016-01-17 17:36 ` Jörg Krause
2016-01-17 18:22 ` Rodrigo Rebello
2016-01-17 19:02 ` Gary Bisson
2016-01-17 19:06 ` Romain Naour
2016-01-18 7:06 ` Alexey Brodkin
2016-01-18 12:22 ` Gustavo Zacarias
2016-01-18 20:53 ` Peter Seiderer
2016-01-18 21:03 ` Thomas Petazzoni
2016-01-19 9:54 ` [Buildroot] [PATCH] zbar: Fix gcc5 logical-not-parentheses error Viacheslav Volkov
2016-01-19 10:16 ` Thomas Petazzoni
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.