Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: James Hilliard <james.hilliard1@gmail.com>
Cc: "Yann E . MORIN" <yann.morin.1998@free.fr>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/2] package/linux-headers: enable host build
Date: Tue, 28 Dec 2021 23:33:14 +0100	[thread overview]
Message-ID: <20211228233314.7dfb8575@windsurf> (raw)
In-Reply-To: <20210810064547.2579380-1-james.hilliard1@gmail.com>

Hello James,

On Tue, 10 Aug 2021 00:45:46 -0600
James Hilliard <james.hilliard1@gmail.com> wrote:

> This will be used for building tools that are included with the kernel,
> such as host-bpftool.
> 
> Signed-off-by: James Hilliard <james.hilliard1@gmail.com>

I'm sorry, but I fail to see how this can make sense, for a number of
reasons:

 * For external toolchains, package/linux-headers/Config.in.host is not
   even included, which means that no version of kernel headers are
   defined.

 * Even for internal toolchains, the kernel headers version selected
   for the target, which you re-use here for the host kernel headers,
   has no correlation with the actual kernel running on the build
   machine. If you are running an oldish 3.10 kernel on your build
   machine, install host-linux-headers 5.15, and build host-bpftool
   based on that, you'll run into issue.

So, perhaps the first thing is to figure out why the host variant of
bpftool needs kernel headers. What are these tool doing on the host?
What is the use case?

Then if we really want to build them for the host, I guess the only
solution is to ask the user to install the kernel headers matching their
build machine (so with some hidden option
BR2_NEEDS_HOST_KERNEL_HEADERS, which is selected by your package, and
then with logic in support/dependencies/ to check that).

Thanks!

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:[~2021-12-28 22:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-10  6:45 [Buildroot] [PATCH 1/2] package/linux-headers: enable host build James Hilliard
2021-08-10  6:45 ` [Buildroot] [PATCH 2/2] package/linux-tools: add host-bpftool support James Hilliard
2021-12-28 22:33 ` Thomas Petazzoni [this message]
2022-01-31  2:22   ` [Buildroot] [PATCH 1/2] package/linux-headers: enable host build James Hilliard

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=20211228233314.7dfb8575@windsurf \
    --to=thomas.petazzoni@bootlin.com \
    --cc=buildroot@buildroot.org \
    --cc=james.hilliard1@gmail.com \
    --cc=yann.morin.1998@free.fr \
    /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