Automic VaultAutomic Vault

brew

使用 Homebrew, MacPorts 安装 x86_64-elf-gcc

查看 x86_64-elf-gcc 的安装路径、可执行文件、元数据以及面向 AI 代理工作流的安全说明。

安装

其他安装命令

macOS

Homebrew已验证 · 100%
brew install x86_64-elf-gcc

local Homebrew formula metadata

MacPorts已验证 · 94%
sudo port install x86_64-elf-gcc

MacPorts ports tree · cross/x86_64-elf-gcc/Portfile · 来源: api.github.com

概览

软件包摘要

GNU compiler collection for x86_64-elf

命令和别名

  • x86_64-elf-c++
  • x86_64-elf-cpp
  • x86_64-elf-g++
  • x86_64-elf-gcc
  • x86_64-elf-gcc-16.1.0
  • x86_64-elf-gcc-ar
  • x86_64-elf-gcc-nm
  • x86_64-elf-gcc-ranlib
  • x86_64-elf-gcov
  • x86_64-elf-gcov-dump
  • x86_64-elf-gcov-tool
  • x86_64-elf-lto-dump

历史

项目历史与用法

x86_64-elf-gcc is GCC built as a cross compiler for the `x86_64-elf` target. Its package role is not to be a separate compiler project, but to provide the GNU Compiler Collection configured for freestanding 64-bit x86 ELF output without assuming the host operating system's headers, C library, startup files, or ABI conventions.

That makes it a standard tool for operating-system kernels, bootloaders, freestanding runtimes, and bare-metal experiments. It usually works together with `x86_64-elf-binutils`, which supplies the matching target assembler, linker, and object-file tools.

项目历史

GCC began as the GNU C Compiler, written for the GNU operating system and first released in 1987. It later expanded into the GNU Compiler Collection, with official front ends for C, C++, Objective-C, Objective-C++, Fortran, Ada, Go, D, Modula-2, COBOL, Rust, Algol 68, and related runtime libraries documented by the GCC project.

The GCC governance and release story also matters to cross packages. GCC's 2.95 release in July 1999 was the first after the GCC/EGCS reunification, and the project has since been maintained by a global developer community under a steering committee. The modern GCC site emphasizes regular releases that work across native and cross targets.

采用历史

Cross compilation has been central to GCC's identity because GCC supports many processors and systems. The official GCC homepage explicitly says the project aims for releases that work on a variety of native and cross targets, while OSDev documentation explains why hobby OS and kernel developers build target-specific GCCs instead of relying on the host compiler.

For `x86_64-elf`, adoption is concentrated in OSDev and freestanding x86-64 work. The target prefix lets build systems call `x86_64-elf-gcc` and get code-generation defaults for x86-64 ELF rather than the host triple. OSDev guidance also notes that a target-specific compiler removes the need to pass host-overriding options such as `-m64` for every build.

使用方式

Typical users compile freestanding C or C++ with options such as `-ffreestanding`, link with a custom linker script, and provide their own runtime entry point instead of relying on a hosted C library. The compiler may also be used as the driver for assembly and linking so it selects the matching target Binutils tools.

In kernel work, x86-64 has hardware and ABI details that package users must understand beyond simply choosing this compiler. OSDev material commonly calls out issues such as separate 32-bit and 64-bit toolchains, bootloader expectations, and x86-64 red-zone behavior; the package gives the target compiler, but the build still has to define the freestanding environment correctly.

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

x86_64-elf-gcc is important because it packages the first serious bootstrap hurdle of hobby OS development. Instead of every user manually building a cross GCC, the package provides a stable prefixed compiler that can be dropped into Makefiles and tutorials.

It is also a clear example of how package names can describe configuration rather than upstream identity. The upstream is GCC; the meaningful package distinction is the target triple, which changes what the compiler assumes about object format, runtime, and operating-system services.

时间线

  • 1987-03-22: GCC 1.0 is first released as the GNU C Compiler.
  • 1999-04: The EGCS steering committee is appointed as the official GCC maintainer after the GCC/EGCS reunification process.
  • 1999-07-31: GCC 2.95 is released as the first GCC release after GCC/EGCS reunification.
  • 2000s: OSDev communities popularize target-prefixed GCC cross compilers such as `i686-elf-gcc` and later `x86_64-elf-gcc` for freestanding kernels.
  • 2026-04-30: GCC 16.1 is released, and the GCC homepage lists ongoing support for native and cross targets.

