Skip to content

Commit bd6516f

Browse files
sunnylqmclaude
andcommitted
ci: raise glibc symbol ceiling to 2.34
The LZMA multithreading support links pthread symbols, which carry GLIBC_2.34 versions when built on glibc >= 2.34 runners; published v2.3.0 prebuilds already require 2.34 and it remains compatible with Ubuntu 22.04, Debian 12, and RHEL 9. The 2.33 ceiling predated that. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
1 parent aab20f7 commit bd6516f

2 files changed

Lines changed: 7 additions & 3 deletions

File tree

.github/workflows/ci.yml

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -59,11 +59,12 @@ jobs:
5959
- run: node test/test.js
6060
- run: bun ./test/test.js
6161
# 与 publish 一致:固定 Linux prebuild 的 glibc 符号版本上限
62+
# (2.34 基线依据见 publish.yml,兼容 Ubuntu 22.04/Debian 12/RHEL 9)
6263
- name: Check glibc symbol ceiling
6364
if: runner.os == 'Linux'
6465
run: |
6566
set -euo pipefail
66-
ceiling="2.33"
67+
ceiling="2.34"
6768
max=$(objdump -T prebuilds/*/*.node | grep -o 'GLIBC_[0-9.]*' | sed 's/GLIBC_//' | sort -Vu | tail -1)
6869
test -n "$max"
6970
echo "max required glibc: $max (ceiling: $ceiling)"

.github/workflows/publish.yml

Lines changed: 5 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -44,12 +44,15 @@ jobs:
4444
- run: node test/test.js
4545
- run: bun ./test/test.js
4646
# 曾发生过 Ubuntu 24.04 构建把最低要求抬到 GLIBC_2.38、导致
47-
# Ubuntu 22.04/Debian 12 无法加载的回归;此处固定符号版本上限
47+
# Ubuntu 22.04/Debian 12 无法加载的回归;此处固定符号版本上限。
48+
# 2.34 是现实基线:LZMA 多线程链接 pthread,在 glibc>=2.34 的
49+
# 构建机上这些符号必然带 GLIBC_2.34 版本(v2.3.0 起即如此),
50+
# 兼容 Ubuntu 22.04 / Debian 12 / RHEL 9。
4851
- name: Check glibc symbol ceiling
4952
if: runner.os == 'Linux'
5053
run: |
5154
set -euo pipefail
52-
ceiling="2.33"
55+
ceiling="2.34"
5356
max=$(objdump -T prebuilds/*/*.node | grep -o 'GLIBC_[0-9.]*' | sed 's/GLIBC_//' | sort -Vu | tail -1)
5457
test -n "$max"
5558
echo "max required glibc: $max (ceiling: $ceiling)"

0 commit comments

Comments
 (0)