From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: "\"Schaumlöffel, Jan\"" <J.Schaumloeffel@astro-kom.de>,
"yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: Migration from 1.7.1 to 1.8 - kernel-abiversion missing
Date: Thu, 30 Apr 2015 08:18:42 -0400 [thread overview]
Message-ID: <55421DA2.9060909@windriver.com> (raw)
In-Reply-To: <a01714e680f8470cb21bb0b52e66c91e@ASTRO-EX1.Bensberg.de>
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
>> STAGING_KERNEL_BUILDDIR="/home/bruce/poky/build/tmp/work-
>> shared/qemux86-64/kernel-build-artifacts"
>>
>
> So I experimented a bit more and found a minimal set of steps to reproduce the problem. Maybe that might give someone a clue as to what is happening and/or how to resolve it.
>
> Steps to reproduce:
>
> - clone Poky repository, checkout branch 'fido'
> - go to meta-yocto-bsp/conf/machine and copy beaglebone.conf to another file (I used astro.conf)
> - from poky repository do source oe-init-build-env into new build directory
> - edit conf/local.conf to set MACHINE ?= "astro" (use filename from second step) and DL_DIR (if present)
> - run bitbake core-image-minimal
>
> -> kernel-abiversion is missing, build fails
>
> - edit conf/local.conf, set MACHINE ?= "beaglebone"
> - run bitbake core-image-minimal
>
> -> image builds fine
>
> It stays the same if the copied config is in a custom BSP layer, some minor modifications are made, etc., but to eliminate complexity I just put that into the meta-yocto-bsp layer. What strikes me as really odd is that now the only thing changed between working and non-working configuration seems to be the filename of the machine configuration - what am I missing?
>
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 ?
The big difference that I see would be the kernel recipe, and
some of the tasks not executing (and hence not generating the
abiversion file).
Bruce
> How do I create a working machine configuration for Poky 1.8? (In 1.7.1 I just took some machine configuration from eldk, fiddled around with it a bit, put it into my BSP layer and never had any trouble with that.)
>
> Regards,
> Jan
>
next prev parent reply other threads:[~2015-04-30 12:18 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-28 6:49 Migration from 1.7.1 to 1.8 - kernel-abiversion missing Schaumlöffel, Jan
2015-04-28 13:52 ` Bruce Ashfield
2015-04-28 15:36 ` Schaumlöffel, Jan
2015-04-28 18:58 ` Bruce Ashfield
2015-04-29 7:38 ` Schaumlöffel, Jan
2015-04-29 13:23 ` Bruce Ashfield
2015-04-30 7:14 ` Schaumlöffel, Jan
2015-04-30 12:18 ` Bruce Ashfield [this message]
2015-04-30 12:27 ` Schaumlöffel, Jan
2015-04-30 14:06 ` Bruce Ashfield
2015-05-11 18:10 ` Brian Hutchinson
2015-05-11 18:10 ` [yocto] " Brian Hutchinson
2015-05-11 18:34 ` Brian Hutchinson
2015-05-11 18:34 ` [yocto] " Brian Hutchinson
2015-05-11 19:06 ` Bruce Ashfield
2015-05-11 19:06 ` [yocto] " Bruce Ashfield
2015-05-12 14:20 ` Brian Hutchinson
2015-05-12 14:20 ` [yocto] " Brian Hutchinson
2015-05-12 15:35 ` Bruce Ashfield
2015-05-12 15:35 ` [yocto] " Bruce Ashfield
2015-05-14 22:08 ` [meta-ti] " Denys Dmytriyenko
2015-05-14 22:08 ` [yocto] " Denys Dmytriyenko
2015-05-14 22:16 ` [meta-ti] " Brian Hutchinson
2015-05-14 22:16 ` [yocto] " Brian Hutchinson
2015-05-15 13:55 ` [meta-ti] " Brian Hutchinson
2015-05-15 13:55 ` [yocto] " Brian Hutchinson
2015-05-15 19:26 ` [meta-ti] " Brian Hutchinson
2015-05-15 19:26 ` [yocto] " Brian Hutchinson
2015-05-15 20:21 ` [meta-ti] " Brian Hutchinson
2015-05-15 20:21 ` [yocto] " Brian Hutchinson
2015-05-19 11:39 ` [meta-ti] " Bruce Ashfield
2015-05-19 11:39 ` [yocto] " Bruce Ashfield
2015-05-19 16:31 ` [meta-ti] " Bruce Ashfield
2015-05-19 16:31 ` [yocto] " Bruce Ashfield
2015-05-19 16:42 ` [meta-ti] " Brian Hutchinson
2015-05-19 16:42 ` [yocto] " Brian Hutchinson
2015-05-21 1:49 ` Patricia Holden
2015-06-10 1:12 ` [meta-ti] " Brian Hutchinson
2015-06-10 1:12 ` [yocto] " Brian Hutchinson
2015-06-10 1:14 ` [meta-ti] " Bruce Ashfield
2015-06-10 1:14 ` [yocto] " Bruce Ashfield
2015-06-10 1:34 ` [meta-ti] " Brian Hutchinson
2015-06-10 1:34 ` [yocto] " Brian Hutchinson
2015-06-10 17:32 ` [meta-ti] " Brian Hutchinson
2015-06-10 17:32 ` [yocto] " Brian Hutchinson
2015-06-23 19:15 ` Robert Calhoun
2015-06-23 19:56 ` Bruce Ashfield
-- strict thread matches above, loose matches on Subject: below --
2015-04-29 13:53 Carl van Schaik
2015-04-29 14:04 Carl van Schaik
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=55421DA2.9060909@windriver.com \
--to=bruce.ashfield@windriver.com \
--cc=J.Schaumloeffel@astro-kom.de \
--cc=yocto@yoctoproject.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.