Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Denys Dmytriyenko <denis@denix.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: bitbake virtual/kernel fails for davinci
Date: Tue, 30 Jun 2009 13:05:33 -0400	[thread overview]
Message-ID: <20090630170533.GC6573@denix.org> (raw)
In-Reply-To: <5f2b60906300444w31cdcf67o6b3eeab0d1fb85ab@mail.gmail.com>

On Tue, Jun 30, 2009 at 01:44:43PM +0200, Bj??rn Forsman wrote:
> Hi,
> 
> I am a bit new to OpenEmbedded, but have successfully built angstrom
> for davinci and qemu in the past. Today I tried to "bitbake
> virtual/kernel" for a davinci (dm6446) system. The build fails during
> unpack of linux-davinci kernel because git cannot find a given object
> hash (see output below). Has anybody else experienced this? How come
> OE references a non-existent git object?
> 
> The non-existent git object hash is specified in
> "recipes/linux/linux-davinci_git.bb" and was lastly modified by commit
> 160616d5f2a57ba828ed5ec06e37fc1cd4713af7.

Since then linux-davinci tree was updated to 2.6.30 final and more 
specifically, staging/vpfe branch was rebased from v2 to v3 vpfe patches. 
Unfortunately, rebase rewrites the history and changes commit numbers, hence 
the old commit cannot be found any more...

I'll update the recipe with the latest state of the linux-davinci tree. But, 
it may brake in the future again, as this is a moving target. If you want 
something, which does not break that often, I'd suggest you don't use the 
"git" version of the recipe - try setting PREFFERED_PROVIDER/VERSION for 
2.6.28 or 2.6.29...

-- 
Denys



  reply	other threads:[~2009-06-30 17:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-30 11:44 bitbake virtual/kernel fails for davinci Bjørn Forsman
2009-06-30 17:05 ` Denys Dmytriyenko [this message]
2009-06-30 19:14   ` Bjørn Forsman
2009-06-30 19:54     ` Denys Dmytriyenko

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=20090630170533.GC6573@denix.org \
    --to=denis@denix.org \
    --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