3271 2012-10-10 16:29:10 +0000 Better error message when bitbake is run from the 'wrong' directory 2013-10-02 12:59:51 +0000 1 1 7 Build System, Metadata & Runtime BitBake bitbake unspecified x86 Multiple VERIFIED FIXED Low enhancement 1.5 1 evadeflow richard.purdie bluelightning corneliux.stoicescu jessica.zhang poky.bs.watcher poky.watcher --- --- Done (doc changes complete) oldest_to_newest 26494 0 evadeflow 2012-10-10 16:29:10 +0000 I was just trying to follow along with Patrick Turley's 'Hello World' example (see https://lists.yoctoproject.org/pipermail/yocto/2012-October/012193.html) and I accidentally forgot to switch to the build directory before invoking bitbake. The error I got (with bitbake master) was: > % ../bitbake/bin/bitbake a > The BBPATH variable is not set > DEBUG: Removed the following variables from the environment: http_proxy, CVS_RSH, LANG, SHLVL, LD_LIBRARY_PATH, EDITOR, SUDO_USER, USERNAME, PROMPT, PYTHONPATH, SUDO_UID, RPROMPT, _, SUDO_COMMAND, SUDO_GID, OLDPWD, MAIL DEBUG: UI 'knotty' does not require extra cache! A simple oversight like this must happen a dozen times daily here on Planet Earth. Once you've become accustomed to bitbake's quirks, I'm sure this isn't the slightest bit confusing; but to a novitiate like myself, it almost feels like I'm being hazed. Don't Haze Me, Bro'! :-} There are probably valid reasons that bitbake can't detect with 100% accuracy that the user has simply forgotten to change to the correct directory. But it should be able to make a good guess and offer corrective advice. If there's a directory named 'build*' in the current directory with a 'conf' sub-folder, how about saying: > The BBPATH variable is not set > (Perhaps you intended to run bitbake from /home/evadeflow/projects/foo/build?) Even for out-of-source builds, there's got to be some way of emitting a more helpful error message. BBPATH is not set? Heck, NOTHING is set. Can't bitbake detect this and say: > The BBPATH variable is not set > (Did you invoke bitbake from the wrong directory?) Oh, yes--yes, I did. Thank you! 26521 1 corneliux.stoicescu 2012-10-11 14:46:22 +0000 Hello. I just ran bitbake from the poky directory and I got: " Unable to find conf/bblayers.conf BitBake must be run from within your build diectory: /home/cornel/Yocto/poky/build " Please give us the exact steps to reproduce this. Thank you Cornel. 26533 2 885 evadeflow 2012-10-11 16:08:04 +0000 Created attachment 885 Bitbake 'Hello World!' example This example is the one that caused me to file the bug. But I don't think it's needed to reproduce the behavior: > poky|master|% pwd > /home/evadeflow/projects/poky > poky|master|% echo "Note: I have not sourced oe-init-build-env" > Note: I have not sourced oe-init-build-env > poky|master|% echo $PATH > /home/evadeflow/bin:/home/evadeflow/jdk/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin > poky|master|% ./bitbake/bin/bitbake foo > The BBPATH variable is not set > DEBUG: Removed the following variables from the environment: http_proxy, CVS_RSH, LANG, SHLVL, LD_LIBRARY_PATH, EDITOR, SUDO_USER, USERNAME, PROMPT, PYTHONPATH, SUDO_UID, RPROMPT, _, SUDO_COMMAND, SUDO_GID, OLDPWD, MAIL > DEBUG: UI 'knotty' does not require extra cache! Not a big deal, I just think that error message could be better. :-) 26553 3 bluelightning 2012-10-12 13:43:22 +0000 You should not be running bin/bitbake but instead scripts/bitbake, which is a wrapper that ensures everything is set up correctly. bitbake as we use it in OE-Core/Poky is really intended be run from the wrapper script so I don't think we really support doing otherwise (until the wrapper script goes away, which it will do at some point in the future). 26560 4 evadeflow 2012-10-12 16:00:16 +0000 (In reply to comment #3) > You should not be running bin/bitbake but instead scripts/bitbake... The message is a lot clearer in this case: > bitbake_hello% ../poky/scripts/bitbake foo > Unable to find conf/bblayers.conf > BitBake must be run from within your build directory Since I was following along with someone's 'Hello, World' example, I just did what it recommended. If the wrapper script can emit such a lucid error message, why can't bitbake/bin say something more helpful than: > The BBPATH variable is not set I completely understand that this is an extremely low priority item. You can assign this bug to me if you want. It would be a good introduction for me, and maybe I'll discover along the way that improving the error output is actually quite involved. I'm just trying to be as critical of bitbake's user experience as I am about my own company's products. A bad first impression can turn off would-be users who are just 'doing a drive-by', and mind share is everything. 26561 5 887 evadeflow 2012-10-12 16:40:03 +0000 Created attachment 887 Fix error msg when bblayers.conf not found Humbly submit this is small improvement... 34208 6 richard.purdie 2013-06-28 09:35:47 +0000 Patch merged to master: http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=624160af6e5429c9f08b201bc6599dc8dcb62c3f sorry about the delay in doing so, didn't notice there was a patch here. Incidentally the wrapper script is now gone so this is a bigger issue. 37478 7 corneliux.stoicescu 2013-10-02 12:59:51 +0000 Verified in: poky master:2f64fae60b3f61a2c45dc9e5314d2d16b1e64605 Please look at this bug for tips on using bitbake from any directory: bug 5063 885 2012-10-11 16:08:04 +0000 2012-10-11 16:08:04 +0000 Bitbake 'Hello World!' example bitbake_hello.tar.bz2 application/x-bzip2 667 evadeflow QlpoOTFBWSZTWeNoS2IAAoL/7c6QAEB0/f/ev+/dpf9/36oAAQCAAIAAAIAAgAhAAlxbBIBCSZAZ A0GJkAMgaGQyMgAAaAAaKJ6NGpiaaaT1BiDDQjIyaGho9IM1MBNNGhxkyaNAaNMRkaGIYE0aYgxG gwgAMEigmkCnlPaCmnlHqaGjQNA00M1GCD1GgNDynQkdHKsZ72GVGcWwKJDvNppO0kgCebQ4Z+w3 ohoRcFgEiNJldcG4Ox1wg4tQkkWxIxgmhKAkQGkZel8zWbp95HCNSZDRbSLaS/CQ0F23b2QsDAcI uIC6GJ9EEQYKFzKR/FMXJI49D5qBtYqvAhPcAspIrhjrMYPicCjyoE99CX0DUbOB106MC/YIHG4Q ZBdCAcRSmTaddyn7qUUebyM8IIAycmnTp45cm7z8+6CR6uAFt317GcEd/iqmFaRZUNE3KJpjWObK VFSRK1jpKEyI4UmKLRKlRVC5GVFBgTE6SlIcERg3kFWKARQUE1FVxVVHVXGkCQOVxDK0x1k4khTk Q3HbZy8mmQ3yxhma1PvWmHPxcJtBwhrPciEavDFAy0OUjA81fROGtWMJdIwh5+qS4UkgGBISWshS t9xCgohMnHNdSESqhWAZOiwZvQk0YimABaSasyInHnm4sSJSuwBll24b/pBYEjxZOi90/r2oX0BN wWdtDiooVO6W3CT/r129bDZshTHt1pctk4l1NEb6CZTj+X85tWtgtzXTeoCwgVnU1AX89gKXX2AY Z40LRb880LFUrVNlTSuoWVC1XL1yFTAmhWV4S6BASNWugkU2rWbBHevJGBKsw9tI/yRLHK/EsrmM LmRItiRIFivoW1ViygbEi7angugX9GwCzQBUCX/F3JFOFCQ42hLYgA== 887 2012-10-12 16:40:03 +0000 2012-10-12 16:40:03 +0000 Fix error msg when bblayers.conf not found 0001-Fix-error-msg-when-bblayers.conf-not-found.patch text/plain 1083 evadeflow RnJvbSA3ODUzNzc5NjFhNTM3MzFiYWMzYTI0NTIxM2RiODRmZTY1NTFiZTM4IE1vbiBTZXAgMTcg MDA6MDA6MDAgMjAwMQpGcm9tOiBFdmFkZSBGbG93IDxldmFkZWZsb3dAZ21haWwuY29tPgpEYXRl OiBGcmksIDEyIE9jdCAyMDEyIDEyOjM3OjUzIC0wNDAwClN1YmplY3Q6IFtQQVRDSF0gRml4IGVy cm9yIG1zZyB3aGVuIGJibGF5ZXJzLmNvbmYgbm90IGZvdW5kCgpTaWduZWQtb2ZmLWJ5OiBFdmFk ZSBGbG93IDxldmFkZWZsb3dAZ21haWwuY29tPgotLS0KIGxpYi9iYi9jb29rZXIucHkgfCAgICA3 ICsrKysrKy0KIDEgZmlsZSBjaGFuZ2VkLCA2IGluc2VydGlvbnMoKyksIDEgZGVsZXRpb24oLSkK CmRpZmYgLS1naXQgYS9saWIvYmIvY29va2VyLnB5IGIvbGliL2JiL2Nvb2tlci5weQppbmRleCA3 Y2ExZmZkLi42NTllYTgxIDEwMDY0NAotLS0gYS9saWIvYmIvY29va2VyLnB5CisrKyBiL2xpYi9i Yi9jb29rZXIucHkKQEAgLTg1OCw3ICs4NTgsMTIgQEAgY2xhc3MgQkJDb29rZXI6CiAgICAgICAg ICAgICBkYXRhLmRlbFZhcignTEFZRVJESVInKQogCiAgICAgICAgIGlmIG5vdCBkYXRhLmdldFZh cigiQkJQQVRIIiwgVHJ1ZSk6Ci0gICAgICAgICAgICByYWlzZSBTeXN0ZW1FeGl0KCJUaGUgQkJQ QVRIIHZhcmlhYmxlIGlzIG5vdCBzZXQiKQorICAgICAgICAgICAgbXNnID0gIlRoZSBCQlBBVEgg dmFyaWFibGUgaXMgbm90IHNldCIKKyAgICAgICAgICAgIGlmIG5vdCBsYXllcmNvbmY6CisgICAg ICAgICAgICAgICAgbXNnICs9ICgiIGFuZCBiaXRiYWtlIGRpZCBub3QgZmluZCBhIGNvbmYvYmJs YXllcnMuY29uZiBmaWxlIGluIgorICAgICAgICAgICAgICAgICAgICAgICAgIiB0aGUgZXhwZWN0 ZWQgbG9jYXRpb24uXG5NYXliZSB5b3UgYWNjaWRlbnRhbGx5IgorICAgICAgICAgICAgICAgICAg ICAgICAgIiBpbnZva2VkIGJpdGJha2UgZnJvbSB0aGUgd3JvbmcgZGlyZWN0b3J5PyIpCisgICAg ICAgICAgICByYWlzZSBTeXN0ZW1FeGl0KG1zZykKIAogICAgICAgICBkYXRhID0gX3BhcnNlKG9z LnBhdGguam9pbigiY29uZiIsICJiaXRiYWtlLmNvbmYiKSwgZGF0YSkKIAotLSAKMS43LjkuNQoK