You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
wasm-bindgen has been working great for me so far - thanks!
I'm in the middle of publishing the first version of a crate and got some build errors during cargo publish (that I didn't get during weeks of cargo build) so updated to the latest nightly tried again.
Now for build / publish attempts I get the following error after running cargo build -p virtual-dom-rs in my cargo workspace.
LLVM ERROR: Global variable '_ZN14virtual_dom_rs7webapis41__WASM_BINDGEN_GENERATED_fa4110c820b3561817h4afda009a1e7c776E' has an invalid section specifier '__wasm_bindgen_unstable': mach-o section specifier requires a segment whose length is between 1 and 16 characters.
error: Could not compile `virtual-dom-rs`.
Anywho.. the bit that sticks out is:
has an invalid section specifier '__wasm_bindgen_unstable': mach-o section specifier requires a segment whose length is between 1 and 16 characters
The string __wasm_bindgen_unstable is 23 characters long. Is it possible that we need to shorten that in order for builds to work on macOS? Or is there something else going on here?
Alright so I suspect that this is a mac issue, but that's surprising since I figured at least a few other people are using wasm-bindgen with macOS? Also not sure why this started happening after I attempted to cargo publish.
Anyways.. I changed the 2 instances of __wasm_bindgen_unstable to __wasm_bindngen,unstable and my code built.
Note that the comma was added because without it I was getting a new error:
LLVM ERROR: Global variable '_ZN13percy_webapis41__WASM_BINDGEN_GENERATED_f9fd3881c38380a217hefaad0f29ad9dcd8E' has an invalid section specifier '__wb_unstable': mach-o section specifier requires a segment and section separated by a comma.
This issue suggests that we might need different specifiers for different targets.. but I'm not sure.. so I'm going to PR a fix and see if CI passes then go from there...
chinedufn
added a commit
to chinedufn/wasm-bindgen
that referenced
this issue
Jul 25, 2018
Hey!
wasm-bindgen has been working great for me so far - thanks!
I'm in the middle of publishing the first version of a crate and got some build errors during
cargo publish
(that I didn't get during weeks ofcargo build
) so updated to the latest nightly tried again.Now for build / publish attempts I get the following error after running
cargo build -p virtual-dom-rs
in my cargo workspace.Anywho.. the bit that sticks out is:
has an invalid section specifier '__wasm_bindgen_unstable': mach-o section specifier requires a segment whose length is between 1 and 16 characters
The string
__wasm_bindgen_unstable
is 23 characters long. Is it possible that we need to shorten that in order for builds to work on macOS? Or is there something else going on here?macOS High Sierra Version 10.13.3
wasm-bindgen = "0.2.13"
Here's some source code, in case anything sticks out - https://gist.github.com/chinedufn/17b2306b5366ea78157b9f2bd599202f
Feel free to let me know if I can provide any other info!
The text was updated successfully, but these errors were encountered: