From: Phil Blundell <philb@gnu.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH 2/3] cairo.inc: let arm, mips and ppc depend on libatomic-ops
Date: Wed, 23 Mar 2011 10:21:50 +0000 [thread overview]
Message-ID: <1300875710.2228.117.camel@phil-desktop> (raw)
In-Reply-To: <20110322173047.GA10685@rhein.zuhause.netz>
On Tue, 2011-03-22 at 18:30 +0100, Henning Heinold wrote:
> but how do you will filter it? We have no versions dep in bitbake.
You could arrange for gcc-cross 4.5 (and later) to PROVIDE
virtual/atomic-ops or some such.
p.
next prev parent reply other threads:[~2011-03-23 10:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-22 8:01 Attempt to fix libatomic-ops heinold
2011-03-22 8:01 ` [PATCH 1/3] libatomic-ops: switch to own directroy and use cvs version heinold
2011-03-22 8:19 ` Koen Kooi
2011-03-22 9:00 ` Henning Heinold
2011-03-22 9:05 ` Martin Jansa
2011-03-22 9:05 ` Koen Kooi
2011-03-22 8:01 ` [PATCH 2/3] cairo.inc: let arm, mips and ppc depend on libatomic-ops heinold
2011-03-22 8:31 ` Paul Menzel
2011-03-22 9:07 ` Koen Kooi
2011-03-22 17:19 ` Khem Raj
2011-03-22 17:30 ` Henning Heinold
2011-03-22 18:14 ` Khem Raj
2011-03-23 10:21 ` Phil Blundell [this message]
2011-03-22 8:01 ` [PATCH 3/3] pulseaudio.inc: " heinold
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=1300875710.2228.117.camel@phil-desktop \
--to=philb@gnu.org \
--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