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…
A static archive containing GCC LTO objects is more than a collection of target machine instructions. Its consumer may need to read GCC’s intermediate representation through a compatible compiler and linker plugin. When an archive is visible but linking fails, establish that tool relationship before changing library order. This guide pins GCC 14.2 and GNU…
Before shipping a C++ executable to an older root filesystem, compare the versioned symbols it needs with the symbols exported by the runtime that the image will actually load. Finding a file named libstdc++.so.6 is only the start. The useful release artifact is a required-versus-provided inventory bound to exact executable, dependency and provider identities. This…
A C++ library that links with one application but reports unresolved std::__cxx11 symbols with another needs an object-level ABI check. Changing the language dialect alone is not a reliable repair. With GCC’s libstdc++ dual ABI, the library declarations selected by _GLIBCXX_USE_CXX11_ABI can differ between translation units even when both are compiled as C++17. This procedure…
If an executable finds its direct library but that library cannot find a dependency, inspect which object owns the runtime search path. With the glibc loader, an executable’s DT_RUNPATH applies to its direct DT_NEEDED dependencies, not automatically to their children. Give each object the search policy needed for its own direct dependencies, then test the…
Package the runtime name recorded in each consumer’s DT_NEEDED entries, and keep it aligned with the library’s DT_SONAME and actual ABI. The implementation filename, runtime SONAME and development linker name have different jobs. Pointing an old major-version name at an incompatible new library does not create compatibility. This guide pins GNU BFD Binutils 2.44 and…