From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH] host-libcap: do not use setcap on itself
Date: Thu, 12 Jan 2017 09:24:48 +0100 [thread overview]
Message-ID: <20170112082448.mpjsmryqm4kpl2dg@pengutronix.de> (raw)
In-Reply-To: <20170111203321.7524-1-clemens.gruber@pqgruber.com>
On Wed, Jan 11, 2017 at 09:33:21PM +0100, Clemens Gruber wrote:
> Set RAISE_SETFCAP=no in host-libcap.make.
>
> Fixes an error in the install stage:
> unable to set CAP_SETFCAP effective capability: Operation not permitted
Thanks, applied. Not sure why you get this error and I don't. Maybe some
strange interaction of fakeroot and the underlying filesystem.
Michael
> Signed-off-by: Clemens Gruber <clemens.gruber@pqgruber.com>
> ---
> rules/host-libcap.make | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/rules/host-libcap.make b/rules/host-libcap.make
> index 0c753b8e4..251f2d56b 100644
> --- a/rules/host-libcap.make
> +++ b/rules/host-libcap.make
> @@ -19,6 +19,6 @@ HOST_PACKAGES-$(PTXCONF_HOST_LIBCAP) += host-libcap
> # ----------------------------------------------------------------------------
>
> HOST_LIBCAP_MAKE_OPT := prefix= PAM_CAP=no LIBATTR=no lib=lib
> -HOST_LIBCAP_INSTALL_OPT := $(HOST_LIBCAP_MAKE_OPT) install
> +HOST_LIBCAP_INSTALL_OPT := $(HOST_LIBCAP_MAKE_OPT) RAISE_SETFCAP=no install
>
> # vim: syntax=make
> --
> 2.11.0
>
>
> _______________________________________________
> ptxdist mailing list
> ptxdist@pengutronix.de
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2017-01-12 8:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-11 20:33 Clemens Gruber
2017-01-12 8:24 ` Michael Olbrich [this message]
2017-01-12 8:29 ` Michael Olbrich
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=20170112082448.mpjsmryqm4kpl2dg@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=ptxdist@pengutronix.de \
/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