All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pierluigi Passaro <pierluigi.passaro@phoenixsoftware.it>
To: openembedded-devel@lists.openembedded.org
Subject: Re: bitbake error?
Date: Fri, 29 Oct 2010 11:33:00 +0200	[thread overview]
Message-ID: <4CCA94CC.3080302@phoenixsoftware.it> (raw)
In-Reply-To: <loom.20101029T033738-284@post.gmane.org>

Not sure this is the best solution, but I solved same issue using latest 
bitbake 1.10.1 downloaded from

http://download.berlios.de/bitbake/bitbake-1.10.1.tar.gz


James Ronald wrote:
> Jaap de Jong <jaap.dejong <at> nedap.com> writes:
>
>   
>> I'm probably totally stupid...
>> What am doing wrong?
>> (I'm working on a fresh unstable branch)
>> When I bitbake I get:
>>
>> MACHINE=at91sam9263ek  bitbake u-boot
>> Traceback (most recent call last):
>>    File "/media/OpenEmbedded/unstable/bitbake/bin/bitbake", line 143, in 
>> <module>
>>      main()
>>    File "/media/OpenEmbedded/unstable/bitbake/bin/bitbake", line 123, in 
>> main
>>      cooker.parseConfiguration()
>>    File "/media/OpenEmbedded/unstable/bitbake/lib/bb/cooker.py", line 
>> 68, in parseConfiguration
>>      self.parseConfigurationFile( os.path.join( "conf", "bitbake.conf" ) )
>>    File "/media/OpenEmbedded/unstable/bitbake/lib/bb/cooker.py", line 
>> 402, in parseConfigurationFile
>>      bb.fetch.fetcher_init(self.configuration.data)
>>    File "/media/OpenEmbedded/unstable/bitbake/lib/bb/fetch/__init__.py", 
>> line 93, in fetcher_init
>>      pd = persist_data.PersistData(d)
>>    File "/media/OpenEmbedded/unstable/bitbake/lib/bb/persist_data.py", 
>> line 52, in __init__
>>      bb.mkdirhier(self.cachedir)
>>    File "/media/OpenEmbedded/unstable/bitbake/lib/bb/__init__.py", line 
>> 133, in mkdirhier
>>      debug(3, "mkdirhier(%s)" % dir)
>>    File "/media/OpenEmbedded/unstable/bitbake/lib/bb/__init__.py", line 
>> 103, in debug
>>      bb.msg.debug(lvl, None, ''.join(args))
>>    File "/media/OpenEmbedded/unstable/bitbake/lib/bb/msg.py", line 100, 
>> in debug
>>      bb.event.fire(MsgDebug(msg, None))
>>    File "/media/OpenEmbedded/unstable/bitbake/lib/bb/event.py", line 67, 
>> in fire
>>      if tmpHandler(event) == Handled:
>>    File "tmpHandler(e)", line 8, in tmpHandler
>> NameError: global name 'msg' is not defined
>>
>>     
>
> I'm getting the exact same error. I'm new to OE and just going through the 
> Getting started wiki entry. Ubuntu 10.04 installing bitbake via apt-get install 
> bitbake.
>
> bitbake --version 
> BitBake Build Tool Core version 1.8.18, bitbake version 1.8.18
>   
> OE is current as of a few minutes ago.
>
> jr@ubuntu-xpc:~/oe/build$ bitbake nano
> Traceback (most recent call last):
>   File "/usr/bin/bitbake", line 143, in <module>
>     main()
>   File "/usr/bin/bitbake", line 123, in main
>     cooker.parseConfiguration()
>   File "/usr/lib/pymodules/python2.6/bb/cooker.py", line 67, in 
> parseConfiguration
>     self.parseConfigurationFile( os.path.join( "conf", "bitbake.conf" ) )
>   File "/usr/lib/pymodules/python2.6/bb/cooker.py", line 401, in 
> parseConfigurationFile
>     bb.fetch.fetcher_init(self.configuration.data)
>   File "/usr/lib/pymodules/python2.6/bb/fetch/__init__.py", line 93, in 
> fetcher_init
>     pd = persist_data.PersistData(d)
>   File "/usr/lib/pymodules/python2.6/bb/persist_data.py", line 52, in __init__
>     bb.mkdirhier(self.cachedir)
>   File "/usr/lib/pymodules/python2.6/bb/__init__.py", line 133, in mkdirhier
>     debug(3, "mkdirhier(%s)" % dir)
>   File "/usr/lib/pymodules/python2.6/bb/__init__.py", line 103, in debug
>     bb.msg.debug(lvl, None, ''.join(args))
>   File "/usr/lib/pymodules/python2.6/bb/msg.py", line 100, in debug
>     bb.event.fire(MsgDebug(msg, None))
>   File "/usr/lib/pymodules/python2.6/bb/event.py", line 67, in fire
>     if tmpHandler(event) == Handled:
>   File "tmpHandler(e)", line 8, in tmpHandler
> NameError: global name 'msg' is not defined
>
> - Jim 
>
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>   



  reply	other threads:[~2010-10-29 11:20 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-28 13:18 bitbake error? Jaap de Jong
2010-10-29  1:51 ` James Ronald
2010-10-29  9:33   ` Pierluigi Passaro [this message]
2010-10-29 15:20     ` James Ronald
2010-10-30 10:16       ` Jaap de Jong
2010-10-30 10:21         ` Denys Dmytriyenko
2010-11-01  9:59           ` Walter Franzini
  -- strict thread matches above, loose matches on Subject: below --
2017-08-09  8:29 bitbake error ? Riko
2017-08-09  8:31 ` Burton, Ross
2017-08-09  8:34   ` Riko
2017-08-09  8:38     ` Burton, Ross
2017-08-09 10:27       ` Riko Ho
2017-08-09 10:34         ` Burton, Ross
2017-08-09 12:42           ` Bejar-Colonia, Carlos
     [not found]             ` <CAByQQ_rHGL-wCDP_gnws4txKTq_6Qn1ux83jx4BjiZbveLDCNQ@mail.gmail.com>
2017-08-09 21:06               ` Riko Ho
2017-08-09 21:13                 ` Burton, Ross
2017-08-10  1:19                   ` Riko
2017-08-10  1:09       ` Riko

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=4CCA94CC.3080302@phoenixsoftware.it \
    --to=pierluigi.passaro@phoenixsoftware.it \
    --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.