Jörg Krause

I am using [Buildroot](https://buildroot.org) to build a musl based toolchain. You can copy the output of the toolchain build to "/usr/local/bin" or create some symlinks. For reference have a look...

I am using symlinks in `/usr/local/bin` to the Buildroot output directory: ``` joerg ) ls -l /usr/local/bin/ total 17708 arm-linux-ar -> /home/joerg/buildroot/output/host/usr/bin/arm-linux-ar* arm-linux-as -> /home/joerg/buildroot/output/host/usr/bin/arm-linux-as* arm-linux-g++ -> /home/joerg/buildroot/output/host/usr/bin/arm-linux-g++.br_real* arm-linux-gcc ->...

Rust is porting compiler-rt into Rust and therefore has changed the location of compiler-rt. Commit 81b4605b23108e107c914ee65184a3223364e9e0 fixes the issue. The standard library is build now, but I still get linking...

You're building with the host linker. Did you run `export CC=...`? The exports have to be called each time the terminal is opened.

I've pushed another commit cda40d5ccb1486883b68d377795e1e3d060de2db which enables the jemalloc feature. This way, I can build the following hello crate: ``` Rust #![feature(alloc_jemalloc)] extern crate alloc_jemalloc; fn main() { println!("Hello, world!");...

This is the same linking error I get. You could try adding the feature macro from the hello example above to the main file of librespot.

I removed the `lib-allocation-crate` and `exe-allocation-crate` entries from the config json files. hello builds now without the linking errors.

Because I am running a musl libc linux system. Therefore, I patch liblibc: https://github.com/joerg-krause/rust-cross-libs/blob/master/patch/liblibc/0001-liblibc-do-not-link-libc-statically-for-ARM-musl.patch I haven't tried to build a statically linked executable, yet.

This has nothing to do with Buildroot. Buildroot is used to build the musl-based toolchain. The problem is to tell the Rust build system to link statically. In fact, linking...

@jr01 Good catch, thanks! Also, thanks for sharing your setup for the Synology. I will later add it to the README.