-
-
Notifications
You must be signed in to change notification settings - Fork 214
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
When using Askama at revision 36cbfd4bad8c3f534c8cb13f9ddbc463e1c44ef5, binaries produced by Rust nightly-2018-04-07 dynamically link libstd and libproc_macro which cannot be found #73
Comments
I did a git bisect.
The result is:
|
I then manually checked that this result was correct because my bisection test was a bit simplified.
Yes, the identified commit has the issue with dynamic linking of libstd and libproc_macro (as well as additionally libtest but that does not affect the validity of the result). So something in b787bb4 makes it so that this issue occurs. |
Hey, sorry you're having so much trouble! When is the last time you've run Otherwise, you should probably report this in the syn issue tracker, as this issue doesn't appear to have anything to do with Askama in particular. Please cc me so I can support the investigation and keep track of any changes we have to make here. |
I've run |
I will write a bug report for syn then :) |
Until the issue in syn has been found and fixed I think this issue should be kept open since it affects Askama even though it is not within Askama itself, don't you agree? |
Yup, I explicitly left it open! |
I opened #77 with a fix. |
Thank you both :) |
I originally misattributed this issue first as cross-rs/cross#193 and then as #72 but I have now found conclusively that simply using Askama at revision 36cbfd4 with Rust nightly-2018-04-07 causes the following problem: The produced binary gets dynamically linked to libstd and libproc_macro which cannot be found, resulting in it being possible to run the binary with
cargo run
but not by direct execution of./target/debug/hello_askama
(hello_askama is what I named the minimal example that is made based on the Askama README) as in rust-lang/cargo#4651.I used a
Cargo.toml
that looks like this:build.rs
like in Askama README:templates/hello.htm
like in Askama README:src/main.rs
like in Askama README:And like I said, I was using Rust nightly-2018-04-07.
The text was updated successfully, but these errors were encountered: