-
-
Notifications
You must be signed in to change notification settings - Fork 31.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Failure to build out of source from a not clean source #76115
Comments
The error message when building out of a not clean source tree: renaming build/scripts-3.7/2to3 to build/scripts-3.7/2to3-3.7 |
What's "unclean" in this case? I mean you can always re-run Make after making changes and the build succeeds, so I'm not quite sure what leads to this state. |
When you build out of the source tree and this source tree has been built previously (by running 'make' in the source tree), then you get the error msg printed in msg305486 when you try to build *out* of this not clean source tree. The solution is to run 'make clean' in the source tree first. The reason that one must use a clean source tree is that otherwise 'make' finds an existing Programs/_testembed.o file in the source tree as the prerequisite to the Programs/_testembed target, but cannot build this target since Programs/_testembed.o does not exist locally. It is not obvious from the error message to understand the reason for the build failure and one can waste quite some time finding the solution. |
To build out of the 'src' source tree (a subdirectory of the current directory) in a 'build' subdirectory: $ ls -ld src
drwxr-xr-x 21 xavier xavier 4.0K Nov 3 23:50 src/
$ mkdir build
$ cd build
$ $(cd ../src && pwd)/configure && make This is useful when you build for multiple platform configurations. For example on Android one can build for multiple API versions and multiple architectures (x86_64, armv7, aarch64, ...). |
Note for myself: Xavier proposed PR 4255 fix :-) |
I tested manually the commit 0c4785b merged into Python 3.6: it works as expected ;-) |
I also tested the 2.7 and 3.6 PRs before submitting them. |
Oh, I don't trust anyone, including myself :-) Since there is no automated, I chose to ("double") test manually your PRs. |
Oh I understand, there is no practical way to test that feature except manually. |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: