From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Martin Jansa <martin.jansa@gmail.com>
Cc: bitbake-devel@lists.openembedded.org
Subject: Re: [PATCH] setup.py: fix path for bitbake-selftest
Date: Sun, 13 May 2012 20:02:27 +0100 [thread overview]
Message-ID: <1336935747.2711.21.camel@ted> (raw)
In-Reply-To: <1336805867-25625-1-git-send-email-Martin.Jansa@gmail.com>
On Sat, 2012-05-12 at 08:57 +0200, Martin Jansa wrote:
> * currently fails with:
> running build_scripts
> creating build/scripts-2.7
> copying and adjusting bin/bitbake -> build/scripts-2.7
> copying and adjusting bin/bitbake-layers -> build/scripts-2.7
> copying and adjusting bin/bitbake-diffsigs -> build/scripts-2.7
> copying and adjusting bin/bitbake-prserv -> build/scripts-2.7
> error: file '/tmp/tmpfs/portage/dev-embedded/bitbake-9999/work/bitbake-9999/bitbake-selftest' does not exist
>
> Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
> ---
> setup.py | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
Merged to master, thanks.
Richard
prev parent reply other threads:[~2012-05-13 19:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-12 6:57 [PATCH] setup.py: fix path for bitbake-selftest Martin Jansa
2012-05-13 19:02 ` Richard Purdie [this message]
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=1336935747.2711.21.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=bitbake-devel@lists.openembedded.org \
--cc=martin.jansa@gmail.com \
/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