Skip to contentSkip to conversation

Can't build core-image-weston

DISCUSSION Gary Thomas 3 participants 3 messages Feb 13, 2014

lore
Share & tools
lore
#0 lore raw

I just tried this build (my checkout is only a few days old):
Build Configuration:

BB_VERSION        = "1.21.1"
BUILD_SYS         = "i686-linux"
NATIVELSBSTRING   = "Fedora-13"
TARGET_SYS        = "arm-poky-linux-gnueabi"
MACHINE           = "qemuarm"
DISTRO            = "poky"
DISTRO_VERSION    = "1.5+snapshot-20140213"
TUNE_FEATURES     = "armv5 thumb dsp"
TARGET_FPU        = "soft"

meta
meta-yocto
meta-yocto-bsp = "master:4e9eb77108c7e628ebd00ec848b8bc034802e197"

'bitbake core-image-weston' yielded this error:

| Note: to be installed: packagegroup-core-ssh-dropbear@all rsync@armv5te libclutter-1.0-examples@armv5te openssh@armv5te psplash@armv5te weston@armv5te weston-init@all gtk+3-demo@armv5te weston-examples@armv5te smartpm@armv5te packagegroup-base-extended@qemuarm rpm@armv5te packagegroup-core-boot@qemuarm locale-base-en-us@armv5te locale-base-en-gb@armv5te

| Loading cache...
| Updating cache...               ######################################## [100%]
|
| Computing transaction...error: Can't install dropbear-2013.62-r0@armv5te: it's conflicted by the locked package openssh-6.4p1-r0@armv5te

I had previously built core-image-sato-sdk with some extra packages:
CORE_IMAGE_EXTRA_INSTALL += "rsync openssh"
That worked fine, but core-image-weston fails as above. Is there a reason I can't choose openssh instead of dropbear (and perhaps there is some other way I am supposed to choose)?

I removed the openssh from the extras and now it builds, but it doesn't do anything [useful] - should it actually work? I don't see anything that looks like 'weston' running.

Thanks

Signature · 4 lines
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------
#1 lore raw

Hi Gary,

Quoted 5 lines · Gary Thomas

I had previously built core-image-sato-sdk with some extra packages:
CORE_IMAGE_EXTRA_INSTALL += "rsync openssh"
That worked fine, but core-image-weston fails as above. Is there a reason I can't choose openssh instead of dropbear (and perhaps there is some other way I am supposed to choose)?

You might find EXTRA_IMAGE_FEATURES += "ssh-server-openssh" better than CORE_IMAGE_EXTRA_INSTALL, because core-image-weston has the ssh-server-dropbear image feature. When specifying both the right thing happens (dropbear is dropped).

Quoted 3 lines

I removed the openssh from the extras and now it builds, but it doesn't do anything [useful] - should it actually work? I don't see anything that looks like 'weston' running.

Looks like weston is crashing. There are known problems with Weston in qemu:

https://bugzilla.yoctoproject.org/show_bug.cgi?id=5660

Valentin did the research here and I can't remember the details:
Valentin, can you elaborate on the comments there about what is working/breaking? I remember there being a qemu option that changed behaviour too.

Try changing the init script (or just running weston manually) to pick the fbdev backend. Note that right now this isn't enabled but there's a patch on the list to enable it by default, but it's just a PACKAGECONFIG away from being enabled.

Ross

#2 lore raw
Quoted 25 lines · Ross

Hi Gary,

Quoted 5 lines · Gary Thomas

I had previously built core-image-sato-sdk with some extra packages:

   CORE_IMAGE_EXTRA_INSTALL += "rsync openssh"

That worked fine, but core-image-weston fails as above. Is there a reason I can't choose openssh instead of dropbear (and perhaps there is some other way I am supposed to choose)?

You might find EXTRA_IMAGE_FEATURES += "ssh-server-openssh" better than CORE_IMAGE_EXTRA_INSTALL, because core-image-weston has the ssh-server-dropbear image feature. When specifying both the right thing happens (dropbear is dropped).

Quoted 3 lines

I removed the openssh from the extras and now it builds, but it doesn't do anything [useful] - should it actually work? I don't see anything that looks like 'weston' running.

Looks like weston is crashing. There are known problems with Weston in qemu:

https://bugzilla.yoctoproject.org/show_bug.cgi?id=5660

Valentin did the research here and I can't remember the details:
Valentin, can you elaborate on the comments there about what is working/breaking? I remember there being a qemu option that changed behaviour too.

Quoted 6 lines

Try changing the init script (or just running weston manually) to pick the fbdev backend. Note that right now this isn't enabled but there's a patch on the list to enable it by default, but it's just a PACKAGECONFIG away from being enabled.

Ross

Hi,
To get something on the screen build weston with fbdev and with WESTON_NATIVE_BACKEND="fbdev-backend.so":
1) add fbdev to PACKAGECONFIG ( PACKAGECONFIG ??=
"${@base_contains('DISTRO_FEATURES', 'wayland', 'kms fbdev wayland', '', d)} \ .... )
2) append EXTRA_OECONF with WESTON_NATIVE_BACKEND="fbdev-backend.so".
If it's not working make sure you have a framebuffer device (/dev/fb0 should be there). If it's still not working, try with kms:
1) configure mesa (edit mesa.inc ) to build mesa dri driver :
a) PACKAGECONFIG ??= "egl gles dri gallium gallium-egl
gallium-gbm \ ....
b) change DRIDRIVERS = "swrast" to DRIDRIVERS = "" (so you can
build all dri drivers including vmwgfx)
c) (optional I think) change GALLIUMDRIVERS = "swrast" to
GALLIUMDRIVERS = "svga" (as I know vmwgfx is part of svga gallium drivers)
2) add this to your local.conf
CORE_IMAGE_EXTRA_INSTALL += " libgles2-mesa libegl-gallium
libgbm-gallium mesa-driver-vmwgfx "
If still not working, reply to this mail.