librespot-org
update cross-compile oldstable debian to stable(trixie)
This is mainly so we can cross-compile to the stable Debian Trixie changing from old-stable (Bookworm)
It seems using native-tls was broken in the previous build container. Since debian trixie provides rustup in the repositories I switch to running that which fixes the issue of failing to build using native-tls so it fixes this bug
I tested building towards all the targets in the Dockerfile and compilation was successful and actually tested the binary itself on aarch64-unknown-linux-gnu, since that's what I'm running
Hi @tomodachi
I have built the librespot binary for a Raspberry Pi 3 (aarch64 architecture) using your branch. I still have bookworm on this Raspberry Pi, and the compiled binary fails with the following error:
./librespot_aarch64_trixie_071_dev: /lib/aarch64-linux-gnu/libc.so.6: version `GLIBC_2.39' not found (required by ./librespot_aarch64_trixie_071_dev)
On the other hand, binaries built using bookworm in the Docker image still run fine on a machine with Debian trixie installed - at least on a PC. I have just tested it on a fresh PC virtual machine. I plan to verify if it is the same on the Raspberry Pi.
Have you encountered problems with running binaries compiled using bookworm on a machine running trixie?
In my opinion it is better in general to stick to (reasonably) older versions in the development environment(s), because generated binaries usually run fine in newer versions of the target environments. The opposite is frequently not true. :disappointed:
Of course at some point keeping the old version just does not make sense - compatibility, security, third-party dependencies, etc. But given that trixie was released a few months ago, I am not sure if this point has been reached already.
I plan to verify if it is the same on the Raspberry Pi.
I have just checked on the Raspberry Pi 3 with trixie - librespot aarch64 binary generated using bookworm based Docker image works fine on trixie.
