mirror of
https://github.com/librespot-org/librespot.git
synced 2026-04-27 00:05:55 +03:00
[GH-ISSUE #557] undefined reference to `llvm.x86.addcarry.64' on debian buster #355
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#355
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 @christf on GitHub (Dec 31, 2020).
Original GitHub issue: https://github.com/librespot-org/librespot/issues/557
compiling version
0adb8516a6on buster fails withThe error message is:
On https://github.com/rust-lang/rust/issues/47493 I found that enabling lto might fix the problem so I tried that - the output is the same though. What could I try next?
@ashthespy commented on GitHub (Dec 31, 2020):
Why are you building directly with
rustc?PS: Dupe of https://github.com/librespot-org/librespot/issues/555
@christf commented on GitHub (Jan 2, 2021):
I am not directly building with rustc but with cargo instead. As suggested in #555 I supplied --locked but that did not change the behavior:
@ashthespy commented on GitHub (Jan 2, 2021):
Are you sure this is on a fresh checkout?
@christf commented on GitHub (Jan 7, 2021):
Edit clarifying the language:
this was attempted to be built with
414383db18and06f5aa9c90. Both yield the same result as described above@ashthespy commented on GitHub (Jan 7, 2021):
Sorry, I don't follow - are you saying with a fresh checkout and
--locked,github.com/librespot-org/librespot@414383db18build fine, butgithub.com/librespot-org/librespot@06f5aa9c90doesn't?If so, then probably in all the version bumping b/w the commits, some
Cargo.lockgremlins crept it..@christf commented on GitHub (Jan 7, 2021):
the error message appears no matter whether --locked is specified or not. So the project does not build.
@sashahilton00 commented on GitHub (Jan 19, 2021):
This is indeed a dupe of #555, please move discussion there.