Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Darren Hart <dvhart@linux.intel.com>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Cc: Paul Eggleton <paul.eggleton@linux.intel.com>
Subject: Re: [PATCH 6/6] linux-yocto-tiny: add dependency on xz-native
Date: Wed, 14 Mar 2012 07:55:21 -0700	[thread overview]
Message-ID: <4F60B159.6010809@linux.intel.com> (raw)
In-Reply-To: <CADkTA4OjJgjGHVPB-qCFcrVyUXBoBApfmK+NCiAa8t9tH=ce9w@mail.gmail.com>



On 03/14/2012 06:12 AM, Bruce Ashfield wrote:
> On Wed, Mar 14, 2012 at 9:03 AM, Paul Eggleton
> <paul.eggleton@linux.intel.com> wrote:
>> On Wednesday 14 March 2012 08:59:34 Bruce Ashfield wrote:
>>> You could audit the constructed .config as well, since that's the final word
>>> on whether it actually makes it into the kernel build, but also not really
>>> required here.
>>
>> This is what I wanted to do, but I'm assuming the config construction happens
>> far too late to add the dependency.
> 
> Hmm. probably, I admit to not looking too deeply while trying to get enough
> coffee into my system to properly think :)

Paul is correct here. He would have to wait until kernel_configme
completes before he could be sure that LZMA was needed. Adding to
specific recipes is the best approach in this case.

-- 
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel



  reply	other threads:[~2012-03-14 15:04 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-14  0:36 [PATCH 0/6] Misc build failure fixes Paul Eggleton
2012-03-14  0:36 ` [PATCH 1/6] scripts/bitbake: ensure user is in build directory Paul Eggleton
2012-03-14 14:52   ` Darren Hart
2012-03-14 15:09     ` Paul Eggleton
2012-03-14 15:19       ` Darren Hart
2012-03-15  0:30   ` Andreas Oberritter
2012-03-15 23:09     ` Paul Eggleton
2012-03-16  0:20       ` Andreas Oberritter
2012-03-16 10:56         ` Paul Eggleton
2012-03-16 11:55           ` VIJAY KUMAR
2012-03-16 12:19             ` Paul Eggleton
2012-03-18 15:07           ` Andreas Oberritter
2012-04-02 20:00   ` Khem Raj
2012-04-02 20:12     ` Paul Eggleton
2012-04-02 20:32       ` Chris Larson
2012-04-02 20:56         ` Paul Eggleton
2012-03-14  0:36 ` [PATCH 2/6] pulseaudio: add X library dependencies Paul Eggleton
2012-03-14  0:36 ` [PATCH 3/6] gst-plugins-bad: disable directfb in configure Paul Eggleton
2012-03-14  0:36 ` [PATCH 4/6] mx: add dependencies Paul Eggleton
2012-03-14  0:36 ` [PATCH 5/6] ncurses: fix build when ENABLE_WIDEC is not set Paul Eggleton
2012-03-14 14:52   ` Darren Hart
2012-03-14  0:36 ` [PATCH 6/6] linux-yocto-tiny: add dependency on xz-native Paul Eggleton
2012-03-14  8:21   ` Koen Kooi
2012-03-14  8:32     ` Paul Eggleton
2012-03-14 12:29       ` Bruce Ashfield
2012-03-14 12:39         ` Paul Eggleton
2012-03-14 12:59           ` Bruce Ashfield
2012-03-14 13:03             ` Paul Eggleton
2012-03-14 13:12               ` Bruce Ashfield
2012-03-14 14:55                 ` Darren Hart [this message]
2012-03-14 13:18 ` [PATCH 0/6] Misc build failure fixes Richard Purdie

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=4F60B159.6010809@linux.intel.com \
    --to=dvhart@linux.intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=paul.eggleton@linux.intel.com \
    /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