On 19/04/15 02:49, Richard Purdie wrote:
On Fri, 2015-04-17 at 19:19 -0500, Alejandro Hernandez wrote:
On 17/04/15 16:50, Richard Purdie wrote:
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 <[email protected]>
---
.../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
I tried it on the autobuilder and it failed again. I think part of the
problem is that this part of the process runs under pseudo so it thinks
its root, yet can't clear root's pip directory in /tmp.
I suspect we are going to have to tell pip to use WORKDIR somehow, even
if we have to patch it to take some kind of prompt from the environment
for example.
Cheers,
Richard
Yes, the problem does happen when it uses pseudo and it thinks its root,
I thought removing the files inside the same python code would be able
to do it, ok I will find another workaround.
--
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-core
