Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: Paul Eggleton <paul.eggleton@linux.intel.com>,
	Khem Raj <raj.khem@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [RFC] kernel: Enable externalsrc on kernels which instantiate kernel.bbclass
Date: Mon, 22 Sep 2014 11:27:10 -0400	[thread overview]
Message-ID: <54203FCE.3080901@windriver.com> (raw)
In-Reply-To: <2251278.GaOGmN6XgQ@peggleto-mobl5.ger.corp.intel.com>

On 14-09-22 11:24 AM, Paul Eggleton wrote:
> On Thursday 06 February 2014 02:05:05 Khem Raj wrote:
>> This also make a change where for kernel
>> S != B, this is done because when S = B
>> and we use O= option or set KBUILD_OUTPUT
>> to point to objectdir, kernel build system
>> ends up denoting itself dirty and asking for
>> running mrproper during later build steps
>> after do_configure but works perfectly
>> for when S != B
>>
>> Additional fixes make sure that we do not
>> assume directory paths when accessing files
>>
>> Move exporting KBUILD_OUTPUT from kernel-yocto
>> into kernel class
>>
>> Signed-off-by: Khem Raj <raj.khem@gmail.com>
>
> So discussion on this patch seems to have stalled - did you guys make any
> progress offline?

I have an updated patch that I've been carrying in my tree ever
since.

>
> Looking over the patch I'd guess we'd want to try to avoid cd'ing and instead
> be explicit about the path where needed.

I have some more cleanups to this effect, and will send them post
1.7.

But the reports we've been getting have been that externalsrc
builds are working for kernels, and linux-yocto without the change
in place, so I'm looking to reduce the patch footprint and re-submit.

Bruce

>
> Cheers,
> Paul
>



  reply	other threads:[~2014-09-22 15:27 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-06 10:05 [RFC][PATCH] kernel: Enable externalsrc on kernels which instantiate kernel.bbclass Khem Raj
2014-02-06 13:38 ` Bruce Ashfield
2014-02-06 19:26 ` Bruce Ashfield
2014-02-06 19:36   ` Khem Raj
2014-09-22 15:24 ` [RFC] " Paul Eggleton
2014-09-22 15:27   ` Bruce Ashfield [this message]
2014-09-22 17:03     ` Khem Raj
2014-09-22 17:04       ` Bruce Ashfield
2014-12-03 12:00         ` Paul Eggleton
2014-12-03 12:23           ` Laurentiu Palcu
2014-12-03 13:14             ` Bruce Ashfield
2014-12-03 14:36               ` Paul Eggleton
2014-12-03 16:50                 ` Bruce Ashfield
2014-12-04  5:28                   ` Bruce Ashfield
2014-12-08 12:10                     ` Paul Eggleton
2014-12-08 14:32                       ` Bruce Ashfield
2014-12-03 13:12           ` Bruce Ashfield

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=54203FCE.3080901@windriver.com \
    --to=bruce.ashfield@windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=paul.eggleton@linux.intel.com \
    --cc=raj.khem@gmail.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