Tested on master: f9384b0669a5d281e0d251060c453a2b228ea878 OS: Ubuntu 15.04 Steps to reproduce: 1. start toaster 2. create new project (local yocto project) 3. change machine to genericx86-64 4. change DISTRO in bitbake variables to "poky-lsb" (5. remove SDK_MACHINE due to known issue) 6. try to build core-image-lsb Expected: Build starts successfully. Observed: Build fails to start with following error in toaster_ui.log: ERROR: Nothing PROVIDES 'core-image-lsb' ERROR: core-image-lsb was skipped: missing required distro feature 'pam' (not in DISTRO_FEATURES) ERROR: Command execution failed: Note that I have tried to add DISTRO_FEATURES in the bitbake variables page with pam as value but the build still fails.
I tried this on master:7e8ff7b9d793b7be106415c3c80b687977217566 This is what I did: 1. Created a Toaster project with the local release 2. Changed the machine to genericx86-64 3. In the bitbake variables page, I removed the SDKMACHINE variable, set DISTRO to poky-lsb, and added the following variable variable: DISTRO_FEATURES_append value: pam In the value I made sure to put a space before 'pam'. 4. I built core-image-lsb The build went past the parsing state and got to about 70% before failing with something that seems unrelated to the problem reported. The error shown was Function failed: sstate_task_postfunc The task that failed was core-image-lsb do_populate_lic Mihail: could you try again on your side and see if you can reproduce the initial problem? Thanks!
(In reply to comment #1) > Mihail: could you try again on your side and see if you can reproduce the > initial problem? > > Thanks! Just tried and it looks like it works. I was not adding the blank space before "pam" in DISTRO_FEATURES_append. However...shouldn't this be handled by toaster automatically? I don't remember having to add the "pam" distro feature when building "by hand" with bitbake.
A build for core-image-lsb started from Toaster and Knotty should have exactly the same outcome. If I start such build from any of the 2 without adding pam to distro features I get this message: ERROR: core-image-lsb was skipped: missing required distro feature 'pam' (not in DISTRO_FEATURES) If you do the same, do you get a different outcome for the builds?
(In reply to comment #3) > A build for core-image-lsb started from Toaster and Knotty should have > exactly the same outcome. If I start such build from any of the 2 without > adding pam to distro features I get this message: > > ERROR: core-image-lsb was skipped: missing required distro feature 'pam' > (not in DISTRO_FEATURES) > > If you do the same, do you get a different outcome for the builds? Retested on the latest master: 2cd061a29a94fdcdfec86732e6bcbb71c12c4afc TOASTER BUILD: FAILED Started toaster, new project, changed DISTRO to poky-lsb, MACHINE to genericx86-64. Tried to build core-image-lsb, failed with "missing distro feature pam" error. COMMAND LINE BUILD: WORKS sourced new environment, changed in local.conf DISTRO to poky-lsb, MACHINE to genericx86-64. Bitbaked core-image-lsb and build started successfully. So with identical configuration changes, toaster fails but command line works.
There is another issue when building for a machine not provided by the poky layers. Builds fail with this message: Nothing PROVIDES 'virtual/kernel'linux-yocto-tiny PROVIDES virtual/kernel but was skipped: incompatible with machine intel-corei7-64 (not in COMPATIBLE_MACHINE)linux-yocto-rt PROVIDES virtual/kernel but was skipped: incompatible with machine intel-corei7-64 (not in COMPATIBLE_MACHINE)linux-yocto-tiny PROVIDES virtual/kernel but was skipped: incompatible with machine intel-corei7-64 (not in COMPATIBLE_MACHINE)linux-dummy PROVIDES virtual/kernel but was skipped: PREFERRED_PROVIDER_virtual/kernel set to linux-yocto, not linux-dummylinux-yocto PROVIDES virtual/kernel but was skipped: incompatible with machine intel-corei7-64 (not in COMPATIBLE_MACHINE)linux-yocto-rt PROVIDES virtual/kernel but was skipped: incompatible with machine intel-corei7-64 (not in COMPATIBLE_MACHINE)linux-yocto PROVIDES virtual/kernel but was skipped: incompatible with machine intel-corei7-64 (not in COMPATIBLE_MACHINE)linux-yocto-dev PROVIDES virtual/kernel but was skipped: incompatible with machine intel-corei7-64 (not in COMPATIBLE_MACHINE) In the case above, I was trying to build intel-corei7-64 provided by meta-intel. Brian Avery believes this error might be connected to what's causing this bug.
Mihail, can you try if this patch fixes the issue: http://lists.openembedded.org/pipermail/bitbake-devel/2016-January/006926.html ?
Here is my attempt to reproduce this: Tested on fresh master 68c7113a746694e25df2ac5d86171ed96b7c2e94 1. Toaster build triggered from Toaster UI. Changed DISTRO to poky-lsb, MACHINE to genericx86-64 core-image-lsb build failed with: Failed on 20/01/16 11:39 with 1 error and 1 warning Build time: 00:00:22 1 error Nothing PROVIDES 'core-image-lsb'core-image-lsb was skipped: missing required distro feature 'pam' (not in DISTRO_FEATURES) 2. Toaster build triggered from Toaster UI. Changed DISTRO to poky-lsb, MACHINE to genericx86-64, set DISTRO_FEATURES_append to ' pam' core-image-lsb build succeeded. 3. Toaster build triggered from command line: Changed DISTRO to poky-lsb, MACHINE to genericx86-64 in conf/local.conf core-image-lsb build failed with: ERROR: Nothing PROVIDES 'core-image-lsb' ERROR: core-image-lsb was skipped: missing required distro feature 'pam' (not in DISTRO_FEATURES) 4. Toaster build triggered from command line: Changed DISTRO to poky-lsb, MACHINE to genericx86-64, DISTRO_FEATURES_append to ' pam' in conf/local.conf core-image-lsb build succeeded. 5. bitbake command line build with toaster stopped Changed DISTRO to poky-lsb, MACHINE to genericx86-64 in conf/local.conf build succeeded Summary: Toaster UI and command line builds are identical, but differ from bitbake builds
Pam is in DISTRO_FEATURES for local bitbake build without toaster running: $ bitbake -e core-image-lsb | grep '^DISTRO_FEATURES=.* pam' DISTRO_FEATURES="alsa argp bluetooth ext2 irda largefile pcmcia usbgadget usbhost wifi xattr nfs zeroconf pci 3g nfc x11 ipv4 ipv6 libc-backtrace libc-big-macros libc-bsd libc-cxx-tests libc-catgets libc-charsets libc-crypt libc-crypt-ufc libc-db-aliases libc-envz libc-fcvt libc-fmtmsg libc-fstab libc-ftraverse libc-getlogin libc-idn libc-inet-anl libc-libm libc-locales libc-locale-code libc-memusage libc-nis libc-nsswitch libc-rcmd libc-rtld-debug libc-spawn libc-streams libc-sunrpc libc-utmp libc-utmpx libc-wordexp libc-posix-clang-wchar libc-posix-regexp libc-posix-regexp-glibc libc-posix-wchar-io largefile opengl ptest multiarch wayland pam largefile opengl pulseaudio sysvinit bluez5" pam is not there if DISTRO="poky" in local.config: $ bitbake -e core-image-lsb | grep '^DISTRO_FEATURES=.* pam' ERROR: Nothing PROVIDES 'core-image-lsb' ERROR: core-image-lsb was skipped: missing required distro feature 'pam' (not in DISTRO_FEATURES) Conclusion: Bitbake ignores toaster variables set in conf/toaster.conf Reason has to be investigated and fixed.
I've found the reason and hopefully fixed it: https://lists.yoctoproject.org/pipermail/toaster/2016-January/003714.html Please, review.
The fix has been accepted to bitbake master: http://cgit.openembedded.org/bitbake/commit/?id=76c9871740ef42ac35fdfdcb89a68478cca370cd
Verified on master: a4a5d1f3232821ea2695ba5e48ddfeb30ee7ea8d