Reproducible system builds, custom packages, root filesystem layouts, startup services and persistent data. Buildroot is a build and integration tool; it is not a runtime layer between the kernel and applications.
A new input section can survive linking even when a custom linker script never mentions it. GNU BFD ld can create or select an output section for that orphan and place it according to target-specific rules. Treat a successful link as a reason to inspect the placement, not proof that the script accounts for every…
Qualify an AddressSanitizer build in stages: the compiler must instrument the application, the image must provide the matching userspace runtime, and the process must initialize its shadow-memory layout before a bug report is meaningful. A successful cross-link establishes none of the target startup or resource limits by itself. This guide pins GCC 14.2, its bundled…
When a local source edit does not affect a Buildroot package, compare the checkout file, synchronized build-tree file and generated output as three separate artifacts. OVERRIDE_SRCDIR does not compile directly in the original checkout. Its synchronization rules can preserve a newer destination file or exclude an input before the package build even starts. This guide…
A plugin boundary that exchanges polymorphic C++ objects needs more than matching exported function names. The host and plugin must agree on class definitions, runtime type information and exception identity. Test dynamic_cast and typed exception matching across the actual DSO boundary before treating the interface as compatible. This guide uses GCC 14.2, its libstdc++ ABI…
For 32-bit Arm objects, floating-point instruction support and floating-point argument passing are separate compatibility questions. A library can use hardware floating-point instructions while still accepting parameters through the base calling convention. Before mixing vendor archives, inspect the ABI attributes and the actual public call boundary, not just the CPU name. This procedure uses GCC 14.2’s…
Two shared libraries can define a global with the same name and still have both libraries’ internal references resolve to one provider. Before applying a binding flag, decide whether that name is an intentional process-wide interface or accidental private-state exposure. The repair changes semantics, not just the export list. This guide uses GCC 14.2, GNU…
A plugin can pass the shared-library link and still fail during dlopen because its thread-local storage model requires static TLS space that the running process cannot provide. Establish the model and loader allocation path before treating the failure as a missing file or generic heap exhaustion. This guide pins GCC 14.2, Binutils 2.44 and glibc…
Adding -fPIC to a final shared-library link does not rewrite a dependency archive’s existing machine instructions. When a static library moves into a shared object, identify the specific member and relocation that the linker rejects, then rebuild the producer objects with the appropriate position-independent code policy. This procedure is pinned to GCC 14.2 and GNU…
A strong replacement can override a weak fallback only if the replacement participates in the relevant link. Putting the replacement into an archive does not guarantee that its member is extracted. Diagnose symbol binding and object selection separately, then prove which implementation the final executable calls. This guide uses ordinary ELF objects with GCC 14.2…
A registration table can exist in an object file and still disappear from the final executable. Diagnose three separate gates: did the compiler emit the entry, did the linker select its object, and did section garbage collection retain the entry and its callback? A repair at one gate does not automatically satisfy the others. This…