Skip to content

fix: allow undefined symbols during build time#1

Merged
wemeetagain merged 2 commits intoChainSafe:mainfrom
spiral-ladder:bing/fix-undefined-symbols
Dec 12, 2025
Merged

fix: allow undefined symbols during build time#1
wemeetagain merged 2 commits intoChainSafe:mainfrom
spiral-ladder:bing/fix-undefined-symbols

Conversation

@spiral-ladder
Copy link
Copy Markdown
Contributor

Previously, building would fail because zig expects the napi symbols during link time when they actually only exist during runtime. This PR relaxes this with the allow-shlib-undefined option (see: ld docs).

Previously, building would fail because zig expects the napi symbols
during link time when they actually only exist during runtime. This
PR relaxes this with the `allow-shlib-undefined` option (see: [`ld` docs](https://www.man7.org/linux/man-pages/man1/ld.1.html)).
Comment thread build.zig
.name = "napi",
.root_module = module_napi,
.filters = &[_][]const u8{},
.filters = b.option([][]const u8, "napi.filters", "napi test filters") orelse &[_][]const u8{},
Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this change was made from using a newer version of zbuild (same for below)

Comment thread package.json Outdated
@spiral-ladder spiral-ladder force-pushed the bing/fix-undefined-symbols branch from 0162a91 to a6cac0e Compare December 12, 2025 01:13
@wemeetagain wemeetagain merged commit 085c03b into ChainSafe:main Dec 12, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants