From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: ChenQi <Qi.Chen@windriver.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/1] python-numpy: fix compile error for qemumips
Date: Wed, 26 Feb 2014 10:44:45 +0000 [thread overview]
Message-ID: <1393411485.31769.109.camel@ted> (raw)
In-Reply-To: <530DC059.5010608@windriver.com>
On Wed, 2014-02-26 at 18:22 +0800, ChenQi wrote:
> On 02/26/2014 06:02 PM, Burton, Ross wrote:
> > On 26 February 2014 07:33, Chen Qi <Qi.Chen@windriver.com> wrote:
> >> This is because for qemumips, there are no such files in SRC_URI. And
> >> actually we don't need such files. So for qemumips, the `cp' command
> >> is expected to fail.
> > Those files contain the definitions of things like word size and byte
> > ordering, so unless I've misunderstood the build process for numpy
> > what's happening with this patch is that it's using the host
> > environment.
> >
> > Ross
> >
> >
>
> Those files are there already.
> For archs like x86, we first replace them so that the build process
> doesn't fail (according to the comments in the recipe); but for
> mips/ppc, we don't need to do so, the build just succeeds.
>
> chenqi@pek-hostel-vm07:~/poky/build-qemumips64 [0] $ ls
> tmp/work/mips64-poky-linux/python-numpy/1.7.0-r1/numpy-1.7.0/build/src.linux-i686-2.7/numpy/core/include/numpy/
> config.h __multiarray_api.c __multiarray_api.h multiarray_api.txt
> _numpyconfig.h __ufunc_api.c __ufunc_api.h ufunc_api.txt
> __umath_generated.c
Ross' point stands, its just using the values from the host (build)
system. If your build system was mips it might stand a chance of
working, I suspect you're building on x86 though and x86 != mips.
Cheers,
Richard
next prev parent reply other threads:[~2014-02-26 10:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-26 7:33 [PATCH 0/1] python-numpy: fix compile error for qemumips Chen Qi
2014-02-26 7:33 ` [PATCH 1/1] " Chen Qi
2014-02-26 10:02 ` Burton, Ross
2014-02-26 10:22 ` ChenQi
2014-02-26 10:44 ` Richard Purdie [this message]
2014-02-27 3:25 ` ChenQi
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=1393411485.31769.109.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=Qi.Chen@windriver.com \
--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 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.