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] mklibs-native 0.1.33: include unistd.h to fix build for gcc 4.7
Date: Fri, 13 Apr 2012 15:26:06 -0700 [thread overview]
Message-ID: <4F88A7FE.4070703@linux.intel.com> (raw)
In-Reply-To: <cover.1334238048.git.liezhi.yang@windriver.com>
On 04/12/2012 06:43 AM, Robert Yang wrote:
> Test info:
> Has been tested on:
> Fedora 17 64bit
> Fedora 16 64bit
> Ubuntu 10.10 32bit
>
> // Robert
>
> The following changes since commit c37faea947ef3980934c02661ecd79cd9668b8a6:
>
> libunistring: Fix parallel make issue (2012-04-12 12:37:52 +0100)
>
> are available in the git repository at:
> git://git.pokylinux.org/poky-contrib robert/mklibs
> http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=robert/mklibs
>
> Robert Yang (1):
> mklibs-native 0.1.33: include unistd.h to fix build for gcc 4.7
>
> .../mklibs/files/include-unistd.h-for-gcc47.patch | 29 ++++++++++++++++++++
> .../mklibs/mklibs-native_0.1.33.bb | 3 +-
> 2 files changed, 31 insertions(+), 1 deletions(-)
> create mode 100644 meta/recipes-devtools/mklibs/files/include-unistd.h-for-gcc47.patch
>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>
Merged with Updated Patch Header as it's a back port
Thanks
Sau!
prev parent reply other threads:[~2012-04-13 22:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-12 13:43 [PATCH 0/1] mklibs-native 0.1.33: include unistd.h to fix build for gcc 4.7 Robert Yang
2012-04-12 13:43 ` [PATCH 1/1] " Robert Yang
2012-04-13 22:26 ` 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=4F88A7FE.4070703@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 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.