GoKawiilBoris Kolpackov proposes replacing autoconf-style feature probing with static platform tables
In a blog post dated 8 Oct 2026, developer Boris Kolpackov critiques the traditional autoconf/CMake approach of compiling and linking test programs to detect platform features, such as checking for the non-standard strl*() string functions. He argues the method is wasteful, since it keeps re-testing features on platforms where support has long been established, and brittle, since compile or link failures can stem from unrelated mistakes rather than genuine feature absence.
GoKawiil's interpretation of the reporting above, not reported fact.
The critique touches a widely used build-system practice, so Kolpackov's proposed alternative could influence how maintainers of C/C++ projects handle cross-platform configuration going forward. Framing probing as inherently fragile suggests build tooling may need to shift toward curated, versioned platform data rather than runtime compile tests, though this remains the author's own argument rather than an industry consensus.
- Autoconf-style probing compiles test programs to infer whether a platform supports certain features.
- Kolpackov says this approach wastes build time on platforms with known, long-standing support.
- He also argues probing is brittle because compile/link failures can arise from causes unrelated to actual feature absence.
Source: build2.org, 2026-10-08
Published there as: “How to Fix autoconf-style Configuration Probing”
Read the original report → The summary and analysis above are GoKawiil's own, written from reporting by the source above. Facts and quotes belong to the original publisher.