* commit 07792e4a83ca breaks oe-init-build-env sourcing
@ 2013-06-17 9:12 Jack Mitchell
2013-06-17 9:42 ` Richard Purdie
0 siblings, 1 reply; 2+ messages in thread
From: Jack Mitchell @ 2013-06-17 9:12 UTC (permalink / raw)
To: Patches and discussions about the oe-core layer
Pulled to the latest oe-core, bitbake and a few 3rd party layers this
morning, to find that when I source oe-init-build-env the terminal I was
sourcing in either crashes or exits.
I tested with both gnome-terminal and xterm, both produced the same
behaviour.
Heading into a git bisect the apparent bad commit is:
07792e4a83ca4f1c8152c228813c7f795fa6a545 (scripts/oe-buildenv-internal
bitbake: Migrate python version checks)
If it makes a difference the default python on my system is python3. My
workflow is usually source oe-init-build-env, then I add a directory
with a symlink to python2 at the beginning of my PATH, so the default
python is python2.
Any help would be appreciated; holler if you need me to run any more tests.
Cheers,
--
Jack Mitchell (jack@embed.me.uk)
Embedded Systems Engineer
http://www.embed.me.uk
--
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: commit 07792e4a83ca breaks oe-init-build-env sourcing
2013-06-17 9:12 commit 07792e4a83ca breaks oe-init-build-env sourcing Jack Mitchell
@ 2013-06-17 9:42 ` Richard Purdie
0 siblings, 0 replies; 2+ messages in thread
From: Richard Purdie @ 2013-06-17 9:42 UTC (permalink / raw)
To: ml; +Cc: Patches and discussions about the oe-core layer
On Mon, 2013-06-17 at 10:12 +0100, Jack Mitchell wrote:
> Pulled to the latest oe-core, bitbake and a few 3rd party layers this
> morning, to find that when I source oe-init-build-env the terminal I was
> sourcing in either crashes or exits.
>
> I tested with both gnome-terminal and xterm, both produced the same
> behaviour.
>
> Heading into a git bisect the apparent bad commit is:
> 07792e4a83ca4f1c8152c228813c7f795fa6a545 (scripts/oe-buildenv-internal
> bitbake: Migrate python version checks)
>
> If it makes a difference the default python on my system is python3. My
> workflow is usually source oe-init-build-env, then I add a directory
> with a symlink to python2 at the beginning of my PATH, so the default
> python is python2.
>
> Any help would be appreciated; holler if you need me to run any more tests.
I pushed a fix for this, sorry about that.
Cheers,
Richard
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2013-06-17 9:43 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2013-06-17 9:12 commit 07792e4a83ca breaks oe-init-build-env sourcing Jack Mitchell
2013-06-17 9:42 ` Richard Purdie
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.