From: Jaap de Jong <jaap.dejong@nedap.com>
To: "openembedded-devel@lists.openembedded.org"
<openembedded-devel@lists.openembedded.org>
Subject: Re: kernel image
Date: Thu, 22 Nov 2012 17:00:24 +0100 [thread overview]
Message-ID: <50AE4C18.6060500@nedap.com> (raw)
In-Reply-To: <20121122151725.GG12637@jama.jama.net>
On 11/22/2012 04:17 PM, Martin Jansa wrote:
> On Thu, Nov 22, 2012 at 03:33:29PM +0100, Jaap de Jong wrote:
>> On 11/22/2012 02:54 PM, Martin Jansa wrote:
>>> On Thu, Nov 22, 2012 at 02:36:25PM +0100, Jaap de Jong wrote:
>>>> On 11/22/2012 02:31 PM, Martin Jansa wrote:
>>>>> On Thu, Nov 22, 2012 at 02:18:43PM +0100, Jaap de Jong wrote:
>>>>>> Hi,
>>>>>> does anyone know where the + (in
>>>>>> kernel-2.6.35.14+_2.6.35-r14.6_mymachine.ipk) is added?
>>>>>> It is added on my pc (running ubuntu); it is not added on my debian
>>>>>> buildserver.
>>>>> Check if you have oe-core 56fe5300
>>>> I'm using oe-classic for this...
>>> Then apply it in oe-classic kernel.bbclass or your recipe.
>>>
>> Stupid question probably.. Where can I find it?
>> And one more: does it make sense that the '+' is added under ubuntu and
>> that is absent on my buildserver?
> http://git.openembedded.org/openembedded-core/commit/meta/classes/kernel.bbclass?id=56fe5300ab5ab072c20acd03d7fc26e9cae4e652
>
> Try to compare those 3 commands on both builders.
>
>
That seems to help.
I added it to my local linux recipe
do_configure_prepend() {
touch .scmversion
}
Thanks for your support!
prev parent reply other threads:[~2012-11-22 16:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-22 13:18 kernel image Jaap de Jong
2012-11-22 13:31 ` Martin Jansa
2012-11-22 13:36 ` Jaap de Jong
2012-11-22 13:54 ` Martin Jansa
2012-11-22 14:33 ` Jaap de Jong
2012-11-22 15:17 ` Martin Jansa
2012-11-22 16:00 ` Jaap de Jong [this message]
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=50AE4C18.6060500@nedap.com \
--to=jaap.dejong@nedap.com \
--cc=openembedded-devel@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox