[issue8027] distutils fail to determine c++ linker with unixcompiler if using ccache

Steve Dower added the comment: Distutils is now deprecated (see PEP 632) and all tagged issues are being closed. From now until removal, only release blocking issues will be considered for distutils. If this issue does not relate to distutils, please remove the component and reopen it. If y

[issue8027] distutils fail to determine c++ linker with unixcompiler if using ccache

Changes by Mihai Capotă : -- nosy: +mihaic ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.o

[issue8027] distutils fail to determine c++ linker with unixcompiler if using ccache

Erik Bray added the comment: I'm also inclined to agree that the buggy code (and it *is* buggy even if it was meant to fix something originally) should be removed outright. Nobody can point to a real world issue that it fixes anymore, yet we can point to real world consequences caused by this

[issue8027] distutils fail to determine c++ linker with unixcompiler if using ccache

Changes by Erik Bray : -- nosy: +erik.bray ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.o

[issue8027] distutils fail to determine c++ linker with unixcompiler if using ccache

Dan Mick added the comment: So the original author of the code says it's "likely no longer relevant", and it's clearly wrong, but no one has touched this in six years? Even moving the "linker[i] = self.compiler_cxx[i]" inside the if that checks for "env" would *still* limit the exposure of thi

[issue8027] distutils fail to determine c++ linker with unixcompiler if using ccache

Ronald Oussoren added the comment: I don't recall exactly why the universal build support is done the way it is, adding it is too long ago. The reason is likely no longer relevant with any reasonably up-to-date toolset. The patch was created around the time x86 support was added to OSX and a

[issue8027] distutils fail to determine c++ linker with unixcompiler if using ccache

Joshua J Cogliati added the comment: I looked and the autoconf variable for the c++ linker is CXXLINK, so I think the proper way to fix this would be to change sysconfig.py to look at both CXXFLAGS and CXXLINK, and create those and use it to define a cxxlink variable, and only if they are miss

[issue8027] distutils fail to determine c++ linker with unixcompiler if using ccache

Joshua J Cogliati added the comment: Let me try and explain what is trying to be done in the original code, what the fix was, and then discuss some possible better solutions. Original code: if target_lang == "c++" and self.compiler_cxx: linker[0] = self.compiler_cxx[0] Current code: if tar

[issue8027] distutils fail to determine c++ linker with unixcompiler if using ccache

Joshua J Cogliati added the comment: Looking at the patch (3078fdb7cf3d for Issue1488098) it has: if target_lang == "c++" and self.compiler_cxx: -linker[0] = self.compiler_cxx[0] One possibility is that that the problem was: linker[0] = self.compiler_cxx[0]

[issue8027] distutils fail to determine c++ linker with unixcompiler if using ccache

Changes by STINNER Victor : -- nosy: -haypo ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python

[issue8027] distutils fail to determine c++ linker with unixcompiler if using ccache

Ned Deily added the comment: The code in question was added a long time ago by Ronald as part of the initial OS X universal build support (3078fdb7cf3d for Issue1488098). I'm not exactly sure what problem it was trying to solve ao I'm not sure that it's 100% safe to totally remove rather than

[issue8027] distutils fail to determine c++ linker with unixcompiler if using ccache

Éric Araujo added the comment: Thanks for the patch and the testing. I’m not in a position to commit the patch; if no core developer does it in the coming week, feel free to ping python-dev to get action. You can also hop onto IRC at any time and see if someone here can finish this. ---

[issue8027] distutils fail to determine c++ linker with unixcompiler if using ccache

Joshua J Cogliati added the comment: On OSX 10.10.1, With the small_example, and with python 3.4.3 and: $ export CXX="env BAR=FOO g++" $ python3 setup.py build_ext build install --prefix=`pwd` running build_ext building '_example' extension swigging example/example.i to example/example_wrap.cpp

[issue8027] distutils fail to determine c++ linker with unixcompiler if using ccache

Joshua J Cogliati added the comment: > Does the patch fix things on Mac OS X and Linux? So far as I can tell, the code in question is to do something so that CXX variables like: export CXX="env BAR=FOO g++" work better. However, it is broken for that case, and since it has been broken since at

[issue8027] distutils fail to determine c++ linker with unixcompiler if using ccache

Éric Araujo added the comment: Does the patch fix things on Mac OS X and Linux? -- assignee: eric.araujo -> versions: -3rd party, Python 3.1, Python 3.2 ___ Python tracker ___ _

[issue8027] distutils fail to determine c++ linker with unixcompiler if using ccache

Joshua J Cogliati added the comment: Here is an example to use to test for this bug. Proper use on my computer (PYTHONPATH may need adjusting on other systems): Python2: cd small_example python setup.py build_ext build install --prefix=`pwd` export PYTHONPATH=`pwd`/lib64/python2.7/site-packages

[issue8027] distutils fail to determine c++ linker with unixcompiler if using ccache

Joshua J Cogliati added the comment: This bug is still in Python 3.5.0a2 (but first issue 23644 needs to be fixed before g++ can be used at all) Attached is a patch for Python 3.5.0. -- versions: +Python 3.5 Added file: http://bugs.python.org/file38530/fix-distutils-350.patch

[issue8027] distutils fail to determine c++ linker with unixcompiler if using ccache

Xuefer x added the comment: even with CXX="x86_64-openwrt-linux-gnu-g++ -pthread -shared" /usr/src/xuefer/openwrt/trunk/staging_dir/host/bin/python setup.py build it's donig x86_64-openwrt-linux-gnu-g++ gcc -pthread -shared -- ___ Python tracke

[issue8027] distutils fail to determine c++ linker with unixcompiler if using ccache

Xuefer x added the comment: please fix this bug. it seems the patch no longer applies to the current 2.7/3.4 code but the bug is still reproduce-able in another way i have CXX="ccache_cxx -pthread -shared" but what actually happen is: ccache_cxx gcc -pthread -shared ... x86_64-openwrt-linux-gnu

[issue8027] distutils fail to determine c++ linker with unixcompiler if using ccache

Changes by Éric Araujo : -- Removed message: http://bugs.python.org/msg113050 ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue8027] distutils fail to determine c++ linker with unixcompiler if using ccache

Éric Araujo added the comment: Hello Alexander, thanks for the report and patch. Could you add a test for the fixed behavior? -- assignee: tarek -> eric.araujo components: +Distutils2 nosy: +eric.araujo -terry.reedy versions: +3rd party ___ Python

[issue8027] distutils fail to determine c++ linker with unixcompiler if using ccache

Terry J. Reedy added the comment: With development of disutils2, distutils issues are not getting much separate attention. This may or may not get folded in to disutils2. -- nosy: +terry.reedy ___ Python tracker _

[issue8027] distutils fail to determine c++ linker with unixcompiler if using ccache

Changes by Mark Lawrence : -- stage: -> patch review versions: +Python 2.7, Python 3.1, Python 3.2 -Python 2.6 ___ Python tracker ___

[issue8027] distutils fail to determine c++ linker with unixcompiler if using ccache

New submission from Alexander Sulfrian : Hi, if using ccache (CC="ccache gcc --flags", CXX="g++") distutils will try to execute something like "g++ gcc --flags" as linker for c++ libraries. Patch attached. Alex -- assignee: tarek components: Distutils files: fix-distutils-with-ccache