From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] Analysis of build results for 2015-11-18
Date: Fri, 20 Nov 2015 12:29:49 -0300 [thread overview]
Message-ID: <564F3C6D.8080502@zacarias.com.ar> (raw)
In-Reply-To: <20151120001552.51c1b21b@free-electrons.com>
On 19/11/15 20:15, Thomas Petazzoni wrote:
>> powerpc | kompexsqlite-v1.10.12-1 | NOK | http://autobuild.buildroot.net/results/ec82752a6b20ed92beb703f68f591faf27b7724e/
>> powerpc | kompexsqlite-v1.10.12-1 | NOK | http://autobuild.buildroot.net/results/763d9aff86085b67077fc665e462cee81962246d/
>
> Smells like wchar support is needed. Gustavo, can you have a look ?
>
> BTW, it seems like this package also needs thread support, according to
> http://autobuild.buildroot.org/results/ed4/ed410283871926f61175326dc7f2b48fee9038b9/build-end.log.
> Would be good to fix this at the same time.
Hi, yes, it needs both.
For wchar it's mandatory, for threads it could be optional but isn't
because the default for sqlite (bundled) is threads on for *nixes and
the decision can be changed from configure (which is missing).
It's probably not worth the effort/testing to make them optional.
>> powerpc | libgtk3-3.14.15 | NOK | http://autobuild.buildroot.net/results/aae4266c16189b295cc7ceb60000c504ebb60752/
>
> gdkwindow-wayland.c:50:34: error: redefinition of typedef 'GdkWaylandWindow'
> ../../gdk/wayland/gdkwaylandwindow.h:32:34: note: previous declaration of 'GdkWaylandWindow' was here
>
> libgtk3 is for Gustavo :-)
I already have a bump to 3.18 in the pipe.
For now i'd say ignore this, even if it builds it doesn't work at
runtime since the wayland/weston xdg api level != gtk3.
This happened when wayland/westion were bumped, the API level was raised
with it, but gtk3 wasn't, hence it's in a previous level.
Mental note for the future: wayland/weston bumps may be tied to gtk3.
The gtk3 bump isn't 100% clean right now (WIP) and tinkers somewhat
heavily in other packages, so it's material for the 2016.02 release.
Unfortunately this means we'll ship a known-broken combo (gtk3 with
wayland).
>> microblazeel | mesa3d-11.0.4 | NOK | http://autobuild.buildroot.net/results/5b50695350b48cff6ac2eecd4cf9d7b2fb5c1beb/
>
> ./.libs/libglsl.a(glsl_parser_extras.o): In function `_mesa_glsl_compile_shader':
> (.text+0x3588): undefined reference to `__sync_val_compare_and_swap_1'
>
> I'm tempted to simply mark mesa3d as not available on microblaze. Bernd, any suggestion?
This is in the bag of "arch needs libatomic" together with strongswan
for microblaze.
>> sparc | mpd-0.19.11 | NOK | http://autobuild.buildroot.net/results/8dcf5f73904de835bf66c46747cd544efc9d3a22/
>
> undefined reference to `__atomic_fetch_or_4'
>
> Waldemar, can you have a look ?
SPARC (v8, 32 bits) doesn't have atomics at all, libatomic, again could
fit the bill. It may be inherited from somewhere else like boost.
Regards.
next prev parent reply other threads:[~2015-11-20 15:29 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-19 7:30 [Buildroot] [autobuild.buildroot.net] Build results for 2015-11-18 Thomas Petazzoni
2015-11-19 23:15 ` [Buildroot] Analysis of build " Thomas Petazzoni
2015-11-20 0:17 ` Ryan Barnett
2015-11-20 15:29 ` Gustavo Zacarias [this message]
2015-11-20 15:45 ` Thomas Petazzoni
2015-11-22 7:53 ` Waldemar Brodkorb
2015-11-20 21:01 ` Alexey Brodkin
2015-11-24 12:10 ` Alexey Brodkin
2015-11-20 22:26 ` Arnout Vandecappelle
2015-11-21 8:23 ` Thomas Petazzoni
2015-11-21 21:14 ` Arnout Vandecappelle
2015-11-21 14:45 ` Martin Bark
2015-11-21 22:17 ` Arnout Vandecappelle
2015-11-22 18:31 ` Martin Bark
2015-11-23 6:22 ` Rodrigo Rebello
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=564F3C6D.8080502@zacarias.com.ar \
--to=gustavo@zacarias.com.ar \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox