On 2015-06-23 3:15 PM, Robert Calhoun wrote:
On 4/30/15 10:06 AM, Bruce Ashfield bruce.ashfi...@windriver.com wrote:
On 2015-04-30 08:27 AM, Schaumlöffel, Jan wrote:
What kernel recipe is used when your machine is set to 'astro' ?
Something custom ? Or have you added machine compatibility
On 4/30/15 10:06 AM, Bruce Ashfield bruce.ashfi...@windriver.com wrote:
On 2015-04-30 08:27 AM, Schaumlöffel, Jan wrote:
What kernel recipe is used when your machine is set to 'astro' ?
Something custom ? Or have you added machine compatibility to another
known kernel recipe ?
How would I
On Mon, May 11, 2015 at 3:06 PM, Bruce Ashfield
bruce.ashfi...@windriver.com wrote:
On 2015-05-11 02:10 PM, Brian Hutchinson wrote:
On Thu, Apr 30, 2015 at 10:06 AM, Bruce Ashfield
bruce.ashfi...@windriver.com wrote:
It is plausible. But in theory, linux-dummy should still provide
what you
On 2015-05-12 10:20 AM, Brian Hutchinson wrote:
On Mon, May 11, 2015 at 3:06 PM, Bruce Ashfield
bruce.ashfi...@windriver.com wrote:
On 2015-05-11 02:10 PM, Brian Hutchinson wrote:
On Thu, Apr 30, 2015 at 10:06 AM, Bruce Ashfield
bruce.ashfi...@windriver.com wrote:
It is plausible. But in
On Thu, Apr 30, 2015 at 10:06 AM, Bruce Ashfield
bruce.ashfi...@windriver.com wrote:
It is plausible. But in theory, linux-dummy should still provide
what you need (but since it doesn't build anything, there is
no abi .. and no modules can be built against it) .. so the
error isn't graceful.
On Mon, May 11, 2015 at 2:10 PM, Brian Hutchinson b.hutch...@gmail.com wrote:
On Thu, Apr 30, 2015 at 10:06 AM, Bruce Ashfield
bruce.ashfi...@windriver.com wrote:
It is plausible. But in theory, linux-dummy should still provide
what you need (but since it doesn't build anything, there is
no
On 2015-05-11 02:10 PM, Brian Hutchinson wrote:
On Thu, Apr 30, 2015 at 10:06 AM, Bruce Ashfield
bruce.ashfi...@windriver.com wrote:
It is plausible. But in theory, linux-dummy should still provide
what you need (but since it doesn't build anything, there is
no abi .. and no modules can be
That is really odd. I'll be interested to hear how that happened. I just did a
test and it points to where I expect:
[/home/bruc...poky/build] bitbake -e core-image-minimal | grep
STAGING_KERNEL_BUILDDIR # $STAGING_KERNEL_BUILDDIR
STAGING_KERNEL_BUILDDIR=/home/bruce/poky/build/tmp/work-
What kernel recipe is used when your machine is set to 'astro' ?
Something custom ? Or have you added machine compatibility to another
known kernel recipe ?
How would I see which kernel recipe is used?
I did not customize anything except for aforementioned steps, simply copied
On 2015-04-30 3:14 AM, Schaumlöffel, Jan wrote:
That is really odd. I'll be interested to hear how that happened. I just did a
test and it points to where I expect:
[/home/bruc...poky/build] bitbake -e core-image-minimal | grep
STAGING_KERNEL_BUILDDIR # $STAGING_KERNEL_BUILDDIR
On 2015-04-30 08:27 AM, Schaumlöffel, Jan wrote:
What kernel recipe is used when your machine is set to 'astro' ?
Something custom ? Or have you added machine compatibility to another
known kernel recipe ?
How would I see which kernel recipe is used?
This is where my brute force techniques
Have you tried setting linux-dummy as the preferred provider for the kernel
? That would skip the build processing doing anything more than satisfying
the various kernel dependencies.
Ah, that's a good hint, I'll try that.
After your build has failed, if you look in
I've just encountered the exact same issue upgrading.
Have you tried setting linux-dummy as the preferred provider for the kernel ?
That would skip the build processing doing anything more than satisfying the
various kernel dependencies.
We do explicitly set preferred provider to
On 04/29/2015 03:38 AM, Schaumlöffel, Jan wrote:
Have you tried setting linux-dummy as the preferred provider for the kernel
? That would skip the build processing doing anything more than satisfying
the various kernel dependencies.
Ah, that's a good hint, I'll try that.
After your build
I've just encountered the exact same issue upgrading.
Have you tried setting linux-dummy as the preferred provider for the kernel ?
That would skip the build processing doing anything more than satisfying the
various kernel dependencies.
We do explicitly set preferred provider to
On 2015-04-28 02:49 AM, Schaumlöffel, Jan wrote:
Hi everyone,
I have a working root fs based on “dizzy”, for which I created a
customized machine config, a custom package config recipe and a custom
image recipe.
When running into problems with the python installation on that rootfs I
decided
Hmmm. It shouldn't have gone missing. Bits of the kernel build outputs
did move around in 1.8, but the abiversion is still generated and
placed in the STAGING_KERNEL_BUILDDIR.
I was just wondering, is there an easy way to resolve these Paths from the
command line? I do not have a lot of
Hi everyone,
I have a working root fs based on dizzy, for which I created a customized
machine config, a custom package config recipe and a custom image recipe.
When running into problems with the python installation on that rootfs I
decided to upgrade to Poky 1.8 fido.
So I checked out the
18 matches
Mail list logo
