Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Laurentiu Palcu <laurentiu.palcu@intel.com>
To: Paul Eggleton <paul.eggleton@linux.intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [RFC] kernel: Enable externalsrc on kernels which instantiate kernel.bbclass
Date: Wed, 3 Dec 2014 14:23:07 +0200	[thread overview]
Message-ID: <20141203122307.GB15731@lpalcu-linux> (raw)
In-Reply-To: <2558455.kgL2mNBB1h@peggleto-mobl5.ger.corp.intel.com>

Hi Paul,

On Wed, Dec 03, 2014 at 12:00:31PM +0000, Paul Eggleton wrote:
> On Monday 22 September 2014 13:04:47 Bruce Ashfield wrote:
> > On 14-09-22 01:03 PM, Khem Raj wrote:
> > > On Mon, Sep 22, 2014 at 8:27 AM, Bruce Ashfield
> > > 
> > > <bruce.ashfield@windriver.com> wrote:
> > >> 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.
> > > 
> > > no, it cant work if folks were trying the usecase I have mentioned.
> > > The fix is infact for
> > > non linux-yocto kernels.
> > 
> > I'll send out my updated patch shortly, it should fix both cases.
> 
> Bruce, did you get around to doing this?
> 
> At the moment I am trying to make my workflow tool ("devtool modify") work with 
> linux-yocto. I've at least got to the point where I can extract the 
> appropriate source from the recipe, but when I use externalsrc to point to it 
> and then try to build it, it doesn't even get past do_configure, so something 
> must be missing (make complains about missing targets, presumably because it's 
> running in ${B} and there's nothing in that directory).
> 
> Do you expect linux-yocto + externalsrc to work at the moment in master? If 
> so, are there any special steps I need to do with respect to preparing the 
> external source tree that my tool might not be performing?
FWIW, I'm using externalsrc to build non linux-yocto kernels but, to make it
work, I had to overwrite the KERNEL_CONFIG_COMMAND:

KERNEL_CONFIG_COMMAND = "oe_runmake_call -C ${S} O=${B} oldnoconfig || yes '' | oe_runmake -C ${S} O=${B} oldconfig"

This might be the reason of your do_configure failure...

I hope it helps,
laurentiu



  reply	other threads:[~2014-12-03 12:23 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
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 [this message]
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=20141203122307.GB15731@lpalcu-linux \
    --to=laurentiu.palcu@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