All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nicolas Ferre <nicolas.ferre@atmel.com>
To: openembedded-devel@lists.openembedded.org
Cc: Martin Jansa <martin.jansa@gmail.com>
Subject: release-2010.12 (was: parsing error while building from scratch: literki_git.bb)
Date: Tue, 30 Nov 2010 10:56:22 +0100	[thread overview]
Message-ID: <4CF4CA46.8000302@atmel.com> (raw)
In-Reply-To: <4CE6A5F8.4090301@atmel.com>

Le 19/11/2010 17:29, Nicolas Ferre :
> Le 19/11/2010 17:07, Martin Jansa :
>> On Fri, Nov 19, 2010 at 04:55:07PM +0100, Nicolas Ferre wrote:
>>> Hi,
>>>
>>> While trying to build from scratch the latest .dev branch with:
>>> - at91sam9m10g45ek machine
>>> - angstrom-2010.x distribution
>>> - bitbake 1.10.1
>>>
>>> I have the following error just after bitbake parsing .bb files:
>>
>> what does it show if you do
>> git ls-remote http://git.senfdax.de/git/literki master
>> in terminal?
> 
> It seems to work:
> $ git ls-remote http://git.senfdax.de/git/literki master
> 1da40724369c8adc069288f1bfc6b2e167bbb87b        refs/heads/master
> 
>> are you using BB_LOCALCOUNT_OVERRIDE and/or BB_GIT_CLONE_FOR_SRCREV (ie
>> in your local.conf?
> 
> No, neither the one nor the other.

My build on top of release-2010.12 is only working with the following
commit form org.openembedded.dev:
dc07958c6fad86917bd7d1b65614b14a1eec8c11

Please include in release...

Bye,
-- 
Nicolas Ferre




  reply	other threads:[~2010-11-30  9:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-19 15:55 parsing error while building from scratch: literki_git.bb Nicolas Ferre
2010-11-19 16:07 ` Martin Jansa
2010-11-19 16:29   ` Nicolas Ferre
2010-11-30  9:56     ` Nicolas Ferre [this message]
2010-11-30 18:05       ` release-2010.12 (was: parsing error while building from scratch: literki_git.bb) Khem Raj

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=4CF4CA46.8000302@atmel.com \
    --to=nicolas.ferre@atmel.com \
    --cc=martin.jansa@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.