From: Jack Mitchell <ml@communistcode.co.uk>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: commit 07792e4a83ca breaks oe-init-build-env sourcing
Date: Mon, 17 Jun 2013 10:12:34 +0100 [thread overview]
Message-ID: <51BED302.8020107@communistcode.co.uk> (raw)
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
--
next reply other threads:[~2013-06-17 9:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-17 9:12 Jack Mitchell [this message]
2013-06-17 9:42 ` commit 07792e4a83ca breaks oe-init-build-env sourcing Richard Purdie
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=51BED302.8020107@communistcode.co.uk \
--to=ml@communistcode.co.uk \
--cc=openembedded-core@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox