mirror of
https://github.com/librespot-org/librespot.git
synced 2026-04-27 08:15:50 +03:00
[GH-ISSUE #401] docker-build-pi-armv6hf.sh fails with dpkg-deb error #258
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#258
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 @pejobo on GitHub (Nov 17, 2019).
Original GitHub issue: https://github.com/librespot-org/librespot/issues/401
I tried the described cross-build method for raspberry and it fails for me with
dpkg-deb: error: 'libasound2_1.0.25-4_armhf.deb' is not a debian format archiveComplete log:
I then used the described generic armfh method, which worked fine and is now running without flaws on my raspberry.
@praul commented on GitHub (Dec 7, 2019):
You could change the alsa version in the script to, for example
1.1.3-5
and try again.
I think, you have to rebuild the docker image, though
@john-a-harris commented on GitHub (Dec 13, 2019):
I've tried this (and rebuilt the docker image). I am now getting a linking error:
I can add more of the error output if it's useful. What might I have done wrong here?
@praul commented on GitHub (Dec 14, 2019):
I could not successfully build either.
Also, I cannot get armhf-build without script to work, see: https://github.com/librespot-org/librespot/issues/408
I have switched to librespot-java now
@pejobo commented on GitHub (Dec 14, 2019):
@praul No need to switch to the java version, the "generic armfh" build is working and the produced binary is running stable on my raspberry.
@ashthespy commented on GitHub (May 11, 2020):
@pejobo Marking this as closed, feel free to jump back in if you are still having issues..
@rlopzc commented on GitHub (Sep 4, 2020):
Hello. I'm having issues, I already changed the ALSA_VER to the latest one and also the recommended in this post:
1.1.3-5. Do you know if this cross compilation is still working?I get the error:
@ashthespy commented on GitHub (Sep 4, 2020):
You might have to match the right
ALSA_VERfor the targetGLIBCversion (the version instretchmaybe?)I can look up my build scripts later this evening..
@rlopzc commented on GitHub (Sep 4, 2020):
@ashthespy do you mean change
stretchtobuster?Edit
I changed it
FROM debian:busterand got:@ashthespy commented on GitHub (Sep 5, 2020):
@romariolopezc No I meant you need to find the right version of the ALSA lib that matches the cross-compilers GLIBC version..
You might have to poke around the
sysrootand check -- something likeLooking through my stuff, I see I did try some other things (
github.com/ashthespy/librespot@64f6644224 (diff-43bcfbb35e))Big disclaimer - I may be completely wrong though, but this is what I vaguely recall while trying to get things working for armv6 (pi) target for a while, before ultimately going down a different path with a different toolchain with
armelarchitecture instead.@felixstorm commented on GitHub (Aug 12, 2022):
I know this is very old stuff and just in case anybody will be searching for it: I also had the problem that
contrib/docker-build-pi-armv6hf.shfailed for me and was able to fix it.The new script works for both the old and the new api as of now and can be found here: https://github.com/librespot-org/librespot/pull/1044