You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by po...@apache.org on 2026/10/20 09:14:28 UTC

(airflow) 17/20: Document the stricter C extension builds of the hardened images

This is an automated email from the ASF dual-hosted git repository.

potiuk pushed a commit to branch hardened-python-base-images
in repository https://gitbox.apache.org/repos/asf/airflow.git

commit cdff2105257b923a5c04363c95d78b632c92f09b
Author: Jarek Potiuk <ja...@potiuk.com>
AuthorDate: Sun Oct 11 10:47:42 2026 +0100

    Document the stricter C extension builds of the hardened images
    
    Users extending the image with old source distributions hit the same GCC 14 errors as CI, and need to know how to relax them.
    
    Generated-by: Claude Opus 5
    Claude-Session: https://claude.ai/code/session_014np1fVAxHmGaBFt3qebJ8x
---
 docker-stack-docs/build.rst | 7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/docker-stack-docs/build.rst b/docker-stack-docs/build.rst
index 598ec7aa066..69fc721b02a 100644
--- a/docker-stack-docs/build.rst
+++ b/docker-stack-docs/build.rst
@@ -938,6 +938,13 @@ previous images that can matter when you extend or run the image are:
   wrong Python. The image build fails when this happens, but a custom image that installs extra apt
   packages is not checked. Check what ``apt-get install --simulate`` would install before adding packages
   that might depend on ``python3``, and prefer the runtime library packages over their ``-dev`` variants.
+* **C extensions are compiled more strictly.** The Debian 13 images come with GCC 14, which turns
+  incompatible pointer types, integer conversions and implicit function declarations into errors, and the
+  hardened Python passes ``-Werror=implicit-function-declaration`` on to every C extension it builds. Old
+  source distributions that compiled with warnings before - for example ``xmlsec`` 1.3.14 or ``ibm-db``
+  3.2.0 - fail to build. Prefer versions with wheels or newer releases; if you have to build such a
+  package, setting ``CFLAGS="-Wno-error=incompatible-pointer-types -Wno-error=int-conversion
+  -Wno-error=implicit-function-declaration"`` for the installation turns the errors back into warnings.
 * **apt does not refresh the shared library cache.** The base images ship ``libc-bin`` without its
   ``dpkg`` trigger, so installing a shared library does not run ``ldconfig``, and anything that looks
   libraries up through the cache - such as ``ctypes.util.find_library()`` - does not find it. The image