On Fri, Sep 9, 2016 at 8:12 AM, Siegel, Jeffrey (Nokia - US) <
jeffrey.sie...@nokia.com> wrote:
> Thanks, this fixed the issue. After checking the output of ‘git log’, I
> picked this commit:
>
> git checkout d458b3
>
Sorry about that, I’ll see about creating stable release branches.
--
Thanks, this fixed the issue. After checking the output of ‘git log’, I picked
this commit:
git checkout d458b3
Jeff
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
On 8 September 2016 at 23:06, Siegel, Jeffrey (Nokia - US) <
jeffrey.sie...@nokia.com> wrote:
> ‘bb’ Python source contains shebang path ‘/usr/bin/env python3’ , which
> means it expects to be run by a Python 3.x interpreter. But then it imports
> python code from bitbake/lib, and bitbake/Yocto
Hi,
I'm fairly new to Yocto, several web article recommend the use of Chris
Larson's 'bb' utility. I understand 'bb' is not part of Yocto, but perhaps
someone here knows the answer to my problem. Running 'bb log' in my build
directory results in:
[siegel@xxx junk]$ bb log
Traceback (most
