Run build with 'MACHINE ?= "beagleboard"' $ bitbake eglinfo-x11 Error messages: ERROR: Function failed: do_configure (log file is located at /buildarea/wfan/yocto/eglinfo-x11/tmp/work/armv7a-vfp-neon-poky-linux-gnueabi/eglinfo-x11/1.0-r0/temp/log.do_configure.14194) ERROR: Logfile of failure stored in: /buildarea/wfan/yocto/eglinfo-x11/tmp/work/armv7a-vfp-neon-poky-linux-gnueabi/eglinfo-x11/1.0-r0/temp/log.do_configure.14194 Log data follows: | DEBUG: Executing python function sysroot_cleansstate | DEBUG: Python function sysroot_cleansstate finished | DEBUG: Executing shell function do_configure | Setting top to : /buildarea/wfan/yocto/eglinfo-x11/tmp/work/armv7a-vfp-neon-poky-linux-gnueabi/eglinfo-x11/1.0-r0/git | Setting out to : /buildarea/wfan/yocto/eglinfo-x11/tmp/work/armv7a-vfp-neon-poky-linux-gnueabi/eglinfo-x11/1.0-r0/git/build | Checking for 'gcc' (c compiler) : arm-poky-linux-gnueabi-gcc -march=armv7-a -mthumb-interwork -mfloat-abi=softfp -mfpu=neon --sysroot=/buildarea/wfan/yocto/eglinfo-x11/tmp/sysroots/beagleboard | Checking for 'g++' (c++ compiler) : arm-poky-linux-gnueabi-g++ -march=armv7-a -mthumb-interwork -mfloat-abi=softfp -mfpu=neon --sysroot=/buildarea/wfan/yocto/eglinfo-x11/tmp/sysroots/beagleboard | Checking for library X11 : yes | Checking for header X11/Xlib.h : yes | Checking for library ['EGL', 'IMGegl', 'srv_um'] : not found | The configuration failed | (complete log in /buildarea/wfan/yocto/eglinfo-x11/tmp/work/armv7a-vfp-neon-poky-linux-gnueabi/eglinfo-x11/1.0-r0/git/build/config.log) | WARNING: exit code 1 from a shell command. | ERROR: Function failed: do_configure (log file is located at /buildarea/wfan/yocto/eglinfo-x11/tmp/work/armv7a-vfp-neon-poky-linux-gnueabi/eglinfo-x11/1.0-r0/temp/log.do_configure.14194) ERROR: Task 5 (/buildarea/wfan/yocto/poky/meta/recipes-graphics/eglinfo/eglinfo-x11_1.0.bb, do_configure) failed with exit code '1'
meta-yocto-bsp's beagleboard support doesn't have any EGL drivers, so that won't work. The question is how do we differentiate meta-yocto-bsp's beagleboard from meta-ti's beagleboard.
So the problem is that we have two competing BSPs both called beagleboard. We should probably remove the non-oe-core machines from the recipe in oe-core and let each BSP add its own bbappend.
Patch sent to oe-core.
Merged as 2c1e147e61875054039ff08c36657c68c73037ee.