From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/tpm2-tss: needs host-acl
Date: Mon, 18 Oct 2021 22:34:58 +0200 [thread overview]
Message-ID: <20211018223458.6d52ee5e@windsurf> (raw)
In-Reply-To: <20211013065446.1857356-1-fontaine.fabrice@gmail.com>
On Wed, 13 Oct 2021 08:54:46 +0200
Fabrice Fontaine <fontaine.fabrice@gmail.com> wrote:
> Add host-acl mandatory dependency for setfacl to avoid the following
> build failure since bump to version 3.1.0 in commit
> 470e2e9bc5211184431fbc868359a9d695e624f4 and
> https://github.com/tpm2-software/tpm2-tss/commit/9d42f4dbde6a94724e95d57c333cda7711dda57c:
So this commit adds:
# Check all tools used by make install
AS_IF([test "$HOSTOS" = "Linux"],
[ERROR_IF_NO_PROG([groupadd])
ERROR_IF_NO_PROG([useradd])
ERROR_IF_NO_PROG([id])
ERROR_IF_NO_PROG([chown])
ERROR_IF_NO_PROG([chmod])
ERROR_IF_NO_PROG([mkdir])
ERROR_IF_NO_PROG([setfacl])])
But in the context of Buildroot, using groupadd, useradd, chown, chmod,
setfacl at install time cannot work, since we're not doing "make
install" as root.
So are we sure that adding host-acl as a dependency to get a host
variant of setfacl is really the good solution?
How is it handled for groupadd/useradd/chown/chmod today ?
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2021-10-18 20:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-13 6:54 [Buildroot] [PATCH 1/1] package/tpm2-tss: needs host-acl Fabrice Fontaine
2021-10-18 20:34 ` Thomas Petazzoni [this message]
2021-10-19 21:28 ` Fabrice Fontaine
2021-11-06 14:56 ` Yann E. MORIN
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=20211018223458.6d52ee5e@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@buildroot.org \
--cc=fontaine.fabrice@gmail.com \
/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