Skip to content
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

Does not currently build on Rust 1.30 (currently beta) #18

Closed
icefoxen opened this issue Sep 23, 2018 · 1 comment
Closed

Does not currently build on Rust 1.30 (currently beta) #18

icefoxen opened this issue Sep 23, 2018 · 1 comment

Comments

@icefoxen
Copy link
Contributor

rustc issue here: rust-lang/rust#54471

Error message:

   Compiling ipfs-api v0.5.0-alpha1 (/home/icefox/tmp/rust-ipfs-api/ipfs-api)
error[E0432]: unresolved imports `response::BitswapStatResponse`, `response::RepoStatResponse`
 --> ipfs-api/src/response/stats.rs:9:16
  |                                                                                                   9 | use response::{BitswapStatResponse, RepoStatResponse};
  |                ^^^^^^^^^^^^^^^^^^^  ^^^^^^^^^^^^^^^^ no `RepoStatResponse` in `response`. Did you
mean to use `ResolveResponse`?
  |                |
  |                no `BitswapStatResponse` in `response`. Did you mean to use `BitswapUnwantResponse`
?

error: cannot determine resolution for the attribute macro `serde`
  --> ipfs-api/src/response/bitswap.rs:12:3
   |
12 | #[serde(rename_all = "PascalCase")]
   |   ^^^^^
   |
   = note: import resolution is stuck, try simplifying macro imports

error: cannot determine resolution for the attribute macro `serde`
  --> ipfs-api/src/response/bitswap.rs:24:3
   |
24 | #[serde(rename_all = "PascalCase")]
   |   ^^^^^
   |
   = note: import resolution is stuck, try simplifying macro imports
 ...

...plus a lot more serde stuff. Full build log available here: https://crater-reports.s3.amazonaws.com/beta-1.30-1/beta-2018-09-19/reg/ipfs-api-0.5.0-alpha2/log.txt

@ferristseng
Copy link
Owner

Tested it recently, and this should be fixed I think with the latest nightly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants