Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix unresolved symbol issue when using latest Rust nightly #87

Merged
merged 1 commit into from
Apr 22, 2024

Conversation

dicej
Copy link
Collaborator

@dicej dicej commented Apr 22, 2024

As of this writing, recent Rust nightly builds include a version of the libc crate that expects wasi-libc to define the following global variables, but wasi-libc defines them as preprocessor constants which aren't visible at link time, so we need to define them somewhere. Ideally, we should fix this upstream, but for now we work around it.

This commit also addresses an unused field warning.

Fixes #86

As of this writing, recent Rust `nightly` builds include a version of the `libc`
crate that expects `wasi-libc` to define the following global variables, but
`wasi-libc` defines them as preprocessor constants which aren't visible at link
time, so we need to define them somewhere.  Ideally, we should fix this
upstream, but for now we work around it.

This commit also addresses an unused field warning.

Fixes #86

Signed-off-by: Joel Dice <joel.dice@fermyon.com>
@dicej dicej merged commit 013d51b into main Apr 22, 2024
1 check passed
@dicej dicej deleted the nightly-fix branch April 22, 2024 15:59
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.

Unresolved symbols when building from source
1 participant