From: Koen Kooi <koen@dominion.thruhere.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] cairo: disable native atomic operations, conflicts with libatomics-ops
Date: Thu, 17 Mar 2011 15:47:38 +0100 [thread overview]
Message-ID: <ilt6ua$r2l$1@dough.gmane.org> (raw)
In-Reply-To: <20110317141220.GA16796@rhein.zuhause.netz>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 17-03-11 15:12, Henning Heinold wrote:
> Hi,
>
> I looked deeper into the problem.
> Cairo looks first for:
>
> return __sync_fetch_and_add
> __sync_val_compare_and_swap
>
> and defines it as cairo_cv_atomic_primitives="Intel".
>
> According to http://gcc.gnu.org/wiki/Atomic
> arm and sh3/4 should work too.
>
> If the configure compile fails
> cairo is looking for libatomic-ops
> support.
>
> The libatomic-ops in oe is very old and misses diffrent bug fixes and is only
> needed for ppc and mips.
Is there a new version released yet or do you mean debian/fedora/suse
bugfixes?
regards,
Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
iD8DBQFNgh8KMkyGM64RGpERAlJzAJ0b6sByXKXffddvKChK+FpL7Hu4ngCfcQwQ
ek1CXJV0RPVg0BNVudsCnl0=
=q81c
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2011-03-17 14:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-17 1:25 [PATCH] cairo: disable native atomic operations, conflicts with libatomics-ops Denys Dmytriyenko
2011-03-17 1:43 ` Denys Dmytriyenko
2011-03-17 3:25 ` Khem Raj
2011-03-17 7:37 ` Koen Kooi
2011-03-17 8:51 ` Henning Heinold
2011-03-17 14:12 ` Henning Heinold
2011-03-17 14:47 ` Koen Kooi [this message]
2011-03-17 17:18 ` Henning Heinold
2011-03-17 19:17 ` Denys Dmytriyenko
2011-03-17 21:36 ` Khem Raj
2011-03-17 22:00 ` Denys Dmytriyenko
2011-03-18 7:02 ` Esben Haabendal
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='ilt6ua$r2l$1@dough.gmane.org' \
--to=koen@dominion.thruhere.net \
--cc=openembedded-devel@lists.openembedded.org \
/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