Upstream software project

abi-compliance-checker

A Compliance Checker For library ABIs

About abi-compliance-checker

A Compliance Checker For library ABIs

This project links 7 native package records across 5 recorded operating-system releases. Compare the retained versions and architectures below, then open the package for your own release.

These are catalog observations, not a guarantee of installation, compatibility, or upstream support.

Visit project website

Project pictures and package coverage

Debian 12 (Bookworm): 2 package records; Debian 13 (Trixie): 2 package records; openSUSE Leap 15.6: 1 package records; openSUSE Leap 16.0: 1 package records; openSUSE Tumbleweed: 1 package records. Catalog coverage diagram, not an application screenshot.abi-compliance-checker: recorded package coverageDebian 12 (Bookworm)2 recordsDebian 13 (Trixie)2 recordsopenSUSE Leap 15.61 recordsopenSUSE Leap 16.01 recordsopenSUSE Tumbleweed1 records
OpenFactory diagram of linked package records. It is not an application screenshot.

Project identity

Project
abi-compliance-checker
Publisher
Not authoritatively mapped
Native package records
7
Operating systems
debian-12, debian-13, opensuse-leap-15-6, opensuse-leap-16-0, opensuse-tumbleweed
License expression
LGPL-2.1-only
Metadata completeness
100/100 (not a software quality rating)
Homepage
Visit upstream site
Source repository
Not reported

Source-reported description

The fullest retained description is shown with its source. Distribution packaging descriptions may include downstream details.

ABI Compliance Checker (ACC) is an easy-to-use tool for checking backward binary compatibility (BC) of a shared C/C++ library. It checks header files along with shared libraries of old and new versions and analyzes changes in Application Binary Interface (ABI) that may cause compatibility problems: changes in calling stack, v-table changes, removed symbols, etc. Breakage of the binary compatibility may result in crashing or incorrect behavior of applications built with an old version of the library if they run on a new one. The tool is intended for library developers and operating system maintainers who are interested in ensuring binary compatibility, i.e. allow old applications to run with newer library versions without the need to recompile.

Description source

Packages by operating system

Compare recorded versions, then open a package for dependency, file, checksum, and repository evidence. Version strings are distribution-specific, not a ranking of newer software.

Debian 12 (Bookworm)

  1. Package abi-compliance-checker

    bookworm (Debian 12 (Bookworm)) (devel): tool to compare ABI compatibility of shared C/C++ library versions

    2.3-2: all

  2. Package dh-acc

    bookworm (Debian 12 (Bookworm)) (devel): debhelper addon to compare ABI compatibility of shared C/C++ library versions

    2.3-2: all

    Source: abi-compliance-checker

Debian 13 (Trixie)

  1. Package abi-compliance-checker

    trixie (Debian 13 (Trixie)) (devel): tool to compare ABI compatibility of shared C/C++ library versions

    2.3-3: all

  2. Package dh-acc

    trixie (Debian 13 (Trixie)) (devel): debhelper addon to compare ABI compatibility of shared C/C++ library versions

    2.3-3: all

    Source: abi-compliance-checker

openSUSE Leap 15.6

  1. Package abi-compliance-checker

    leap-15.6 (openSUSE Leap 15.6) (Unspecified): A Compliance Checker For library ABIs

    2.3-bp156.3.1: noarch

    Source: abi-compliance-checker

openSUSE Leap 16.0

  1. Package abi-compliance-checker

    leap-16.0 (openSUSE Leap 16.0) (Unspecified): A Compliance Checker For library ABIs

    2.3-bp160.1.10: noarch

    Source: abi-compliance-checker

openSUSE Tumbleweed

  1. Package abi-compliance-checker

    tumbleweed (openSUSE Tumbleweed) (Unspecified): A Compliance Checker For library ABIs

    2.3-5.3: noarch

    Source: abi-compliance-checker

Project resources and further reading

Mapping provenance

Only source-backed identity signals create public cross-OS links. A reviewer can later approve or dispute an inferred relationship without rewriting native package history.

No field-level source record is published yet.