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
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: x86_64-pc-linux
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
<https://bugs.python.org/issue38
New submission from Alex Grund :
In e.g. Linux users can set CPATH and LIBRARY_PATH to a list of paths
considered by e.g. GCC, Clang, ... as if they were passed to `-I`, `-L`
These paths show up in the verbose compiler output too.
However in native builds (not cross-compiling) these
Alex Grund added the comment:
The changelog wrongfully links to https://bugs.python.org/issue41928 instead of
this issue.
Also the fix introduced a regression: Trying to copy a directory now raises a
FileNotFoundError
--
nosy: +Alex Grund
New submission from Alex Grund :
After https://bugs.python.org/issue43219 was resolved the function now shows
faulty behavior when the source is a directory:
`copy_file('/path/to/dir', '/target')` throws a FileNotFoundError while
previously it was a IsADirectoryError whic
New submission from Alex Grund :
When configuring with `LIBS=-lpthread` env var set, the pthread detection
assumes that no flag is necessary and distutils will build all extensions
without any flag for pthreads. This will make them fail, when they use certain
pthread symbols on certain
