Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: Christian Stewart <christian@paral.in>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v3 1/2] package/runc: add host package
Date: Thu, 27 Jan 2022 08:57:04 +0100	[thread overview]
Message-ID: <20220127085704.2192a320@windsurf> (raw)
In-Reply-To: <20220127062504.1835450-1-christian@paral.in>

Hello,

On Wed, 26 Jan 2022 22:25:03 -0800
Christian Stewart <christian@paral.in> wrote:

> diff --git a/package/runc/runc.mk b/package/runc/runc.mk
> index c4e45a00a9..932bf39eea 100644
> --- a/package/runc/runc.mk
> +++ b/package/runc/runc.mk
> @@ -10,6 +10,8 @@ RUNC_LICENSE = Apache-2.0
>  RUNC_LICENSE_FILES = LICENSE
>  RUNC_CPE_ID_VENDOR = linuxfoundation
>  
> +RUNC_GOMOD = github.com/opencontainers/runc

How is this related to  the addition of the host package? This seems
unrelated. Why is this needed now?

> +HOST_RUNC_BIN_NAME = runc

Why is this not needed for the target package ?

> +HOST_RUNC_LDFLAGS = $(RUNC_LDFLAGS)
> +HOST_RUNC_TAGS = $(RUNC_TAGS)
> +HOST_RUNC_INSTALL_BINS = $(HOST_RUNC_BIN_NAME)

This makes me think we should probably have some inheritance of those
variables between the target variant and the host variant of the
package.

However, HOST_RUNC_TAGS = $(RUNC_TAGS) looks most likely wrong. Indeed:

ifeq ($(BR2_PACKAGE_LIBAPPARMOR),y)
RUNC_DEPENDENCIES += libapparmor
RUNC_TAGS += apparmor
endif

ifeq ($(BR2_PACKAGE_LIBSECCOMP),y)
RUNC_TAGS += seccomp
RUNC_DEPENDENCIES += libseccomp host-pkgconf
endif

and you most likely don't want HOST_RUNC_TAGS to contain apparmor or
seccomp, because we are not building libseccomp or libapparmor for the
host.

Best regards,

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

      parent reply	other threads:[~2022-01-27  7:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-27  6:25 [Buildroot] [PATCH v3 1/2] package/runc: add host package Christian Stewart via buildroot
2022-01-27  6:25 ` [Buildroot] [PATCH v3 2/2] package/buildah: new package Christian Stewart via buildroot
2022-01-27  8:01   ` Thomas Petazzoni
2022-01-27 20:31     ` Christian Stewart via buildroot
2022-08-21 15:14       ` Yann E. MORIN
2022-08-21 17:05         ` Christian Stewart via buildroot
2022-01-27  7:57 ` Thomas Petazzoni [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=20220127085704.2192a320@windsurf \
    --to=thomas.petazzoni@bootlin.com \
    --cc=buildroot@buildroot.org \
    --cc=christian@paral.in \
    /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