From: Phil Blundell <philb@gnu.org>
To: Marcin Juszkiewicz <marcin.juszkiewicz@linaro.org>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/8] add fontcache.bbclass
Date: Thu, 07 Feb 2013 23:18:02 +0000 [thread overview]
Message-ID: <1360279082.6206.30.camel@x121e.pbcl.net> (raw)
In-Reply-To: <5113CA88.9020508@linaro.org>
On Thu, 2013-02-07 at 16:38 +0100, Marcin Juszkiewicz wrote:
>> +${@qemu_run_binary(d, '$D', '/usr/bin/fc-cache')} --sysroot=$D
>/dev/null 2>&1
> What about platform which do not have qemu support? Like AArch64...
There are other places in the oe-core tree that already require working
qemu support so I don't think this is a qualitatively new issue. I
suspect that in the long term, qemu is going to become another tool that
needs targetting to any new architecture, just like gcc, binutils,
glibc, linux, javascriptcore and so on.
On the other hand, that "/usr/bin" looks a bit unwholesome to me. :-}
p.
next prev parent reply other threads:[~2013-02-07 23:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-05 9:34 [PATCH 0/8] Generate fonts cache on host and other fixes Laurentiu Palcu
2013-02-05 9:34 ` [PATCH 1/8] add fontcache.bbclass Laurentiu Palcu
2013-02-07 15:38 ` Marcin Juszkiewicz
2013-02-07 22:43 ` Richard Purdie
2013-02-07 23:18 ` Phil Blundell [this message]
2013-02-05 9:34 ` [PATCH 2/8] add qemuwrapper-cross recipe Laurentiu Palcu
2013-02-05 9:34 ` [PATCH 3/8] qemu.bbclass: return qemuwrapper instead of qemu-allarch Laurentiu Palcu
2013-02-05 9:34 ` [PATCH 4/8] image.bbclass: add a proper error message if hook script fails Laurentiu Palcu
2013-02-05 9:34 ` [PATCH 5/8] fontconfig: add sysroot option to fc-cache and fc-cat Laurentiu Palcu
2013-02-05 9:35 ` [PATCH 6/8] liberation-fonts: use the new fontcache.bbclass Laurentiu Palcu
2013-02-05 9:35 ` [PATCH 7/8] package_ipk, rootfs_ipk: remove the "set -x" Laurentiu Palcu
2013-02-05 9:35 ` [PATCH 8/8] pulseaudio: do not postpone postinstall Laurentiu Palcu
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=1360279082.6206.30.camel@x121e.pbcl.net \
--to=philb@gnu.org \
--cc=marcin.juszkiewicz@linaro.org \
--cc=openembedded-core@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