Tags: zanieb/python-build-standalone
Tags
unix: normalize build configuration to aid portability This commit implements a long desired feature to normalize the build configuration in various distribution files post build but pre packaging. The goal of this general feature is to make distributions highly portable. Before, configurations (which were used to e.g. compile extension modules) referenced build environment paths, like `/tools`. This is not desirable and can confuse downstream users when unexpected settings are used. The impetus for this work is astral-sh#194. As part of this change we strip the `-fdebug-default-version` argument from `CFLAGS` to restore CFLAGS compatibility with GCC. There's no doubt additional settings that could be normalized. Those can be implemented as follow-ups.
downloads: CPython 3.11.4 -> 3.11.5 We remove a patch for limits.h handling because upstream incorporated a fix (from a bug report I filed). And it looks like upstream backported build system changes to build with OpenSSL 3.0 on Windows. We need to update our code accordingly. We really should be building against OpenSSL 3.0. But that's scope bloat. We'll get there.
unix: patch configure.ac instead of configure Python 3.11 introduces a configure based mechanism for configuring extension modules. It is looking like we'll need to bulk modify behavior to get it to work with our opinionated way of statically linking extension modules. In preparation for that, this commit changes all our configure patches to patch `configure.ac` instead of `configure` so we can make changes at the source without bloating patch size. As part of this, I also moved the patches to standalone files, as having to copy inline patches with tabs was historically annoying. This approach is much easier.
PreviousNext