From: Dmitry Vinokurov <d.vinokuroff@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: bitbake ignores DEFAULT_PREFERENCE
Date: Fri, 21 Aug 2009 10:45:50 +0600 [thread overview]
Message-ID: <4A8E267E.9070201@gmail.com> (raw)
In-Reply-To: <19c1b8a90908201946o18975addyfd8f8194661620eb@mail.gmail.com>
Khem Raj wrote:
> On Wed, Aug 19, 2009 at 10:04 PM, Denys Dmytriyenko<denis@denix.org> wrote:
>
>> On Thu, Aug 20, 2009 at 10:40:08AM +0600, Dmitry Vinokurov wrote:
>>
>>> Hello,
>>>
>>> I want to port OE to LPC3250 board and now I'm trying to build
>>> helloworld-image.
>>>
>>> I've created lpc3250.conf in conf/machine:
>>> TARGET_ARCH = "arm"
>>> PACKAGE_EXTRA_ARCHS = "armv5te"
>>> TARGET_CC_ARCH = "-fsigned-char -mfpu=vfp -mfloat-abi=softfp"
>>>
>>> Then I've added DEFAULT_PREFERENCE_lpc3250 = "1" to
>>> 'recipes/linux/linux_2.6.27.bb', but 'bitbake -v helloworld-image'
>>> downloads 2.6.23 kernel all the same. Re-reading all recipes database make
>>> no sense.
>>>
>
> It could be downloading it for linux-libc-headers package too. bitbake -g
> can help you here.
>
>
>>> Could anybody advise, how this can be solved? I need to use exactly 2.6.27
>>> kernel as I know that it definitely works.
>>>
>> Are you sure it downloads 2.6.23 to build your kernel and not the
>> linux-libc-headers? Check the dependencies and what it's going to build by
>> executing "bitbake <target> -g" and then poking into depends.dot...
>>
>> Otherwise you can try setting PREFERRED_VERSION_virtual/kernel = "2.6.23" to
>> override DEFAULT_PREFERENCE...
>>
>> --
>> Denys
>>
Yes, you're right, it was for linux-libc-headers package. I'm not so
easily work with OE yet.
--
Best Regards,
Dmitry Vinokurov
<d.vinokuroff@gmail.com>
prev parent reply other threads:[~2009-08-21 5:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-20 4:40 bitbake ignores DEFAULT_PREFERENCE Dmitry Vinokurov
2009-08-20 5:04 ` Denys Dmytriyenko
2009-08-21 2:46 ` Khem Raj
2009-08-21 4:45 ` Dmitry Vinokurov [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=4A8E267E.9070201@gmail.com \
--to=d.vinokuroff@gmail.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 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.