Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] Header is nine years old
Date: Mon, 6 Jan 2020 21:33:17 +0100	[thread overview]
Message-ID: <20200106213317.693ae331@windsurf> (raw)
In-Reply-To: <XnsAB3CA67D5979Efgotham@195.159.176.226>

Hello Frederick,

On Mon, 6 Jan 2020 16:21:59 -0000 (UTC)
Frederick Gotham <cauldwell.thomas@gmail.com> wrote:

> The following header file:
> 
>     #include <linux/list.h>
> 
> was added to the Github for the Linux kernel in May 2011. That was 9 years 
> ago.

This is an internal kernel header.

> So on my Buildroot setup, I navigate to this directory:
> 
>     build/output/host/x86_64-buildroot-linux-gnu/sysroot/usr/include/linux

This only contains the kernel headers exposed to userspace, i.e the
UAPI (user-space API). There is absolutely no reason for list.h to be
in there.

> And I check to see if "list.h" is in there. It's not there, and this is why I 
> am unable to build the latest version of Barebox.
> 
> Anyone got any idea why that header file isn't in there?

You need to give more details about the Barebox failure you're seeing:
which version you're trying to build, what is the build error. But the
error is clearly not due to <linux/list.h> being missing from the
compiler sysroot.

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

  reply	other threads:[~2020-01-06 20:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-06 16:21 [Buildroot] Header is nine years old Frederick Gotham
2020-01-06 20:33 ` Thomas Petazzoni [this message]
2020-01-07  8:28   ` Frederick Gotham
2020-01-07  9:39     ` Peter Seiderer
2020-01-07 17:30       ` Peter Seiderer
2020-01-07 19:36         ` Peter Seiderer

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=20200106213317.693ae331@windsurf \
    --to=thomas.petazzoni@bootlin.com \
    --cc=buildroot@busybox.net \
    /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