Related projects

  • GNU Binutils provides the assembler, linker, and object tools required by a matching `x86_64-elf` GCC toolchain.
  • GDB is commonly built as a target-aware debugger alongside cross GCC and Binutils.
  • Newlib and other small C libraries are used when a freestanding cross compiler grows into a hosted embedded or OS-specific toolchain.
  • LLVM/Clang can also target freestanding x86-64 ELF workflows, often with `lld` and LLVM binary tools.

安全态势

风险级别:绿色

narrow executable package without higher-risk signals.

风险分类器

绿色 风险 · 低 置信度 · appliance

原因

  • narrow executable package without higher-risk signals

信号

  • metadata:no-higher-risk-signals

安装行为

  • formula 元数据中未记录 Homebrew post-install 钩子。
  • Homebrew bottle 元数据适用于 6 个平台目标。
  • 安装时包含 5 个运行时依赖。

建议审查

在无人值守的代理使用前,请检查该工具是否读取明文凭据、写入远程状态、发布制品或调用插件。

可执行文件

已安装的可执行文件

命令类型暴露范围备注
x86_64-elf-c++cli全局可执行文件
x86_64-elf-cppcli全局可执行文件
x86_64-elf-g++cli全局可执行文件
x86_64-elf-gcccli全局可执行文件
x86_64-elf-gcc-16.1.0cli全局可执行文件
x86_64-elf-gcc-arcli全局可执行文件
x86_64-elf-gcc-nmcli全局可执行文件
x86_64-elf-gcc-ranlibcli全局可执行文件
x86_64-elf-gcovcli全局可执行文件
x86_64-elf-gcov-dumpcli全局可执行文件
x86_64-elf-gcov-toolcli全局可执行文件
x86_64-elf-lto-dumpcli全局可执行文件

新鲜度

版本和新鲜度

这些信号区分页生成时间、软件包管理器活动和上游发布比较。只有存在证据 URL 和可比较版本时,才会提示版本落后。

页面生成时间2026-07-10
管理器版本16.1.0
管理器更新时间2026-05-01
本地数据OK
上游not checked
检测到的最新版本未检测到

https://gcc.gnu.org

  • 信息Release/tag comparison is only available for GitHub repositories.https://gcc.gnu.orgnone 置信度

安装元数据

软件包元数据

软件包键brew:x86_64-elf-gcc
版本16.1.0
软件包管理器Homebrew
软件包管理器页面https://formulae.brew.sh/formula/x86_64-elf-gcc
主页https://gcc.gnu.org
仓库https://gcc.gnu.org/git/gcc.git
上游文档https://gcc.gnu.org/
许可证GPL-3.0-or-later WITH GCC-exception-3.1
源码归档https://ftpmirror.gnu.org/gnu/gcc/gcc-16.1.0/gcc-16.1.0.tar.xz
最后更新2026-05-01T04:23:32Z
Pulseupdated
依赖gmp, libmpc, mpfr, x86_64-elf-binutils, zstd
Bottle可用 (于 arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, sonoma, x86_64_linux)
Homebrew post-install未定义
服务未声明

注册表事实

源数据库详情

Source DatabaseHomebrew formula API
Taphomebrew/core
Full Namex86_64-elf-gcc
Version Scheme0
Revision0
Bottle Stable Root URLhttps://ghcr.io/v2/homebrew/core
Deprecatedno
Disabledno
Keg Onlyno
URL Keys
  • stable

源数据库匹配

其他软件包管理器记录

匹配项来自外部软件包管理器索引,并与本地 Automic Vault 软件包链接分开显示。

MacPorts95%

x86_64-elf-gcc

sudo port install x86_64-elf-gcc
  • normalized package name match
  • 匹配方式:X86 64 Elf Gcc
MacPorts ports tree · api.github.com · MacPorts ports tree: cross/x86_64-elf-gcc/Portfile from https://api.github.com/repos/macports/macports-ports/git/trees/master?recursive=1

来源线索

由仓库数据生成

此页面由 av-webscripts/generate-pkg-sqlite.py 生成的私有软件包 SQLite 工件提供。

使用的来源

  • Geiger risk classifier
  • Nucleus package database
  • av.db category and tag curation
  • cross-ecosystem install command graph
  • curated package history
  • external package-manager database matches
  • package relationship graph
  • package version freshness
  • package-page enrichment