Skip to content

Commit 93cf331

Browse files
committed
[ci] install liburing for the site build
The v1.0.0-RC6 site deploy failed linking the browser bundle: /usr/bin/ld: cannot find -luring: No such file or directory [error] (kyo-netJS / ffiCompile) C compilation failed (exit=1) The bundle reaches kyo-net through kyo-http, so linking it compiles kyo-net's io_uring shim, which statically links -luring. deploy-site.yml does not use .github/actions/setup and so never installed it. Before RC6 the site build pulled in no native shim and the gap did not show. Installs liburing-dev inline, the way readme.yml already does for the same reason. BoringSSL is not staged: build.sbt falls back to the c-boringssl-stub shim, which is all a docs render needs, and readme.yml sets the same precedent.
1 parent fe26b57 commit 93cf331

1 file changed

Lines changed: 7 additions & 0 deletions

File tree

.github/workflows/deploy-site.yml

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -40,6 +40,13 @@ jobs:
4040
with:
4141
jvm: corretto:25
4242
apps: sbt
43+
# liburing (build-time only): the site bundle reaches kyo-net through kyo-http, and linking it
44+
# compiles kyo-net's io_uring FFI shim (kyo_uring.c), which statically links -luring. This
45+
# workflow does not use .github/actions/setup, so install it here too, as readme.yml does.
46+
# BoringSSL is not staged: build.sbt falls back to the c-boringssl-stub shim, which is all a
47+
# docs render needs.
48+
- name: Install liburing (Linux)
49+
run: bash scripts/apt-install.sh liburing-dev
4350
- name: Link the browser bundle (fullLinkJS)
4451
run: sbt 'kyo-website-bundleJS/Compile/fullLinkJS'
4552
- name: Render and assemble the site from the current repo

0 commit comments

Comments
 (0)