Closed palnabarun closed 6 years ago
This was cross-posted to Stack Overflow.
Thanks @shepmaster for cross-referencing the posts.
Can you run cargo update
(to try and get the latest versions of the
dependencies) and see if this fixes the build?
Nabarun Pal notifications@github.com schrieb am Sa. 20. Jan. 2018 um 16:22:
Thanks @shepmaster https://github.com/shepmaster for cross-referencing the posts.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/killercup/trpl-ebook/issues/49#issuecomment-359178819, or mute the thread https://github.com/notifications/unsubscribe-auth/AABOX9kfDgOnFgHmX4t9dRd957p17vvBks5tMgS5gaJpZM4Rld9E .
Cross-posting my answer:
rustc-serialize 0.3.19 was released on April 4, 2016. It includes the syntax:
fn read_enum_struct_variant_field<T, F>(
&mut self,
&f_name: &str, // This is no longer allowed
f_idx: usize,
f: F,
) -> Result<T, Self::Error>;
This syntax was erroneously allowed until Oct 21, 2016 (Rust 1.14.0) when it was turned into a warning. On Nov 4, 2017 (Rust 1.23.0), this became an error.
The solution is to update the version of rustc-serialize.
@killercup the real fix would be to move away from rustc-serialize, but I'm guessing you know that ;-).
Well, it worked but cropped up another issue which according to me is a different thread altogether
Thanks @shepmaster for the help.
the real fix would be to move away from rustc-serialize, but I'm guessing you know that ;-).
@shepmaster the real fix would be to move this functionality into mdBook, but I'm guessing you know that ;-).
Seems like this issue should remain open until the master branch has been updated?
Indeed!
@palnabarun can you open a PR that updates the Cargo.lock file so the project compiles again?
Sure. @killercup
I am new to rust and I wanted to generate the epub format ebook for my kindle.
I downloaded the project to rebuild the book the second edition draft. When I do
cargo run --release
, I encounter the following error:I tried to search and debug the error but couldn't do so owing to my lack of knowledge of rust at the moment. Did anyone else encounter this error?