Problems with bitbake meta-toolchain-sdk

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Problems with bitbake meta-toolchain-sdk

Jump to solution
2,340 Views
sebastianvogel
Contributor I

Hello everybody,

I am not sure if this is the correct place to put my question, so please be patient if I am wrong...

I tried to build the Community Yocto BSP as described here: fsl-community-bsp-platform/README at master · Freescale/fsl-community-bsp-platform · GitHub

Anyway I am having problems to build images other than core-image-minimal. I tried meta-toolchain-sdk, core-image-core and core-image-base. All of them keep putting out the following error message in a loop after a while.

ERROR: Running idle function

Traceback (most recent call last):

  File "fsl-community-bsp/sources/poky/bitbake/lib/bb/cooker.py", line 1134, in buildTargetsIdle(server=<ProcessServer(ProcessServer-1, started)>, rq=<bb.runqueue.RunQueue instance at 0xdbc8d2c>, abort=False):

                 try:

    >                retval = rq.execute_runqueue()

                 except runqueue.TaskFailure as exc:

  File "fsl-community-bsp/sources/poky/bitbake/lib/bb/runqueue.py", line 971, in RunQueue.execute_runqueue():

             if self.state is runQueueRunning:

    >            retval = self.rqexe.execute()

    

  File "fsl-community-bsp/sources/poky/bitbake/lib/bb/runqueue.py", line 1407, in RunQueueExecuteTasks.execute():

             for pipe in self.build_pipes:

    >            self.build_pipes[pipe].read()

    

  File "fsl-community-bsp/sources/poky/bitbake/lib/bb/runqueue.py", line 1808, in runQueuePipe.read():

             while index != -1:

    >            bb.event.fire_from_worker(self.queue[:index+8], self.d)

                 self.queue = self.queue[index+8:]

  File "fsl-community-bsp/sources/poky/bitbake/lib/bb/event.py", line 155, in fire_from_worker(event='<event>ccopy_reg\n_reconstructor\np1\n(clogging\nLogRecord\np2\nc__builtin__\nobject\np3\nNtRp4\n(dp5\nS\'taskpid\'\np6\nI2541\nsS\'threadName\'\np7\nS\'MainThread\'\np8\nsS\'name\'\np9\nS\'BitBake.Util\'\np10\nsS\'thread\'\np11\nI-1221941568\nsS\'created\'\np12\nF1348052231.8618729\nsS\'process\'\np13\nI2541\nsS\'processName\'\np14\nS\'ProcessServer-1\'\np15\nsS\'args\'\np16\n(tsS\'module\'\np17\nS\'utils\'\np18\nsS\'filename\'\np19\nS\'utils.py\'\np20\nsS\'levelno\'\np21\nI40\nsS\'exc_text\'\np22\nNsS\'pathname\'\np23\nS\'fsl-community-bsp/sources/poky/bitbake/lib/bb/utils.py\'\np24\nsS\'lineno\'\np25\nI372\nsS\'msg\'\np26\nS\'    data = "<event>" + pickle.dumps(event) + "</event>', d=<bb.data_smart.DataSmart object at 0xb6cfb70c>):

             return

    >    event = pickle.loads(event[7:-8])

         fire_ui_handlers(event, d)

ValueError: insecure string pickle

Does anybody have an idea of what I am doing wrong? Btw, my local.conf looks like this:

MACHINE ??= 'qemuarm'

DISTRO ?= 'poky'

PACKAGE_CLASSES ?= "package_rpm"

EXTRA_IMAGE_FEATURES = "debug-tweaks"

USER_CLASSES ?= "buildstats image-mklibs image-prelink"

PATCHRESOLVE  = "noop"

CONF_VERSION = "1"

BB_NUMBER_THREADS = '4'

PARALLEL_MAKE = '-j 4'

My system is a freshly installed Ubuntu 12.04.1 LTS for x86.

1 Solution
1,339 Views
daiane_angolini
NXP Employee
NXP Employee

I got this error too.

But, I have the fix. It's not a beautiful fix but it works.

You need to have the file gnutls-2.12.17.tar.bz2 and gnutls-2.12.17.tar.bz2.done under your downloads folder.

There is a bug on bitbake (somewhere) that point as an WARNING and not an ERROR when do_fetch fail for the package.

View solution in original post

0 Kudos
2 Replies
1,340 Views
daiane_angolini
NXP Employee
NXP Employee

I got this error too.

But, I have the fix. It's not a beautiful fix but it works.

You need to have the file gnutls-2.12.17.tar.bz2 and gnutls-2.12.17.tar.bz2.done under your downloads folder.

There is a bug on bitbake (somewhere) that point as an WARNING and not an ERROR when do_fetch fail for the package.

0 Kudos
1,339 Views
sebastianvogel
Contributor I

Thanks Daiane :smileyhappy: Works perfectly. Unfortunately I have no time currently to identify the actual bug, but this fix works :smileyhappy:. You made my day! :smileyhappy: