From: Saul Wold <saul.wold@intel.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCHv2 0/3] Fix recipes to build with uclibc
Date: Fri, 20 May 2011 08:20:31 -0700 [thread overview]
Message-ID: <4DD686BF.5000606@intel.com> (raw)
In-Reply-To: <cover.1305849572.git.raj.khem@gmail.com>
On 05/19/2011 05:02 PM, Khem Raj wrote:
> This series addresses review from RP
>
> The following changes since commit bcf6445c5e77ab3563dc2dfa56d17ae811eb813d:
>
> opkg_svn.bb: Install rcS.d into ${D} instead of ${IMAGE_ROOTFS} (2011-05-19 16:56:45 -0700)
>
> are available in the git repository at:
> git@git.openembedded.org:openembedded-core-contrib.git kraj/uclibc
> http://cgit.openembedded.org/cgit.cgi//log/?h=kraj/uclibc
>
> Khem Raj (3):
> uclibc/site_config/funcs: getloadavg is unimplemented
Pulled
> distcc_2.18.3.bb: Fix compilation on uclibc
Not pulled - See Phil's comments
> nfs-utils_1.2.3.bb: Fix compile failure on uclibc
>
Pulled
Thanks
Sau!
> .../nfs-utils/nfs-utils-1.0.6-uclibc.patch | 16 +++++++-----
> .../nfs-utils/nfs-utils-1.2.3-uclibc-libio.h.patch | 26 ++++++++++++++++++++
> .../nfs-utils/nfs-utils_1.2.3.bb | 1 +
> meta/recipes-core/uclibc/site_config/funcs | 1 -
> meta/recipes-devtools/distcc/distcc_2.18.3.bb | 15 +++++++----
> 5 files changed, 46 insertions(+), 13 deletions(-)
> create mode 100644 meta/recipes-connectivity/nfs-utils/nfs-utils/nfs-utils-1.2.3-uclibc-libio.h.patch
>
prev parent reply other threads:[~2011-05-20 15:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-20 0:02 [PATCHv2 0/3] Fix recipes to build with uclibc Khem Raj
2011-05-20 0:02 ` [PATCHv2 1/3] uclibc/site_config/funcs: getloadavg is unimplemented Khem Raj
2011-05-20 0:02 ` [PATCHv2 2/3] distcc_2.18.3.bb: Fix compilation on uclibc Khem Raj
2011-05-20 7:03 ` Phil Blundell
2011-05-20 11:50 ` Richard Purdie
2011-05-20 0:02 ` [PATCHv3 3/3] nfs-utils_1.2.3.bb: Fix compile failure " Khem Raj
2011-05-20 15:20 ` 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=4DD686BF.5000606@intel.com \
--to=saul.wold@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