devshell not working for Qt or Boundary Devices based yocto
Hi ,
I'm trying out two different yocto distributions and in each one the devshell doens't work. Instead it just gets to the Summary line and returns to my normal shell ( bash ) .
I'm invoking it with
bitbake -c devshell core-image-minimal
bitbake --version = 1.32.0
I'm getting my distribution from
|repo init -u http:||//github||.com||/boundarydevices/boundary-bsp-platform||-b morty|
|or from Qt's boot2qt system using "b2qt-init-build-env init --device nitrogen6x|
||
Any ideas what is going wrong ?
Thanks,
Quoted 4 lines · Jimi Damon
Hi ,
I'm trying out two different yocto distributions and in each one the devshell doens't work. Instead it just gets to the Summary line and returns to my normal shell ( bash ) .
What are you expecting to happen? 'devshell' is just that - a shell environment (e.g. bash) where you are set up to "develop" (tinker, explore, etc) the given recipe.
Quoted 27 lines
I'm invoking it with
bitbake -c devshell core-image-minimal
bitbake --version = 1.32.0
I'm getting my distribution from
|repo init -u http:||//github||.com||/boundarydevices/boundary-bsp-platform||-b morty|
|or from Qt's boot2qt system using "b2qt-init-build-env init --device nitrogen6x|
||
Any ideas what is going wrong ?
Thanks,
Signature · 4 lines
------------------------------------------------------------ Gary Thomas | Consulting for the MLB Associates | Embedded world ------------------------------------------------------------
Quoted 8 lines · CEST Gary Thomas
Quoted 3 lines · Jimi Damon
I'm trying out two different yocto distributions and in each one the devshell doens't work. Instead it just gets to the Summary line and returns to my normal shell ( bash ) .
What are you expecting to happen? 'devshell' is just that - a shell environment (e.g. bash) where you are set up to "develop" (tinker, explore, etc) the given recipe.
I think Jimi is saying that it doesn't appear to be launching a separate terminal / shell. Right?
Assuming that's what's happening, the devshell code is supposed to print out an error when it can't launch a suitable terminal, but if the terminal isn't doing what it should then that might leave you in this situation. Does log.do_devshell for the recipe indicate anything?
Cheers,
Paul
Signature · 2 lines
Paul Eggleton Intel Open Source Technology Centre
Hi,
I am not getting a separate terminal or even a different shell ( I would assume that Control-D or exit would get me back to the original shell ). Note that *bitbake -c pydevshell <anyrec**ipe>* also fails in that no python shell is started.
In fact, I've deduced that something is set in my Environment in my Bash shell that is causing this corruption.
For example, I created a brand new user called "testperson" with shell Zsh ( different than my bash )
Using the exact same poky distribution that was setup as follows
Quoted 10 lines
git clone
git://git.yoctoproject.org/poky.gitcd poky
git clone
git://git.yoctoproject.org/meta-raspberrypiMACHINE=raspberrypi3 . ./oe-init-build-env mybuild
bitbake -c devshell gettext
, this part worked for the testuser with zsh .
However, with my bash environment I get :
bitbake -D -c devshell gettext
Quoted 13 lines
...
DEBUG: Inheriting /media/build/poky/meta/classes/autotools.bbclass (from /media/build/poky/meta/recipes-core/gettext/gettext_0.19.8.1.bb:29)
DEBUG: Inheriting /media/build/poky/meta/classes/siteinfo.bbclass (from /media/build/poky/meta/classes/autotools.bbclass:24)
DEBUG: Inheriting /media/build/poky/meta/classes/siteconfig.bbclass (from /media/build/poky/meta/classes/autotools.bbclass:251)
DEBUG: Inheriting /media/build/poky/meta/classes/texinfo.bbclass (from /media/build/poky/meta/recipes-core/gettext/gettext_0.19.8.1.bb:29)
DEBUG: SITE files ['endian-little', 'bit-32', 'arm-common', 'arm-32', 'common-linux', 'common-glibc', 'arm-linux', 'arm-linux-gnueabi', 'common']
DEBUG: SITE files ['endian-little', 'bit-32', 'arm-common', 'arm-32', 'common-linux', 'common-glibc', 'arm-linux', 'arm-linux-gnueabi', 'common']
DEBUG: SITE files ['endian-little', 'bit-32', 'arm-common', 'arm-32', 'common-linux', 'common-glibc', 'arm-linux', 'arm-linux-gnueabi', 'common']
DEBUG: Executing taskdo_devshell
DEBUG: gettext-0.19.8.1-r0do_devshell: Attempting to spawn terminal "xterm"
DEBUG: Teardown for bitbake-worker
The teardown comes immediately after the "Attemping to spawn terminal..."
Compared to
Quoted 9 lines
...
DEBUG: Inheriting /media/build/poky/meta/classes/siteconfig.bbclass (from /media/build/poky/meta/classes/autotools.bbclass:251)
DEBUG: Inheriting /media/build/poky/meta/classes/texinfo.bbclass (from /media/build/poky/meta/recipes-core/gettext/gettext_0.19.8.1.bb:29)
DEBUG: SITE files ['endian-little', 'bit-32', 'ix86-common', 'common-linux', 'common-glibc', 'i586-linux', 'common']
DEBUG: SITE files ['endian-little', 'bit-32', 'ix86-common', 'common-linux', 'common-glibc', 'i586-linux', 'common']
DEBUG: SITE files ['endian-little', 'bit-32', 'ix86-common', 'common-linux', 'common-glibc', 'i586-linux', 'common']
DEBUG: Executing taskdo_devshell
DEBUG: gettext-0.19.8.1-r0do_devshell: Attempting to spawn terminal "xterm"
Currently 1 running tasks (281 of 281) 99% |##################################################################################################### |
in the testuser.
On a side note, how can I produce more debugging output besides "-D" for the bitbake so that I can find out more about where the do_devshell task is failing ?
Thanks,
-Jimi
Quoted 19 lines · Paul Eggleton
Quoted 7 lines · CEST Gary Thomas
Quoted 3 lines · Jimi Damon
I'm trying out two different yocto distributions and in each one the devshell doens't work. Instead it just gets to the Summary line and returns to my normal shell ( bash ) .
What are you expecting to happen? 'devshell' is just that - a shell environment (e.g. bash) where you are set up to "develop" (tinker, explore, etc) the given recipe.
I think Jimi is saying that it doesn't appear to be launching a separate terminal / shell. Right?
Assuming that's what's happening, the devshell code is supposed to print out an error when it can't launch a suitable terminal, but if the terminal isn't doing what it should then that might leave you in this situation. Does log.do_devshell for the recipe indicate anything?
Cheers,
Paul
Hi,
I created a yocto group and user for performing these builds.
The yocto user has the basic Ubuntu default account ( comes from a simple useradd ... )
I verified that this user is able to perform the exact same bitbake -c devshell gettext that fails for other username ( same exact location on the filesystem after a sudo chgrp -R yocto $directory && sudo chmod -R g+rw $directory ).
I'm guessing something is going wrong with the fakeroot command as I'm now seeing the terminal show up for just a second and then close when I try running this devshell as my original username.
I'm not sure which setting in my bash shell is causing this error so I'm all ears for any suggestions.
-Jimi
Quoted 19 lines · Paul Eggleton
Quoted 7 lines · CEST Gary Thomas
Quoted 3 lines · Jimi Damon
I'm trying out two different yocto distributions and in each one the devshell doens't work. Instead it just gets to the Summary line and returns to my normal shell ( bash ) .
What are you expecting to happen? 'devshell' is just that - a shell environment (e.g. bash) where you are set up to "develop" (tinker, explore, etc) the given recipe.
I think Jimi is saying that it doesn't appear to be launching a separate terminal / shell. Right?
Assuming that's what's happening, the devshell code is supposed to print out an error when it can't launch a suitable terminal, but if the terminal isn't doing what it should then that might leave you in this situation. Does log.do_devshell for the recipe indicate anything?
Cheers,
Paul