[issue40642] Cpython "pystate.h" subdirectory wrong

STINNER Victor added the comment: I mark this issue as a duplicate of bpo-39026. -- resolution: -> duplicate stage: patch review -> resolved status: open -> closed superseder: -> pystate.h contains non-relative of initconfig.h include causing macOS Framework include failure ___

[issue40642] Cpython "pystate.h" subdirectory wrong

STINNER Victor added the comment: Having two header files with the same name in two directories which are part of the include directories is causing issues like this one :-( For the internal C API, I solve the issue by adding "pycore_" prefix to filenames. Maybe pystate.h should be renamed

[issue40642] Cpython "pystate.h" subdirectory wrong

Xi Ruoyao added the comment: Dup of #39026. And the proposed fix is nack'ed in #39026. -- ___ Python tracker ___ ___ Python-bugs-l

[issue40642] Cpython "pystate.h" subdirectory wrong

Change by Xi Ruoyao : -- keywords: +patch nosy: +xry111 nosy_count: 3.0 -> 4.0 pull_requests: +23514 stage: -> patch review pull_request: https://github.com/python/cpython/pull/24744 ___ Python tracker _

[issue40642] Cpython "pystate.h" subdirectory wrong

Andrew Tomazos added the comment: After studying the include directives in the Include folder, I think the best fix would be: In Include/cpython/state.h: - #include "cpython/initconfig.h" + #include "initconfig.h" this will mean that state.h will find initconfig.h using a file-relat

[issue40642] Cpython "pystate.h" subdirectory wrong

Andrew Tomazos added the comment: Related: https://stackoverflow.com/q/63211981/1131467 -- ___ Python tracker ___ ___ Python-bugs-l

[issue40642] Cpython "pystate.h" subdirectory wrong

Andrew Tomazos added the comment: The problem occurs if you: #include on *nix systems. Note `/usr/include/` is in the system include path. One workaround is to `-I/usr/include/python3.8` and then `#include `. Another workaround is to comment out: // #include "cpython/initconfig.h

[issue40642] Cpython "pystate.h" subdirectory wrong

Eric V. Smith added the comment: Thanks for the info. It's weird that this is just showing up for you, and I assume works everywhere else. How are you invoking the compiler, via make, or something else? And, what's the gcc command line look like when this specific file fails? I grepped the

[issue40642] Cpython "pystate.h" subdirectory wrong

jpelizza added the comment: In hindsight I provided absolutely nothing, new to this, bound to make dumb mistakes. Compiler error: In file included from /usr/include/python3.8/pystate.h:129, from /usr/include/python3.8/genobject.h:11, from /usr/include/python

[issue40642] Cpython "pystate.h" subdirectory wrong

Eric V. Smith added the comment: Won't either one work, since "Include" is in the "search path"? Is this causing an actual problem? You have this marked as "compile error", but haven't shown any information about the error, such as what compiler, how it's being invoked, and what the error me

[issue40642] Cpython "pystate.h" subdirectory wrong

New submission from jpelizza : Line 9 of pystate.h is: #include "cpython/initconfig.h" should be: #include "./initconfig.h" since pystate.h is already inside cpython dir. -- components: C API messages: 369019 nosy: jpelizza priority: normal severity: normal status: open title: Cpython "