[issue38472] GCC detection in setup.py is broken

STINNER Victor added the comment: The workaround for this bug is to build Python using the command: LC_ALL=C make rather than running: make -- ___ Python tracker

[issue38472] GCC detection in setup.py is broken

Change by miss-islington : -- pull_requests: +29111 pull_request: https://github.com/python/cpython/pull/30932 ___ Python tracker ___

[issue38472] GCC detection in setup.py is broken

Change by miss-islington : -- nosy: +miss-islington nosy_count: 4.0 -> 5.0 pull_requests: +29110 pull_request: https://github.com/python/cpython/pull/30931 ___ Python tracker

[issue38472] GCC detection in setup.py is broken

STINNER Victor added the comment: New changeset a9503ac39474a9cb1b1935ddf159c0d9672b04b6 by Victor Stinner in branch 'main': bpo-38472: setup.py uses LC_ALL=C to check the C compiler (GH-30929) https://github.com/python/cpython/commit/a9503ac39474a9cb1b1935ddf159c0d9672b04b6 --

[issue38472] GCC detection in setup.py is broken

STINNER Victor added the comment: FYI distutils.unixccompiler has a private _is_gcc() function: def _is_gcc(self, compiler_name): # clang uses same syntax for rpath as gcc return any(name in compiler_name for name in ("gcc", "g++", "clang")) It's called with:

[issue38472] GCC detection in setup.py is broken

STINNER Victor added the comment: Ok, I reproduced the issue. I wrote PR 30929 to fix it. The issue only occurs when cross-compiling Python with GCC and a German locale. I can reproduce the issue on Fedora 35: $ LC_ALL=de_DE gcc -E -v Es werden eingebaute Spezifikationen verwendet.

[issue38472] GCC detection in setup.py is broken

Change by STINNER Victor : -- keywords: +patch pull_requests: +29108 stage: -> patch review pull_request: https://github.com/python/cpython/pull/30929 ___ Python tracker ___

[issue38472] GCC detection in setup.py is broken

Change by Irit Katriel : -- resolution: out of date -> versions: -Python 2.7, Python 3.5, Python 3.6, Python 3.7, Python 3.8 ___ Python tracker ___

[issue38472] GCC detection in setup.py is broken

Alex Grund added the comment: Yes this is still an issue. I'm trying to compile Python on an HPC system which uses modules (see e.g. LMod). Yes with LC_ALL=C it does write "gcc version 9.1.0 ..." -- status: pending -> open ___ Python tracker

[issue38472] GCC detection in setup.py is broken

Irit Katriel added the comment: Alex, is this still an issue with current python versions (>= 3.9)? And can you followup on Victor's questions? -- nosy: +iritkatriel resolution: -> out of date status: open -> pending ___ Python tracker

[issue38472] GCC detection in setup.py is broken

STINNER Victor added the comment: What are you trying to do? Compile Python? Cross-compile Python? > `setup.py` runs ` -E -v - /dev/null` to figure out include > and library paths from the compiler in the function `add_gcc_paths`. Are you talking about the add_cross_compiling_paths()

[issue38472] GCC detection in setup.py is broken

Alex Grund added the comment: This seems to be a locale issue. So a solution would be to use `LC_ALL=C` before invoking the compiler (or the cross-platform equivalent) -- ___ Python tracker

[issue38472] GCC detection in setup.py is broken

Change by Ned Deily : -- nosy: +doko ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue38472] GCC detection in setup.py is broken

New submission from Alex Grund : `setup.py` runs ` -E -v - /dev/null` to figure out include and library paths from the compiler in the function `add_gcc_paths`. However sample output from the compiler is: Es werden eingebaute Spezifikationen verwendet. COLLECT_GCC=g++ Ziel: