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
Compilation of python (modules) for foreign target platform problem. #71288
Comments
Compilation of python for foreign target platform problem. Host arch is x86_64, target arch is arm (arm32). Configuration is (target arch part):
Problem: option -I/usr/include passed to compiler during modules compilation. This lead to fails, due to target platform is different from host. Suggested patch resolve the issue for me. BTW, pass -I/usr/include is useless even for native builds. |
for 3.5 branch |
1 similar comment
for 3.5 branch |
for 2.7 branch |
1 similar comment
for 2.7 branch |
The 0002-* patches look fine, however the 0001-* patches are wrong if you are in a Multi-Arch environment, where you can find valid headers in /usr/include. From my point of view, the set of include and header directories should be directly initialized from the compiler defaults, and not hard coded. |
Matthias, This question is really for you: fc19031 (doko 2012-09-21 13:52:29 +0200 422) if multiarch_path_component != '': |
sorry, I don't understand your last comment. |
This mean that code for search in /usr/include/... in multiarch environment was added by you in commit fc19031 2012-09-21 13:52:29 +0200, so in my suggestion I just don't change behaviour of you code. As for my opinion, any additions of -I/usr/include/... are wrong: compiler either see it without such -I... or shouldn't see it at all (as for cross), or require hint from builder (something like CURSES_CFLAGS=-I/home/bluser/new_curses/include). |
2.7 and 3.5 are no longer maintained. Please create a new issue if you are still having this problem with a current version (>= 3.9). |
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: