From: "Maxin B. John" <maxin.john@intel.com>
To: Jianxun Zhang <jianxun.zhang@linux.intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 0/2][PROPOSED] libcap fix and update
Date: Thu, 8 Sep 2016 11:43:52 +0300 [thread overview]
Message-ID: <20160908084351.GA9057@mbabyjoh-desk.ger.corp.intel.com> (raw)
In-Reply-To: <1473284559-187471-1-git-send-email-jianxun.zhang@linux.intel.com>
Hi,
On Wed, Sep 07, 2016 at 02:42:37PM -0700, Jianxun Zhang wrote:
> Need some experts to review this patch series. I am not really
> sure for if what I fixed is a valid case or if fix is the best
> answer. The validation before submission is very limited too.
>
> I ran into the compiling issue when build an application and
> found this recipe cannot be built without specifying anything.
> I don't feel the existing options are passed to make with test,
> and guess EXTRA_CONF won't work with this makefile-based project.
>
> The second patch is a following-up when I saw there is another
> option in the similar situation and seems to be obsolete now.
>
> Jianxun Zhang (2):
> libcap: fix compiling issue when not having libpam
> libcap: remove dependency on attr
I think the libcap build fix is already in master branch now:
http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=b4f2c760aa4e9a92d5ce829136b60ab0ebed186c
Please use the latest master branch and see if you hit this error again.
> meta/recipes-support/libcap/libcap_2.25.bb | 11 +++--------
> 1 file changed, 3 insertions(+), 8 deletions(-)
Best Regards,
Maxin
prev parent reply other threads:[~2016-09-08 8:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-07 21:42 [PATCH 0/2][PROPOSED] libcap fix and update Jianxun Zhang
2016-09-07 21:42 ` [PATCH 1/2][PROPOSED] libcap: fix compiling issue when not having libpam Jianxun Zhang
2016-09-07 21:42 ` [PATCH 2/2][PROPOSED] libcap: remove dependency on attr Jianxun Zhang
2016-09-08 8:43 ` Maxin B. John [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=20160908084351.GA9057@mbabyjoh-desk.ger.corp.intel.com \
--to=maxin.john@intel.com \
--cc=jianxun.zhang@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