After successfully building an image, the second and subsequent
attempts at building the image were failing with a python "OSError:
File exists" exception in do_rootfs.
Even bitbake -c clean did not fix the problem.
Eventually tracked it down to IMAGE_LINK_NAME having been
configured as "" (empt
I just found out that whenever this error is thrown it means that there
is no kernel config file in the specified layer (here it was
meta-yocto-bsp).
Therefore the configuration options can't be listed.
I think it's very irritating that in such cases a traceback is printed.
--
__
Hi,
when issuing the command "$ yocto-kernel config list yocto-bsp" command
i get following error message:
Traceback (most recent call last):
File "/home/c0dix/Downloads/Font/poky/scripts/yocto-kernel", line
394, in
ret = main()
File "/home/c0dix/Downloads/Font/poky/scripts/yocto-ke
> Trying to make the transition from denzil (1.2) to daisy (1.6.1) and have
> run into a problem that's got me stumped.
>
> There seems to have been a change in the way things are packaged that
> is breaking a number of my custom recipes.
>
> Let's say I have a package X that consists of source for
Trying to make the transition from denzil (1.2) to daisy (1.6.1) and have
run into a problem that's got me stumped.
There seems to have been a change in the way things are packaged that
is breaking a number of my custom recipes.
Let's say I have a package X that consists of source for an .so and
