From: Saul Wold <sgw@linux.intel.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 0/1] nspr 4.8.9: failed to build on x86_64 board
Date: Tue, 03 Apr 2012 15:36:27 -0700 [thread overview]
Message-ID: <4F7B7B6B.8090202@linux.intel.com> (raw)
In-Reply-To: <cover.1332839233.git.liezhi.yang@windriver.com>
On 03/27/2012 02:37 AM, Robert Yang wrote:
> * The test info, tested on:
> -> The hosts are:
> Fedora 16 64bit, Ubuntu 10.10 32bit
> -> The MACHINEs are:
> qemux86, qemux86-64 and qemuarm
>
> // Robert
>
> The following changes since commit d3e0beed9eef53018158c9f999cd20b44629aa61:
>
> guile: Deal with hardcoded path issues (2012-03-27 00:29:00 +0100)
>
> are available in the git repository at:
> git://git.pokylinux.org/poky-contrib robert/nspr
> http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=robert/nspr
>
> Robert Yang (1):
> nspr 4.8.9: failed to build on x86_64 board
>
> .../nspr/files/fix-build-on-x86_64.patch | 51 ++++++++++++++++
> .../nspr/files/trickly-fix-build-on-x86_64.patch | 62 ++++++++++++++++++++
> meta/recipes-support/nspr/nspr_4.8.9.bb | 4 +-
> 3 files changed, 116 insertions(+), 1 deletions(-)
> create mode 100644 meta/recipes-support/nspr/files/fix-build-on-x86_64.patch
> create mode 100644 meta/recipes-support/nspr/files/trickly-fix-build-on-x86_64.patch
>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>
Merged into OE-Core
Thanks
Sau!
prev parent reply other threads:[~2012-04-03 22:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-27 9:37 [PATCH 0/1] nspr 4.8.9: failed to build on x86_64 board Robert Yang
2012-03-27 9:37 ` [PATCH 1/1] " Robert Yang
2012-04-03 22:36 ` Saul Wold [this message]
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=4F7B7B6B.8090202@linux.intel.com \
--to=sgw@linux.intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox