Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Alejandro Hernandez <alejandro.hernandez@linux.intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/1] python3-native: Fix pip install issue due to unclean build directory
Date: Fri, 17 Apr 2015 22:50:02 +0100	[thread overview]
Message-ID: <1429307402.6976.207.camel@linuxfoundation.org> (raw)
In-Reply-To: <1ca6d1e0276189ecb640f08ce5afee34a788c163.1429177203.git.alejandro.hernandez@linux.intel.com>

On Thu, 2015-04-16 at 09:45 +0000, Alejandro Hernandez wrote:
> When installing python3-native sometimes pips default build
> directory (which is on the host and is user dependant) is left unclean,
> due to this, when python3-core is being installed it tries to use
> the same directory producing an error, this explicitly removes
> what the previous installation might have left behind, fixing the issue.
> 
> Signed-off-by: Alejandro Hernandez <alejandro.hernandez@linux.intel.com>
> ---
>  .../python/python3-native_3.4.2.bb                 |  1 +
>  .../python3/pip_build_directory_unclean.patch      | 28 ++++++++++++++++++++++
>  2 files changed, 29 insertions(+)
>  create mode 100644 meta/recipes-devtools/python/python3/pip_build_directory_unclean.patch

The problem here is that two builds of python3-native could be happening
on the same system at the same time. In fact I'd bet that is why its
breaking on the autobuilder. Can we not tell it to use something in
WORKDIR as its temp directory instead?

Cheers,

Richard



  reply	other threads:[~2015-04-17 21:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <cover.1429177203.git.alejandro.hernandez@linux.intel.com>
2015-04-16  9:45 ` [PATCH 1/1] python3-native: Fix pip install issue due to unclean build directory Alejandro Hernandez
2015-04-17 21:50   ` Richard Purdie [this message]
2015-04-18  0:19     ` Alejandro Hernandez
2015-04-19  7:49       ` Richard Purdie
2015-04-20 16:05         ` Alejandro Hernandez

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=1429307402.6976.207.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=alejandro.hernandez@linux.intel.com \
    --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