-
Notifications
You must be signed in to change notification settings - Fork 20
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
CC issue #114
Comments
Could you please try compiling without using docker container (with a stable compiler if possible)? Trunk only supports download toolchain with aarch64-apple-darwin and not aarch64-unknown-linux-gnu. It is possible that some toolchain binary is outdated (especially wasm-bindgen) and if trunk does not support automatically downloading toolchain on that target it will not be able to fix it. |
@futursolo I require nightly due to other deps but i am able to compile directly on OSX just fine. Do you think this maybe more of a trunk related issue? Thanks for your help on this BTW |
I would recommend to develop natively with an Apple Silicon Mac until all toolchains have pre-built Linux ARM binaries, which may be a couple years ahead (or try Rosetta x86_64 containers). It could also be because of you are using nightly complier. It's not uncommon that nightly compiler encounter issues. You should run |
So my image installs rust which i have been destroying every now and again so i dont think thats the issue. This was all working so the binaries must have been in place, i just cant work out why this was working just fine in my setup and now i get this issue :( Just to add to this. Its 100% caused by this dep. When removed from cargo.toml my project compiles just fine. |
The latest nightly version could also be bad. Rebuilding may not help at the moment. Try to wait a couple days and try again. In addition, the wasm-bindgen version and wasm-bibdgen-cli must match exactly. If you have modified any dependencies, you need to check the wasm-bindgen version. Similarly, if your image always download the latest version when it is built, you may need to downgrade it. This requirement could be hard to maintain if trunk cannot do it for you. So I would recommend try to avoid Linux ARM64 until Linux arm have proper toolchain support. |
Regardless, I do not think this is related to stylist and can be mitigated by avoiding using a docker container workflow. So I am closing this issue. |
@futursolo If install a targeted version of rust nightly from a few months back everything works as expected (not sure exactly when it broke) so it is the current version of nightly breaking this repo. More of a FYI at this point. Thanks |
Hi,
Im not sure if this is related to the repo or my setup but my project was working then just stopped. I get the following error related to the stylist repo.
Im really not sure how or what is causing this, has anyone seen this before?
Running on M1 Mac within linux docker container.
The text was updated successfully, but these errors were encountered: