Downgrade musl to 1.1.24

[malbarbo]

Fixes #478.

[brainstorm]

At this point, I think it's best to NOT downgrade MUSL on the cross images. A few months have passed with MUSL 1.2.0 merged in and:

1. It allows OpenSSL to be cross-compiled successfully.
2. I'm not aware of any other specific breakage from apps/users?

@malbarbo Which packages have you seen breaking "in the wild" due to this?

[malbarbo]

The problem can happen with any project that interacts with C. See https://github.com/ericonr/rust-time64.

[reitermarkus]

Is this still relevant? I'm guessing it is since the libc issue is still open, so please rebase this.

[Alexhuszagh]

It is, I just tested it with a Dockerfile with OpenSSL. Sample code to reproduce is (based off of sheldon-cross).

Dockerfile

FROM ghcr.io/cross-rs/armv7-unknown-linux-musleabihf:main

COPY install_openssl.sh /
RUN apt-get update && apt-get install wget
RUN wget https://github.com/rossmacarthur/sheldon-cross/blob/trunk/docker/install_openssl.sh
RUN bash /install_openssl.sh linux-armv4 arm-linux-musleabihf-

ENV OPENSSL_DIR=/openssl \
    OPENSSL_STATIC=1 \
    OPENSSL_INCLUDE_DIR=/openssl/include \
    OPENSSL_LIB_DIR=/openssl/lib

Then, set the appropriate target in Cross.toml using the local tag, and try to build the image:

git clone https://github.com/rossmacarthur/sheldon
cd sheldon
cargo build --target armv7-unknown-linux-musleabihf

Which produces a lot of errors related to 64-bit time (undefined references to __time64, __fstat_time64, __clock_gettime64, __stat_time64, and more). Could we get a rebase or I could make the modifications and merge.

I'm using the latest stable Rust version (1.61.0) and cross installed from git (the most recent commit as of the time this comment was posted).

[Alexhuszagh]

bors try --target -musl

[bors]

try

Build succeeded:

• conclusion

[otavio]

bors r+

[bors]

Build succeeded:

• conclusion