mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Frederick Gotham <cauldwell.thomas@gmail.com>
To: barebox@lists.infradead.org
Subject: Why the internal kernel header?
Date: Tue, 7 Jan 2020 09:36:29 -0000 (UTC)	[thread overview]
Message-ID: <XnsAB3D61BD490A1fgotham@195.159.176.226> (raw)


I'm using Barebox with Buildroot. Previously I was using Barebox version 
2018.12.0, and now I have upgraded to version 2019.12.0.

Barebox version 2019.12.0 won't compile for me with Buildroot, because the 
header "<linux/list.h>" is missing.

The reason why this header file is missing is that "list.h" is an internal 
kernel header file, rather than a userspace kernel header file.

I could try simply copying "list.h" into the appropriate directory in order 
to get Barebox to compile, but I'm not keen on doing that.

Does Barebox really need that header file, and if so, why?

Frederick


_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

             reply	other threads:[~2020-01-07  9:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-07  9:36 Frederick Gotham [this message]
2020-01-07 10:02 ` Sascha Hauer

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=XnsAB3D61BD490A1fgotham@195.159.176.226 \
    --to=cauldwell.thomas@gmail.com \
    --cc=barebox@lists.infradead.org \
    /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