| Summary: | SDK installer fails on hosts with Python 3.x | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] OE-Core | Reporter: | Paul Eggleton <bluelightning> | ||||
| Component: | devtools / tool chain | Assignee: | Laurentiu Palcu <laurentiu.palcu> | ||||
| Status: | RESOLVED FIXED | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | Medium+ | CC: | jessica.zhang, meta.mr.watcher, meta.watcher, sgw, srifenbark | ||||
| Version: | 1.5 | ||||||
| Target Milestone: | 1.5 M5 | ||||||
| Hardware: | All | ||||||
| OS: | Multiple | ||||||
| Whiteboard: | 24 March 2014: Set Documentation flag to "Done". | ||||||
| OS type for building Yocto: | --- | Type of Regression: | --- | ||||
| Verified: | Documentation change: | Done (doc changes complete) | |||||
| Attachments: |
|
||||||
Patch sent on the ML. Patch merged: http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=5b5e1b90087bf4aab7b52fd0676fe7a30db84bfe Hi, This documentation is pretty much in place but I went through and made sure that every place we mention some sort of note or process surrounding the Python requirements we are correctly talking about the buildtools-tarball as a way to get the right tools on a system if the user doesn't meet the current requirements. Here are some spots: I updated the FAQ entry that addressed not having the correct Python version - http://www.yoctoproject.org/docs/1.6/ref-manual/ref-manual.html#faq-not-meeting-requirements I updated the section in the ref-manual where we tell how to get the right tools. This is the primary area for this information - http://www.yoctoproject.org/docs/1.6/ref-manual/ref-manual.html#required-git-tar-and-python-versions I updated the note in the QS to point to the primary source for getting the build system updated. It was point to the FAQ, which pointed to the primary source - http://www.yoctoproject.org/docs/1.6/yocto-project-qs/yocto-project-qs.html#building-image I added a note in the QS where we talk about installing the toolchain. The note points out the fact that installing the toolchain gets your Git, tar, and Python requirements met - http://www.yoctoproject.org/docs/1.6/yocto-project-qs/yocto-project-qs.html#installing-the-toolchain. Finally, I added the same note into the section of the adt-manual where it talks about running the .sh file to install the toolchain - http://www.yoctoproject.org/docs/1.6/adt-manual/adt-manual.html#using-an-existing-toolchain-tarball Please check these changes out. Scott After talking with Paul about this, my initial set of changes were off. So what we have now is a change to the primary area of concern in the ref-manual, a alteration to a note in the QS, and an alteration to the FAQ entry: http://www.yoctoproject.org/docs/1.6/ref-manual/ref-manual.html#faq-not-meeting-requirements http://www.yoctoproject.org/docs/1.6/ref-manual/ref-manual.html#required-git-tar-and-python-versions http://www.yoctoproject.org/docs/1.6/yocto-project-qs/yocto-project-qs.html#building-image Please review. Scott Hi, The documentation changes in the previous comment have been reviewed and approved by Paul Eggleton. I am changing the flag to "Done." Scott |
Created attachment 1336 [details] Beginnings of a patch to fix the SDK relocation script for python 3 I was attempting to install buildtools-tarball on a distro that has Python 3.x (which is something we may have to support given that buildtools-tarball might be used on such distros if Python 2.7 isn't readily available); unfortunately the relocate script failed due to a few incompatibilities. Some of these are trivial to fix, others I wasn't quite sure about. I've attached a patch that starts to fix these but I wasn't quite sure what to do when it comes to writing paths into binaries that in theory might be unicode instead of ASCII and thus are longer than expected.