From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] libproxy: Fix build errors due to missing prototypes
Date: Thu, 01 Mar 2012 23:16:02 +0000 [thread overview]
Message-ID: <1330643762.14819.4.camel@ted> (raw)
In-Reply-To: <1330625283-14582-1-git-send-email-raj.khem@gmail.com>
On Thu, 2012-03-01 at 10:08 -0800, Khem Raj wrote:
> g++ really does not like the missing prototypes
> here we were missing close() and read() so include
> unistd.h to get them
>
> Signed-off-by: Khem Raj <raj.khem@gmail.com>
> ---
> .../libproxy/libproxy/g++-namepace.patch | 22 ++++++++++++++++++++
> meta/recipes-support/libproxy/libproxy_0.4.7.bb | 6 +++-
> 2 files changed, 26 insertions(+), 2 deletions(-)
> create mode 100644 meta/recipes-support/libproxy/libproxy/g++-namepace.patch
Merged to master, thanks.
Richard
prev parent reply other threads:[~2012-03-01 23:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-01 18:08 [PATCH] libproxy: Fix build errors due to missing prototypes Khem Raj
2012-03-01 23:16 ` Richard Purdie [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=1330643762.14819.4.camel@ted \
--to=richard.purdie@linuxfoundation.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