Python-3.12.4 install process broken

[blastwave]

Bug report

Bug description:

Python-3.12.4 can be configured out of tree with a trivial configure option once
one accepts that OpenSSL is strange : 

../Python-3.12.4/configure --prefix=/usr/local --enable-shared --with-openssl-rpath=/usr/local/lib --with-openssl=/usr/local

Well that results in something that builds fine. No complaints.

The build is done as an ordinary user and then the install is to be done as root where the
process blows up : 

.
.
.
rm -f /usr/local/share/man/man1/python3.1
(cd /usr/local/share/man/man1; ln -s python3.12.1 python3.1)
if test "xupgrade" != "xno"  ; then \
        case upgrade in \
                upgrade) ensurepip="--upgrade" ;; \
                install|*) ensurepip="" ;; \
        esac; \
        LD_LIBRARY_PATH=/usr/local/build/Python-3.12.4_xeon_linux.004 ./python -E -m ensurepip \
                $ensurepip --root=/ ; \
fi
Looking in links: /var/tmp/root/tmp5ehhx0p2
Requirement already satisfied: pip in /usr/local/lib/python3.12/site-packages (24.0)
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv
o# 

Setting some env var PIP_ROOT_USER_ACTION=ignore means nothing and the same error
happens.

Therefore the install process is broken.

CPython versions tested on:

3.12

Operating systems tested on:

Linux

[blastwave]

another trick documented no where easy " --without-ensurepip ".

[FFY00]

Can you describe the environment where you are attempting to build?

Perhaps reproducible instructions using a container might help us reproduce the issue on our side.