[issue20211] setup.py: do not add system header locations when cross compiling

2019-12-10 Thread Xavier de Gaye
Change by Xavier de Gaye : -- nosy: -xdegaye ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.py

[issue20211] setup.py: do not add system header locations when cross compiling

2017-03-31 Thread Serhiy Storchaka
Changes by Serhiy Storchaka : -- pull_requests: -867 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://m

[issue20211] setup.py: do not add system header locations when cross compiling

2017-03-31 Thread Donald Stufft
Changes by Donald Stufft : -- pull_requests: +867 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.

[issue20211] setup.py: do not add system header locations when cross compiling

2016-12-14 Thread Xavier de Gaye
Xavier de Gaye added the comment: Same patch, but this one is properly set to be handled by Rietveld. -- Added file: http://bugs.python.org/file45894/multiarch_2.patch ___ Python tracker ___

[issue20211] setup.py: do not add system header locations when cross compiling

2016-12-14 Thread Xavier de Gaye
Xavier de Gaye added the comment: >> this assumption is wrong for the multiarch case. > > Please explain why it is wrong. Sadly no explanations have been given, we have to take Matthias word for it. This new patch updates the add_multiarch_paths() method and includes LIBDIR and INCLUDEDIR in th

[issue20211] setup.py: do not add system header locations when cross compiling

2016-12-14 Thread Roundup Robot
Roundup Robot added the comment: New changeset d1b400943483 by Xavier de Gaye in branch '3.6': Issue #20211: Do not add the directory for installing C header files and https://hg.python.org/cpython/rev/d1b400943483 New changeset fcc9f19fcc13 by Xavier de Gaye in branch 'default': Issue #20211: M

[issue20211] setup.py: do not add system header locations when cross compiling

2016-12-10 Thread Xavier de Gaye
Xavier de Gaye added the comment: > this assumption is wrong for the multiarch case. Please explain why it is wrong. -- ___ Python tracker ___ __

[issue20211] setup.py: do not add system header locations when cross compiling

2016-12-10 Thread Chi Hsuan Yen
Chi Hsuan Yen added the comment: xdegaye's explanation is incorrect. The actual scene is much more complicated. First, let me explain why things may be broken. The wrong directory is included only if all of the following conditions are met: 1. PYTHON_FOR_BUILD is not installed with --prefix=/u

[issue20211] setup.py: do not add system header locations when cross compiling

2016-12-10 Thread Matthias Klose
Matthias Klose added the comment: this assumption is wrong for the multiarch case. -- ___ Python tracker ___ ___ Python-bugs-list mail

[issue20211] setup.py: do not add system header locations when cross compiling

2016-12-10 Thread Xavier de Gaye
Xavier de Gaye added the comment: When cross compiling, setup.py must not look for headers in the directory for installing C header files and must not look for libraries in the directory for installing object code libraries of the _native_ interpreter which is being used to run setup.py. Thoma

[issue20211] setup.py: do not add system header locations when cross compiling

2016-12-07 Thread Chi Hsuan Yen
Changes by Chi Hsuan Yen : -- nosy: +xdegaye ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.pytho

[issue20211] setup.py: do not add system header locations when cross compiling

2016-12-07 Thread Chi Hsuan Yen
Chi Hsuan Yen added the comment: Modified this issue a bit and add some experts on the build system -- nosy: +zach.ware title: setup.py: do not add invalid header locations -> setup.py: do not add system header locations when cross compiling versions: +Python 3.5, Python 3.6, Python 3.7