Tree/Branch: Poky/1.1_M1 Poky Commit: 4ff7af11ef69849ef9c16f585eae58ac920b222b Meta Branch: 1.1_M1 Meta Commit: fc719f0cd6530ce15148b4aa274f1644b461b298 I find if there is no ${B} exists for linux-yocto, task do_menuconfig will fail. Because ${B} will be created by do_kernel_configme, which is after do_patch task. For example, if I run "DISPLAY=:1.0 bitbake linux-yocto -c menuconfig" in a clean working directory, which has no ${S} for linux-yocto, there will be no menuconfig menu pop-up. ####### OE Build Configuration: BB_VERSION = "1.11.0" METADATA_BRANCH = "(nobranch)" METADATA_REVISION = "4ff7af11ef69849ef9c16f585eae58ac920b222b" TARGET_ARCH = "i586" TARGET_OS = "linux" MACHINE = "qemux86" DISTRO = "poky" DISTRO_VERSION = "1.0+snapshot-20110603" TARGET_FPU = "" NOTE: Resolving any missing task queue dependencies NOTE: Preparing runqueue NOTE: Executing SetScene Tasks NOTE: Executing RunQueue Tasks NOTE: Running task 99 of 118 (ID: 4, /home/jxu49/osel/poky/meta/recipes-kernel/linux/linux-yocto_git.bb, do_fetch) NOTE: package linux-yocto-2.6.37+git1+79669230fd82a3e7e254cf8b596a2388a4333e62_1+b2afed7ecd54918b73db7f30062aaaf02fdaba54-r18: task do_fetch: Started NOTE: package linux-yocto-2.6.37+git1+79669230fd82a3e7e254cf8b596a2388a4333e62_1+b2afed7ecd54918b73db7f30062aaaf02fdaba54-r18: task do_fetch: Succeeded NOTE: Running task 114 of 118 (ID: 2, /home/jxu49/osel/poky/meta/recipes-kernel/linux/linux-yocto_git.bb, do_unpack) NOTE: package linux-yocto-2.6.37+git1+79669230fd82a3e7e254cf8b596a2388a4333e62_1+b2afed7ecd54918b73db7f30062aaaf02fdaba54-r18: task do_unpack: Started NOTE: package linux-yocto-2.6.37+git1+79669230fd82a3e7e254cf8b596a2388a4333e62_1+b2afed7ecd54918b73db7f30062aaaf02fdaba54-r18: task do_unpack: Succeeded NOTE: Running task 115 of 118 (ID: 1, /home/jxu49/osel/poky/meta/recipes-kernel/linux/linux-yocto_git.bb, do_kernel_checkout) NOTE: package linux-yocto-2.6.37+git1+79669230fd82a3e7e254cf8b596a2388a4333e62_1+b2afed7ecd54918b73db7f30062aaaf02fdaba54-r18: task do_kernel_checkout: Started NOTE: package linux-yocto-2.6.37+git1+79669230fd82a3e7e254cf8b596a2388a4333e62_1+b2afed7ecd54918b73db7f30062aaaf02fdaba54-r18: task do_kernel_checkout: Succeeded NOTE: Running task 116 of 118 (ID: 0, /home/jxu49/osel/poky/meta/recipes-kernel/linux/linux-yocto_git.bb, do_validate_branches) NOTE: package linux-yocto-2.6.37+git1+79669230fd82a3e7e254cf8b596a2388a4333e62_1+b2afed7ecd54918b73db7f30062aaaf02fdaba54-r18: task do_validate_branches: Started NOTE: package linux-yocto-2.6.37+git1+79669230fd82a3e7e254cf8b596a2388a4333e62_1+b2afed7ecd54918b73db7f30062aaaf02fdaba54-r18: task do_validate_branches: Succeeded NOTE: Running task 117 of 118 (ID: 3, /home/jxu49/osel/poky/meta/recipes-kernel/linux/linux-yocto_git.bb, do_patch) NOTE: package linux-yocto-2.6.37+git1+79669230fd82a3e7e254cf8b596a2388a4333e62_1+b2afed7ecd54918b73db7f30062aaaf02fdaba54-r18: task do_patch: Started NOTE: package linux-yocto-2.6.37+git1+79669230fd82a3e7e254cf8b596a2388a4333e62_1+b2afed7ecd54918b73db7f30062aaaf02fdaba54-r18: task do_patch: Succeeded NOTE: Running task 118 of 118 (ID: 5, /home/jxu49/osel/poky/meta/recipes-kernel/linux/linux-yocto_git.bb, do_menuconfig) NOTE: package linux-yocto-2.6.37+git1+79669230fd82a3e7e254cf8b596a2388a4333e62_1+b2afed7ecd54918b73db7f30062aaaf02fdaba54-r18: task do_menuconfig: Started NOTE: package linux-yocto-2.6.37+git1+79669230fd82a3e7e254cf8b596a2388a4333e62_1+b2afed7ecd54918b73db7f30062aaaf02fdaba54-r18: task do_menuconfig: Succeeded NOTE: Tasks Summary: Attempted 118 tasks of which 112 didn't need to be rerun and 0 failed. ####### With the command "DISPLAY=:1.0 bitbake linux-yocto -c menuconfig -e | grep ^B=" I could find the ${B} is set to a folder, which does not exist. ##### jxu49@vt-nhm4:~/osel/poky/build$ DISPLAY=:1.0 bitbake linux-yocto -c menuconfig -e | grep ^B= B="/home/jxu49/osel/poky/build/tmp/work/qemux86-poky-linux/linux-yocto-2.6.37+git1+79669230fd82a3e7e254cf8b596a2388a4333e62_1+b2afed7ecd54918b73db7f30062aaaf02fdaba54-r18/linux-qemux86-standard-build" ##### #### jxu49@vt-nhm4:~/osel/poky/build$ ls /home/jxu49/osel/poky/build/tmp/work/qemux86-poky-linux/linux-yocto-2.6.37+git1+79669230fd82a3e7e254cf8b596a2388a4333e62_1+b2afed7ecd54918b73db7f30062aaaf02fdaba54-r18/linux-qemux86-standard-build ls: cannot access /home/jxu49/osel/poky/build/tmp/work/qemux86-poky-linux/linux-yocto-2.6.37+git1+79669230fd82a3e7e254cf8b596a2388a4333e62_1+b2afed7ecd54918b73db7f30062aaaf02fdaba54-r18/linux-qemux86-standard-build: No such file or directory ####
Testing a fix of just making menuconfig come after configure, which seems sane to me. The typical usage should be to modify the config, not start one from scratch. If you want to start from scratch, you can still do that by deleting the .config or creating your own linux recipe.
http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=64497638e70c97f417c2bcdaf99ffcc843ad58ec
Verify with Yocto 1.1 M2 RC3 build, the bug is fixed.
Having to write a comment is silly.
(In reply to comment #4) > Having to write a comment is silly. Hi Darren, For our project, the end state of a bug is "VERIFIED". Pls. check the bugzilla process on our wiki page, https://wiki.pokylinux.org/wiki/Bugzilla_Configuration_and_Bug_Tracking#Bug_Life_Cycle.
verify the bug as fixed