[yocto] devshell not working for Qt or Boundary Devices based yocto

[Jimi Damon]

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

> git clone git://git.yoctoproject.org/poky.git
>
> cd poky
>
> git clone git://git.yoctoproject.org/meta-raspberrypi
>
> MACHINE=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

> ...
>
> 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 task do_devshell
> DEBUG: gettext-0.19.8.1-r0 do_devshell: Attempting to spawn terminal 
> "xterm"
> DEBUG: Teardown for bitbake-worker
>

The teardown comes immediately after the "Attemping to spawn terminal..."


Compared to

> ...
> 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 task do_devshell
> DEBUG: gettext-0.19.8.1-r0 do_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



On 06/15/2017 01:47 AM, Paul Eggleton wrote:
> On Thursday, 15 June 2017 5:12:19 AM CEST Gary Thomas wrote:
>> On 2017-06-15 01:58, Jimi Damon wrote:
>>> 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
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.yoctoproject.org/pipermail/yocto/attachments/20170615/d6c62719/attachment.html>