All of lore.kernel.org
 help / color / mirror / Atom feed
From: Khem Raj <raj.khem@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH, RFC] Add linux-libc-headers-native, make it default dep for native
Date: Mon, 7 Jun 2010 17:19:41 -0700	[thread overview]
Message-ID: <20100608001941.GA26738@gmail.com> (raw)
In-Reply-To: <AANLkTil27vjcFzRuEIAZp6rEYY7xq2_ozqdU_QdjtEWI@mail.gmail.com>

On (07/06/10 14:31), Chris Larson wrote:
> On Mon, Jun 7, 2010 at 2:21 PM, Khem Raj <raj.khem@gmail.com> wrote:
> 
> > On Mon, Jun 7, 2010 at 12:33 PM, Tom Rini <tom_rini@mentor.com> wrote:
> > > On some host distributions the provided linux kernel headers are too old
> > > to compile utilities we need[1].  Given that we need these utilities to
> > > run things on the target the best solution is to provide
> > > linux-libc-headers-native.  Rather than get things into an inconsistent
> > > state, we make linux-libc-headers-native be a default dependency.
> >
> > could it be made optional so people who use distribution where this is not
> > needed are not penalized.
> >
> 
> You mean like ASSUME_PROVIDED += "linux-libc-headers-native"?

heh sure,I had that in mind but I was thinking if it was otherway around
where the distros which new these headers have to specify to include them
and not the ones which already have them.


> -- 
> Christopher Larson
> clarson at kergoth dot com
> Founder - BitBake, OpenEmbedded, OpenZaurus
> Maintainer - Tslib
> Senior Software Engineer, Mentor Graphics
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel



  reply	other threads:[~2010-06-08  0:24 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 [this message]
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
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=20100608001941.GA26738@gmail.com \
    --to=raj.khem@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.