使用 Homebrew, apk, apt, MacPorts, Nix, pacman, zypper 安装 ecl

项目链接

• 主页
• 仓库
• 上游文档
• 软件包管理器页面

命令和别名

• ecl
• ecl-config

项目历史

The ECL manual traces the project through the Kyoto Common Lisp family. KCL was developed in 1984 at Kyoto University's Research Institute for Mathematical Sciences by Taiichi Yuasa and Masami Hagiya, with an implementation partly in C and partly in Common Lisp and a Lisp-to-C translator. Later descendants included Ibuki Common Lisp, DELPHI Common Lisp, Austin Kyoto Common-Lisp, GNU Common Lisp, and HCL.

Giuseppe Attardi began the ECL line after leaving DELPHI in 1994 and returning to the University of Pisa. The manual explains the name as both Embeddable Common Lisp and ECoLisp, tied to the goal of integrating Lisp code with other languages at a time when Lisp programmers were becoming less common.

Juan Jose Garcia-Ripoll later started the ECLS or ECL-Spain effort from the ECoLisp sources. Its immediate goals were practical package-nerd goals: portability, 64-bit cleanliness, bootstrapping without another Lisp implementation, and restoring the ability to link ECL with C programs. That fork eventually became the continuing community ECL project.

After another maintenance gap beginning in 2013, Daniel Kochmanski took over maintenance in 2015 with Garcia-Ripoll's consent, and Marius Gerbershagen became co-maintainer in 2020. Current development, according to the manual, focuses on ANSI compliance, compatibility with the Common Lisp library ecosystem, bug fixing, speed, and portability.

采用历史

ECL's adoption has been tied to portability and embedding rather than to a single flagship application. Its manual emphasizes C interoperability, modular runtime construction, native CLOS support, bytecode fallback for systems without a C compiler, and ANSI Common Lisp compliance, which explains its presence across Unix-like package managers.

The Homebrew, Debian, Ubuntu, Alpine, Arch, Nix, MacPorts, and openSUSE package names in the batch input reflect the same pattern: ECL is a standard packaged Common Lisp implementation rather than an application-specific one-off. Its upstream GitLab tags show active releases through 2026, including 26.5.5.

使用方式

Users typically install ECL to run an interactive Common Lisp environment, compile Lisp systems, or embed Lisp into a C or C++ application. The `ecl` executable provides the runtime and REPL, while `ecl-config` exposes compiler and linker flags for programs that build against ECL.

The manual's key usage distinction is that compiled Lisp functions follow standard C calling conventions, letting C and Lisp call each other without a separate foreign-function layer. That makes ECL especially relevant for applications that want Common Lisp as an extension language or as a compiled library component.

为什么软件包爱好者会关心

ECL matters to package maintainers because it is both a compiler toolchain and a library runtime. Packaging it means caring about C compilers, runtime modules, dynamic loading, threads, binary images, and ABI-facing configuration through `ecl-config`, not just shipping a single REPL binary.

Its lineage also makes it historically interesting: a modern package-manager formula connects directly back to the KCL family of Lisp-to-C systems, while still tracking contemporary Common Lisp library compatibility and portability work.

时间线

• 1984: Kyoto Common Lisp is developed at Kyoto University.
• 1988: DELPHI Common Lisp is released as an extended KCL descendant.
• 1994: Giuseppe Attardi begins the ECL line at the University of Pisa.
• 1990s: The ECLS or ECL-Spain fork focuses on portability, 64-bit cleanup, bootstrapping, and C linking.
• 2015: Daniel Kochmanski becomes maintainer.
• 2020: Marius Gerbershagen becomes co-maintainer.
• 2026: Upstream GitLab tags include ECL 26.5.5.

Related projects

• Kyoto Common Lisp is the oldest ancestor named in ECL's manual.
• GNU Common Lisp is another AKCL descendant in the same family tree.
• Maxima is named in the ECL history as the computer algebra system that motivated GNU Common Lisp.
• Common Lisp libraries and ANSI Common Lisp conformance are current compatibility targets for ECL development.

来源

• https://ecl.common-lisp.dev/static/manual/History.html
• https://ecl.common-lisp.dev/static/manual/What-is-ECL.html
• https://gitlab.com/api/v4/projects/embeddable-common-lisp%2Fecl/repository/tags?per_page=10