Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Tom Rini <tom_rini@mentor.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH, RFC] Add linux-libc-headers-native, make it default 	dep for native
Date: Tue, 15 Jun 2010 19:06:34 -0700	[thread overview]
Message-ID: <4C1831AA.1030005@mentor.com> (raw)
In-Reply-To: <AANLkTinZ-EFiDW6IK-bRPh9JElAbnwaET56jGKnwm0cr@mail.gmail.com>

Leon Woestenberg wrote:
> Hello Tom,
> 
> On Tue, Jun 15, 2010 at 7:48 PM, Tom Rini <tom_rini@mentor.com> wrote:
>> For the second, yes, ASSUME_PROVIDED still works.  For the first, I'd argue
>> that doing so is a lot harder (at least without some additional
>> infrastructure and reliance on other external tools) than just adding
>> another early package.
>>
>> So, yay or nay?
>>
> I would say the ASSUME_PROVIDED for the native linux headers should be
> mentioned in the local.conf.sample,
> commented out, so that users can enable it easily (optimize the build
> like Khem says).
> 
> Could you add that to the patch, or as a follow-up patch?

As a follow-up:
--- a/conf/local.conf.sample
+++ b/conf/local.conf.sample
@@ -30,6 +30,11 @@ BBFILES := "${@bb.fatal('Edit your conf/local.conf: 
BBFILES')}"
  # This is a regulary expression, so be sure to get your parenthesis 
balanced.
  BBMASK = ""

+# Uncomment this if your host distribution has recent enough Linux
+# Kernel header files.  Utilities we use to generate certain types of
+# target filesystems need somewhat recent header files.
+# ASSUME_PROVIDED += "linux-libc-headers-native"
+
  # Uncomment this if you want to use a prebuilt toolchain. You will need to
  # provide packages for toolchain and additional libraries yourself. 
You also
  # have to set PATH in your environment to make sure BitBake finds 
additional binaries.

-- 
Tom Rini
Mentor Graphics Corporation



  reply	other threads:[~2010-06-16  2:11 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-07 19:33 [PATCH, RFC] Add linux-libc-headers-native, make it default dep for native Tom Rini
2010-06-07 21:21 ` Khem Raj
2010-06-07 21:31   ` Chris Larson
2010-06-08  0:19     ` Khem Raj
2010-06-08  6:36 ` Frans Meulenbroeks
2010-06-08 14:04   ` Khem Raj
2010-06-08 14:36   ` Tom Rini
2010-06-09  6:45     ` Frans Meulenbroeks
2010-06-09 14:51       ` Tom Rini
2010-06-15 17:48 ` Tom Rini
2010-06-15 23:30   ` Leon Woestenberg
2010-06-16  2:06     ` Tom Rini [this message]
2010-06-16  7:36       ` Frans Meulenbroeks

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=4C1831AA.1030005@mentor.com \
    --to=tom_rini@mentor.com \
    --cc=openembedded-devel@lists.openembedded.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