Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

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

rustler errors on OTP26 #544

Closed
CharlesOkwuagwu opened this issue Jun 7, 2023 · 1 comment
Closed

rustler errors on OTP26 #544

CharlesOkwuagwu opened this issue Jun 7, 2023 · 1 comment

Comments

@CharlesOkwuagwu
Copy link

Please I get this error on OTP26 with rustler 0.28
It's not clear how to apply the upgrade from here
https://github.com/rusterlium/rustler/blob/master/UPGRADE.md#028---029

error: failed to run custom build command for `rustler_sys v2.2.0`

Caused by:
  process didn't exit successfully: `c:/Projects/xler/_build/dev/lib/xler/native/xler_native\release\build\rustler_sys-55353dc99dae555c\build-script-build` (exit code: 101)
  --- stderr
  thread 'main' panicked at 'The NIF version given from RUSTLER_NIF_VERSION is not supported: 2.17', C:\Users\Charles Okwuagwu\.cargo\registry\src\index.crates.io-6f17d22bba15001f\rustler_sys-2.2.0\build.rs:925:9
  note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
warning: build failed, waiting for other jobs to finish...

== Compilation error in file lib/xler/native.ex ==
** (RuntimeError) Rust NIF compile error (rustc exit code 101)
    (rustler 0.28.0) lib/rustler/compiler.ex:41: Rustler.Compiler.compile_crate/2
    lib/xler/native.ex:2: (module)

@filmor
Copy link
Member

filmor commented Jun 7, 2023

For now, there is nothing to do. Just update to 0.29. This problem (having to update for a new NIF version) is gone with 0.29 as well. You'll only have to update if you are actually using new NIF features.

@filmor filmor closed this as completed Jun 7, 2023
@rusterlium rusterlium locked and limited conversation to collaborators Jun 7, 2023
@filmor filmor converted this issue into discussion #545 Jun 7, 2023

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants