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
As of d4d4024, compiling salmagundi and directly running the binary results in this error for me:
target/release/salmagundi: error while loading shared libraries: libproc_macro-96fdba3b331ee226.so: cannot open shared object file: No such file or directory
Note this happens for both release and debug builds (of course with the appropriate directory reported). Using cargo run, it works for both builds.
Not sure what else matters here, using rust nightly as of de3d640f5, running on gentoo linux, I simply cloned the repo and built. If you need to know anything more, let me know :)
The text was updated successfully, but these errors were encountered:
This is very definitely a problem with the fact that salmagundi uses syn directly but also uses structopt, which relies on syn internally. This means that cargo will attempt to use only one version of syn if possible, which in turn means that that version of syn gets linked against the compiler-bundled proc-macro crate as a shared library. Then, even though that dependency is no longer necessary at run time, the linker includes it for salmagundi anyway, which fails at load time if the binary is run without instructions on how to find the shared library again (which cargo run somehow provides in the environment).
As of d4d4024, compiling salmagundi and directly running the binary results in this error for me:
Note this happens for both release and debug builds (of course with the appropriate directory reported). Using
cargo run
, it works for both builds.Not sure what else matters here, using rust nightly as of de3d640f5, running on gentoo linux, I simply cloned the repo and built. If you need to know anything more, let me know :)
The text was updated successfully, but these errors were encountered: