mirror of
https://github.com/librespot-org/librespot.git
synced 2026-04-27 00:05:55 +03:00
[GH-ISSUE #96] Compilation error[E0460]: found possibly newer version of crate log which librespot depends on #87
Labels
No labels
A-Alsa
SpotifyAPI
Tokio 1.0
audio
bug
can't reproduce
compilation
dependencies
duplicate
enhancement
good first issue
help wanted
high priority
imported
imported
invalid
new api
pull-request
question
reverse engineering
wiki
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/librespot#87
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @sashahilton00 on GitHub (Jan 29, 2018).
Original GitHub issue: https://github.com/librespot-org/librespot/issues/96
Friday Nov 03, 2017 at 16:53 GMT
Originally opened as https://github.com/plietar/librespot/issues/264
After I cloned and installed librespot on my RPi3 with cargo build, I tried to run the play.rs example with the following command:
pi@raspberrypi:~/librespot/target/release $ rustc play.rs --extern librespot=liblibrespot.rlib && ./excecutableThis results in the following error:
error[E0460]: found possibly newer version of crate 'log' which 'librespot' depends on
--> play.rs:1:1
|
1 | extern crate librespot;
| ^^^^^^^^^^^^^^^^^^^^^^^
|
= note: perhaps that crate needs to be recompiled?
= note: crate 'log' path #1: /home/pi/.rustup/toolchains/stable-armv7-unknown-linux-gnueabihf/lib/rustlib/armv7-unknown-linux-gnueabihf/lib/liblog-4df2ac3c730deffe.rlib
= note: crate 'librespot' path #1: /home/pi/librespot/target/release/liblibrespot.rlib
error: aborting due to previous error
I don't really know what the problem is about. According to Cargo.toml, librespot has a dependency to log = "0.3.5", and the newest version is of log = "0.3.8".
Do I need to update this specific crate?
@ComlOnline commented on GitHub (Jan 29, 2018):
Hey @chriszirkel, Is there any reason you didn't run the binary directly?
@sashahilton00 commented on GitHub (Feb 7, 2018):
Can we close this? I can't reproduce in either release or debug when compiling for RPi...
@plietar commented on GitHub (Feb 7, 2018):
You should be building
play.rswith cargo, not rustc.@sashahilton00 commented on GitHub (Feb 7, 2018):
This feels like a non-issue, so closing for now. Feel free to reopen if you think I've closed this prematurely.