[poky] Poky bernard-5.0 ARM/uclibc meta-toolchain build?

[Sergei Poselenov]

Hello all,

I'm newby in poky and I'm trying to build a toolchain, which targets
the Cortex-M3 CPU, thumb mode. Target kernel 2.6 supports only flat
binaries, so my choice of Libc is uClibc - is it correct?

I created the machine configuratin file for my target in
meta/conf/machines, it has the following definitions:
---
TARGET_ARCH = "arm"

TARGET_CC_ARCH="-mcpu=cortex-m3 -mthumb"
TARGET_FPU="soft"
BASE_PACKAGE_ARCH="armv7"
TARGET_OS="linux-uclibc"


# Guesswork                                                                     
SERIAL_CONSOLE = "115200 ttyAAO2"

#??                                                                             
PREFERRED_PROVIDER_virtual/kernel ?= "linux-dummy"
KERNEL_IMAGETYPE = "vmlinux"

#                                                                               
MACHINE_FEATURES = "kernel26 serial"


---
I initialized poky build environment and started the build as
"POKYLIBC=uclibc bitbake -v meta-toolchain".

After step 88 build failed, last lines of the log are:
ERROR: Required build target 'meta-toolchain' has no buildable providers.
Missing or unbuildable dependency chain was: ['meta-toolchain', 'virtual/arm-poky-linux-uclibcgnueabi-compilerlibs', 'desktop-file-utils-native', 'glib-2.0-native']
NOTE: multiple providers are available for virtual/libc-nativesdk (glibc-nativesdk, eglibc-nativesdk)
NOTE: consider defining a PREFERRED_PROVIDER entry to match virtual/libc-nativesdk
ERROR: Nothing PROVIDES 'glib-2.0-native'
ERROR: Command execution failed: Traceback (most recent call last):
  File "/home/work/psl/poky/poky/bitbake/lib/bb/command.py", line 102, in runAsyncCommand
    commandmethod(self.cmds_async, self, options)
  File "/home/work/psl/poky/poky/bitbake/lib/bb/command.py", line 200, in buildTargets
    command.cooker.buildTargets(pkgs_to_build, task)
  File "/home/work/psl/poky/poky/bitbake/lib/bb/cooker.py", line 828, in buildTargets
    taskdata.add_unresolved(localdata, self.status)
  File "/home/work/psl/poky/poky/bitbake/lib/bb/taskdata.py", line 534, in add_unresolved
    self.remove_buildtarget(targetid)
  File "/home/work/psl/poky/poky/bitbake/lib/bb/taskdata.py", line 491, in remove_buildtarget
    self.fail_fnid(fnid, missing_list)
  File "/home/work/psl/poky/poky/bitbake/lib/bb/taskdata.py", line 471, in fail_fnid
    self.remove_buildtarget(target, missing_list)
  File "/home/work/psl/poky/poky/bitbake/lib/bb/taskdata.py", line 496, in remove_buildtarget
    self.fail_fnid(self.tasks_fnid[taskid], missing_list)
  File "/home/work/psl/poky/poky/bitbake/lib/bb/taskdata.py", line 471, in fail_fnid
    self.remove_buildtarget(target, missing_list)
  File "/home/work/psl/poky/poky/bitbake/lib/bb/taskdata.py", line 491, in remove_buildtarget
    self.fail_fnid(fnid, missing_list)
  File "/home/work/psl/poky/poky/bitbake/lib/bb/taskdata.py", line 471, in fail_fnid
    self.remove_buildtarget(target, missing_list)
  File "/home/work/psl/poky/poky/bitbake/lib/bb/taskdata.py", line 501, in remove_buildtarget
    raise bb.providers.NoProvider(target)
NoProvider: meta-toolchain

What are the real reason of the build failure? What should look for in
the build log?


As a test, I started "MACHINE=quemuarm bitbake -v meta-toolchain",
which built the eglibc-based toolchain successfully. Then I added
"POKYLIBC=uclibc" to the command above, build failed with the same
output.


Is it possible to build uclibc-based ARM toolchain in poky?

Any help would be appreciated.

Regards,
Sergei




tried to build with
"MACHINE=quemuarm POKYLIBC=uclibc"