STINNER Victor added the comment:
> However in native builds (not cross-compiling) these variables/directories
> are ignored which leads to failure of e.g. building the BZip2 extension
> (among others).
Python does not explicitly ignore these environment variable, so I'm not sure
how setup.
STINNER Victor added the comment:
> This did work ages ago, but was broken when it was decided that compiler
> paths (output of `gcc -E -v`) is no longer used for native builds and that
> function was later even renamed:
> https://github.com/python/cpython/commit/32f5fdd7f4213743fe2f6eedd0fe
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 variables
