Understanding API and ABI in Linux OS and Applications

"API" and "ABI" sound alike, but they break in different ways. An API change stops your code from compiling; an ABI change lets it compile and then crashes it, or stops a program you downloaded from starting at all. This guide explains both in the Linux context, shows how to inspect them on a real binary, and explains the error messages you will meet when an ABI does not match.

1. What an API is

An API is the set of functions, data types and constants that one piece of software offers another, described at the source level. In C on Linux, it is what the header files declare:

• the C standard library and POSIX functions, such as printf, open, read and fork;
• library APIs, such as OpenSSL's or libcurl's functions;
• the system call interface, which user programs normally reach through glibc wrappers rather than directly.

An API tells a programmer what to call and what arguments to pass. It says nothing about which CPU register an argument travels in.

2. What an ABI is

An ABI is the contract between pieces of compiled code. Two binaries share an ABI when they agree on:

3. API and ABI side by side

An API change can keep the ABI intact (adding a new function), and an ABI change can keep the API intact (adding a field to a struct that callers allocate themselves). That second case is the dangerous one: the code still compiles, so nobody notices until an old binary misreads memory.

4. A worked example

Take the classic program:

#include <stdio.h>

int main(void) {
    printf("Hello, Linux!\n");
    return 0;
}

printf and stdio.h are the API. Compile it and inspect the ABI facts the compiler recorded:

gcc hello.c -o hello
file hello                  # ELF 64-bit LSB pie executable, x86-64, dynamically linked
readelf -d hello | grep NEEDED    # Shared library: [libc.so.6]
objdump -T hello | grep GLIBC     # e.g. puts with version GLIBC_2.2.5
ldd hello                   # where each needed library is found on this system

Two things stand out. The compiler replaced printf with puts, because the string has no format specifiers: the API you wrote is not always the symbol that ends up in the binary. And the symbol carries a version tag. The binary will run on any system whose glibc provides at least that version of every symbol it uses. Build it on a system with glibc 2.34 or newer and you will also see __libc_start_main tagged GLIBC_2.34, so even this hello-world will not start on an older system.

5. How Linux keeps ABIs stable

• The kernel's user-space ABI is stable. System call numbers and behaviour are not changed in ways that break existing programs, which is why a binary built years ago can still run on a current kernel.
• The kernel's internal API and ABI are not stable. Kernel modules must be rebuilt for each kernel version; tools such as DKMS automate this for drivers.
• glibc is backward compatible through symbol versioning. When a function's behaviour changes, glibc keeps the old version alongside the new one. Programs built against an older glibc run on newer systems, but not the other way round.
• Shared libraries signal ABI breaks with the soname. libssl.so.3 and libssl.so.1.1 are different ABIs; a program built for one cannot load the other.
• C++ adds its own ABI questions: name mangling, the layout of standard library types, and exceptions. GCC's libstdc++ has used a newer ABI for std::string and std::list since GCC 5, while keeping the old one available.

6. ABI errors you will actually see

Distributions built on musl libc, such as Alpine Linux, have a different C library ABI from glibc systems, so a glibc binary will not run there unchanged. Language ecosystems handle this with tagged builds: Python wheels are labelled manylinux (glibc) or musllinux, and Node.js native add-ons built on Node-API keep working across Node.js versions.

7. Good practice for developers

8. Running this on Domain India

• Shared hosting (cPanel, DirectAdmin, Webuzo): jailed SSH access is available on every shared hosting plan. It is off by default; ask support to enable it for your account, and log in with an SSH key. You cannot install system libraries, and tools available inside the jailed shell vary; ask support. The cPanel and DirectAdmin servers run CloudLinux 8 (measured September 2026), so a binary built on a much newer distribution may fail with a GLIBC error; run ldd --version over SSH to see the glibc version before you upload one. PHP's process functions are disabled on cPanel, so PHP cannot launch uploaded programs; see PHP disabled functions on shared hosting. Enabling and accessing jailed SSH covers access.
• App Platform: you control the whole user-space ABI through your Dockerfile's base image; Node.js apps are detected automatically and other languages deploy with a Dockerfile. See App Platform: getting started.
• VPS: a self-managed server with root access and no cPanel, where you choose the distribution, install libraries and build software yourself.

Frequently asked questions

Ready to run your own builds? Deploy with a Dockerfile on the App Platform, take full control on a VPS, or open a support ticket to ask about jailed SSH on your shared hosting.