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 08:37:07 +0100 [thread overview]
Message-ID: <ilsdn3$dg5$1@dough.gmane.org> (raw)
In-Reply-To: <4D817F36.30900@gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 17-03-11 04:25, Khem Raj wrote:
> On 3/16/2011 6:43 PM, Denys Dmytriyenko wrote:
>> An alternative solution, is to build libatomics-ops with emulated CAS
>> (Compare
>> And Swap), as otherwise those non-emulated primitives are not
>> available on
>> armel and sparc, according to [1]
>>
>> Let me know if fixing libatomics-ops is more preferable and I'll make
>> a patch.
>> But I figured that since cairo used to build w/o atomic ops anyway,
>> it's safer
>> to just forcefully disable the check for them.
>
> I am inclined to get the libatomic-ops if possible.
Yes, me too
>
>>
>> [1]
>> http://us.generation-nt.com/answer/bug-566850-ao-compare-swap-full-not-available-armel-sparc-help-169012241.html
>>
>>
>> BTW, the correct name is libatomic-ops and not libatomics-ops, like
>> it's named
>> in OE...
>>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
iD8DBQFNgbojMkyGM64RGpERAjL9AJ9VS80ebM6fnzCAusGTYRXp4p6E9wCfchxY
QgG4eqdx70cqeSWwD0CP7o8=
=+AU8
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2011-03-17 7:39 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 [this message]
2011-03-17 8:51 ` Henning Heinold
2011-03-17 14:12 ` Henning Heinold
2011-03-17 14:47 ` Koen Kooi
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='ilsdn3$dg5$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 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.