Linux workstation

Upstream software project

bison

Runtime support files used by Bison-generated parsers

About bison

Runtime support files used by Bison-generated parsers

This project links 9 native package records across 3 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): 3 package records; Debian 13 (Trixie): 3 package records; Fedora 44: 3 package records. Catalog coverage diagram, not an application screenshot.bison: recorded package coverageDebian 12 (Bookworm)3 recordsDebian 13 (Trixie)3 recordsFedora 443 records
OpenFactory diagram of linked package records. It is not an application screenshot.

Project identity

Project
bison
Publisher
Not authoritatively mapped
Native package records
9
Operating systems
debian-12, debian-13, fedora-44
License expression
GPL-3.0-or-later AND GPL-3.0-or-later WITH Autoconf-exception-generic-3.0 AND GPL-3.0-or-later WITH Bison-exception-2.2 AND GPL-2.0-or-later AND GPL-2.0-or-later WITH Autoconf-exception-generic AND LGPL-3.0-or-later AND LGPL-2.1-or-later AND LGPL-2.0-or-later AND FSFULLR AND GFDL-1.3-or-later AND X11
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.

Bison is a general purpose parser generator that converts a grammar description for an LALR(1) context-free grammar into a C program to parse that grammar. Bison can be used to develop a wide range of language parsers, from ones used in simple desk calculators to complex programming languages. Bison is upwardly compatible with Yacc, so any correctly written Yacc grammar should work with Bison without any changes. If you know Yacc, you shouldn't have any trouble using Bison. You do need to be very proficient in C programming to be able to use Bison. Bison is only needed on systems that are used for development. If your system will be used for C development, you should install Bison.

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. bison

    Debian 12 (Bookworm) / devel / source bison

    2:3.8.2+dfsg-1+b1

    YACC-compatible parser generator

    amd64arm64bookworm
  2. bison-doc

    Debian 12 (Bookworm) / non-free/doc

    1:3.8.2+repack-1

    Documentation for the Bison parser generator

    allbookworm
  3. libbison-dev

    Debian 12 (Bookworm) / libdevel / source bison

    2:3.8.2+dfsg-1+b1

    YACC-compatible parser generator - development library

    amd64arm64bookworm

Debian 13 (Trixie)

  1. bison

    Debian 13 (Trixie) / devel / source bison

    2:3.8.2+dfsg-1+b2

    YACC-compatible parser generator

    amd64arm64trixie
  2. bison-doc

    Debian 13 (Trixie) / non-free/doc

    1:3.8.2+repack-1

    Documentation for the Bison parser generator

    alltrixie
  3. libbison-dev

    Debian 13 (Trixie) / libdevel / source bison

    2:3.8.2+dfsg-1+b2

    YACC-compatible parser generator - development library

    amd64arm64trixie

Fedora 44

  1. bison

    Fedora 44 / Unspecified / source bison

    3.8.2-15.fc44

    GNU general-purpose parser generator

    aarch64x86_6444
  2. bison-devel

    Fedora 44 / Unspecified / source bison

    3.8.2-15.fc44

    -ly library for development using Bison-generated parsers

    aarch64i686x86_6444
  3. bison-runtime

    Fedora 44 / Unspecified / source bison

    3.8.2-15.fc44

    Runtime support files used by Bison-generated parsers

    aarch64x86_6444

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.