Install gnucobol with Homebrew, apk, apt, dnf, MacPorts, Nix, zypper

Project links

• Homepage
• Upstream docs
• Package manager page

Commands and aliases

• cob-config
• cobc
• cobcrun

Project history

The project began as OpenCOBOL around 2002. The FAQ credits Keisuke Nishida as the initial developer, influenced by TinyCOBOL, records the first public 0.9.0 release on January 25, 2002, and notes Roger While taking the lead developer role in 2004. OpenCOBOL 1.0 followed in 2007, and the 1.1 line became the basis for the GNU-era package.

OpenCOBOL was accepted as an official GNU project on September 27, 2013 and first rebranded as GNU Cobol. The spelling GnuCOBOL became preferred in September 2014, Simon Sobisch became project lead in 2014, and the FAQ records Free Software Foundation copyright assignment becoming legally binding in June 2015 for the source tree dating back to the original public release.

Later releases expanded dialect handling, diagnostics, runtime behavior, source-level debugging, report writer support, JSON and XML generation, and compatibility with older and vendor-specific COBOL styles. The project page describes GnuCOBOL 3.2 as producing native executables and supporting Linux, BSD, proprietary Unix systems, macOS, Windows, and other platforms.

Adoption history

GnuCOBOL serves a particular adoption niche: organizations and individual programmers with COBOL code can compile and test it with a free compiler, often on commodity Unix-like systems. The FAQ says OpenCOBOL and GnuCOBOL have been used in production environments, while also warning that each production use needs risk analysis.

Its package-manager significance is amplified by COBOL's long commercial history. GnuCOBOL lets package repositories ship a working COBOL compiler without tying users to proprietary mainframe or vendor compiler ecosystems, and its LGPL runtime allows commercial use of generated programs under the stated license terms.

How it is used

Practitioners use cobc to compile COBOL files into modules, object files, C output, or executable programs. Typical workflows include building legacy COBOL with dialect options such as -std, compiling free-format or fixed-format source, integrating C libraries, running modules with cobcrun, and using compiler listings or warning modes during modernization.

The package is also used for teaching, migration experiments, CI checks for COBOL code, and prototyping around vendor dialects. Because GnuCOBOL emits C, users can lean on the host compiler, linker, debugger, and platform libraries rather than requiring a dedicated COBOL runtime environment for every step.

Why package nerds care

GnuCOBOL is the rare package that makes a historically enterprise language feel like a normal open-source compiler dependency. For package maintainers it is a bridge between COBOL archives and modern Unix build systems; for language-runtime collectors it is a compact way to keep COBOL executable on laptops, CI runners, and free-software distributions.

Timeline

• 2002: OpenCOBOL 0.9.0 was publicly released.
• 2004: Roger While took the lead developer role.
• 2013: OpenCOBOL was accepted as an official GNU project and rebranded as GNU Cobol.
• 2014: GnuCOBOL became the preferred spelling and Simon Sobisch became project lead.
• 2015: FSF copyright assignment for the source tree became legally binding.
• 2023: GnuCOBOL 3.2 was released.

Related projects

• Related projects include TinyCOBOL, the COBOL 85/2002/2014 standards, GCC or another configured C compiler, libcob, GDB, OpenCOBOLIDE, and vendor dialects such as IBM, Micro Focus, ACUCOBOL-GT, RM/COBOL, and GCOS.

Sources

• https://ftp.gnu.org/gnu/gnucobol/
• https://gnucobol.sourceforge.io/
• https://gnucobol.sourceforge.io/doc/gnucobol.html
• https://gnucobol.sourceforge.io/faq/