Safe to link to static libstdc++ from shared library?
Jonathan Wakely
jwakely@redhat.com
Fri Nov 14 15:12:39 GMT 2025
On Fri, 14 Nov 2025 at 14:48, Fredrik Orderud <forderud@gmail.com> wrote:
>
> On Fri, Nov 14, 2025 at 3:18 PM Jonathan Wakely <jwakely@redhat.com> wrote:
> > On Fri, 14 Nov 2025 at 14:10, Fredrik Orderud <forderud@gmail.com> wrote:
> > > On Fri, Nov 14, 2025 at 2:52 PM Jonathan Wakely <jwakely@redhat.com> wrote:
> > > > On Fri, 14 Nov 2025 at 13:45, Fredrik Orderud <forderud@gmail.com> wrote:
> > > > > ASK: Are there any documented or undocumented limitations on
> > > > > -static-libstdc++ usage when building shared libraries on Linux?
> > > >
> > > > The problem is your use of --exclude-libs - that won't work.
> > > >
> > > > You can't pretend there are no dependencies on the C++ runtime like
> > > > that, the symbols in libstdc++ need to be globally visible so that the
> > > > linker can properly resolve them across different ELF objects.
> > >
> > > Ok, so what we're doing is supported if we just let the libstdc++
> > > symbols "leak out" from our shared library?
> > >
> > > If so, then will we still avoid run-time dependencies to the
> > > distro-provided libstdc++?
> >
> > I don't recommend trying to avoid those dependencies. See below.
> >
> > > Also, will it be safe for the client executable to potentially use a
> > > different libstdc++ version than what's used in our shared library?
> >
> > In general, no.
> >
> > I don't recommend trying to do this at all. The approach I would
> > recommend is deciding on a minimum version of libstdc++.so.6 that you
> > support (based on the oldest distro you need to support) and then
> > building against that, and not trying to bundle libstdc++ symbols in
> > your library at all. Just let them be resolved by the system
> > libstdc++.so.6 provided by the target system.
> >
> > On RHEL-like systems this is trivial, by using the GCC Toolset
> > packages. If you're trying to support a wider range of distros with a
> > single binary, that's going to be harder. But if you build against the
> > oldest libstdc++.so.6 that you need to support (e.g. in a VM or
> > container running the old distro) then your library should be able to
> > run on any distro that provides a libstdc++.so.6 that is no older than
> > the one you built against.
> >
> > Since you're using C++11 features, you should not try to use anything
> > older than the libstdc++ that came with GCC 5, as that's when C++11
> > support became ABI-stable.
>
> Thanks for clear actionable answers, Jonathan.
>
> We're already building our shared library in an old Linux container
> with glibc 2.27 and libstdc++ 20191114 for improved backwards
I don't know what libstdc++ 20191114 is. Presumably the value of
__GLIBCXX__ but that's not meaningful, see the discussion of
__GLIBCXX__ at https://gcc.gnu.org/onlinedocs/libstdc++/manual/abi.html#abi.versioning.history
(and the suggestion to use _GLIBCXX_RELEASE instead).
> compatibility. However, it then becomes a tension between the oldest
> libstdc++ version supported and the newest C++ version supported. We
> basically want to adopt C++23 and newer internally in our shared lib
> while still being compatible with old systems. My hope was that static
> linking to libstdc++ could help eliminate that problem.
That's unlikely to work, because the C++23 ABI is not stable yet. You
can't mix and match any objects compiled with C++23 mode by different
GCC versions, because the C++23 features like std::expected might not
be ABI compatible between GCC 13 and GCC 14, for instance.
More information about the Libstdc++
mailing list