Bug 7078 - Not possible to build Python 3 libraries, which depend on each other (distribute -> setuptools?)
Summary: Not possible to build Python 3 libraries, which depend on each other (distrib...
Status: RESOLVED INVALID
Alias: None
Product: OE-Core
Classification: Build System, Metadata & Runtime
Component: devtools / tool chain (show other bugs)
Version: 1.7
Hardware: x86 Multiple
: Medium normal
Target Milestone: 1.8
Assignee: wrobell
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2014-12-11 19:17 UTC by wrobell
Modified: 2015-03-27 15:01 UTC (History)
3 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: Don't know

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description wrobell 2014-12-11 19:17:21 UTC 
Due to change from warning to fatal error for overlapping files (see http://patchwork.openembedded.org/patch/80915/), it is not possible to build  Python 3 libraries, which depend on each other.

Consider library A and B. B depends on A.

1. A is built and installed into sysroot.
2. The B is built next. But current version of "distribute" picks A as well - it is dependency of B. So both B and A are being installed in sysroot overlapping with A installed seconds before.

Python 2.x might be affected as well. Newer version of "distribute" might have "--no-deps" option, but it is obsolete anyway. The "setuptools" has "--no-deps" option for sure, see https://pythonhosted.org/setuptools/easy_install.html#command-line-options.
Comment 1 wrobell 2014-12-11 19:19:25 UTC 
Notice about "distribute" being obsolete can be read at http://pythonhosted.org//distribute/
Comment 2 Alejandro Hernandez 2015-01-21 18:43:09 UTC 
Can you please give some additional info, e.g. libraries used and the given error, I can't seem to reproduce this.
Comment 3 Alejandro Hernandez 2015-03-26 17:20:28 UTC 
It's been over 60 days since the user's last response, I was not able to reproduce this bug, will close this for now, if the user can provide a complete test case this bug should be re-opened.