tree dc3fd08c08b22a95be0f0c2033a3e2d68a60b629
parent 7148293d96843ca868961313b00361504ec0c242
author Petr Viktorin <encukou@gmail.com> 1621896524 +0200
committer GitHub <noreply@github.com> 1621896524 -0400
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJgrC1MCRBK7hj4Ov3rIwAAgY4IAClfW+6NqxiGtX+l/+g7Jx6h
 UXnWddOMCU9S8JDPCKrqsGzUtErfuEcY/0NRRvG68clWORHTQVoo0SdWmCvHvIVx
 747cLwKnrKfiRuF2xkKIaw3Db3gqNbhYhntEsN0bA6mGEN6ugLzwQ5XBs4gUkwwG
 exSf+Ua4TiKvhCs/XoQtWrzwi2LoCpn5E/s5NztAQaGtOpJVJyU2qV3ICqWkbWvc
 6CGw7n8jsDJJonm3hz1s1XvJIPoMGhz6CBEYJnB0Z8mbRhuhfr6SLm0/5beZhR+o
 GtdLF4jnusGppX4VaBj/OkMc90DISJzkNDVA6XrIn/AE2cFvgw4E260/4hitBFU=
 =4Ran
 -----END PGP SIGNATURE-----
 

bpo-41282: Fix broken `make install` (GH-26329)

A previous commit broke a check in sysconfig when building cpython itself.
This caused builds of the standard library modules to search a wrong
location (the installed location rather than the source directory) for
header files with the net effect that a ``make install``
incorrectly caused all extension modules to be rebuilt again and
with incorrect include file paths.

When building Python, we need two distinct "include" directories:
- source .h files
- install target for .h files

Note that this doesn't matter except when building Python from source.

Historically:
- source .h files were in the distutils scheme under 'include'
- the install directory was in the distutils.command.install scheme
    under 'headers'

GH-24549 merged these; sysconfig is now the single source of truth and
distutils is derived from it.

This commit introduces a "secret" scheme path, 'headers', which contains
the install target. It is only present when building Python.
The distutils code uses it if present, and falls back to 'include'.

Co-authored-by: Ned Deily <nad@python.org>