Fix aarch64 build in Dockerfile-CI.alpine.Dockerfile

[mre]

Fixes #1745

[willnode]

I'm not sure that will working since alpine doesn't have glibc, it must be compiled under musl.

[mre]

Okay, I'm not an expert on this but the binary builds are here if you want to give it a go: https://github.com/lycheeverse/lychee/blob/master/.github/workflows/release-binary.yml

Maybe it's possible to create a PR for that new binary?

[willnode]

AFAIK arm-*-linux-* is 32-bit ARM variant and I don't know if any machine runs it anymore (except old android). There's aarch64-unknown-linux-musl for 64 bit musl.

That would be a breaking change I think

[mre]

Breaking change would be fine. The image is broken anyway at the moment. ;)

[mre]

@willnode , do you think the change is correct and fixes the problem? If not, I'd need some guidance here. Not an expert. 😉 If there's a better way, I'd appreciate a pull request or a list of change requests.

[willnode]

I'll test tonight

[eread]

I'll test tonight

@willnode Did you have any luck with your testing?

[eread]

@mre @willnode I don't think this will work because, this being a build for Alpine Linux, it must be musl based and not GNU based.

[mre]

You're right. If you like, you could create a separate pr to try and fix it.

[eread]

@mre I've raised: #1774.

[eread]

@mre I'm wondering with this one if the problem is the binary itself. If I'm not mistaken, this project uses https://github.com/cross-rs/cross for compilation, and uses a subset of https://github.com/cross-rs/cross?tab=readme-ov-file#supported-targets as compilation targets:

lychee/.github/workflows/release-binary.yml

Lines 43 to 49 in e743ea3

	target:
	- x86_64-unknown-linux-gnu
	- x86_64-unknown-linux-musl
	- arm-unknown-linux-gnueabihf
	- arm-unknown-linux-musleabi
	- arm-unknown-linux-musleabihf
	- aarch64-unknown-linux-gnu

I wonder if adding aarch64-unknown-linux-musl as a target would work well, and complement aarch64-unknown-linux-gnu that the project already has?

[eread]

@mre I'm wondering with this one if the problem is the binary itself. If I'm not mistaken, this project uses https://github.com/cross-rs/cross for compilation, and uses a subset of https://github.com/cross-rs/cross?tab=readme-ov-file#supported-targets as compilation targets:

lychee/.github/workflows/release-binary.yml

Lines 43 to 49 in e743ea3

	target:
	- x86_64-unknown-linux-gnu
	- x86_64-unknown-linux-musl
	- arm-unknown-linux-gnueabihf
	- arm-unknown-linux-musleabi
	- arm-unknown-linux-musleabihf
	- aarch64-unknown-linux-gnu

I wonder if adding aarch64-unknown-linux-musl as a target would work well, and complement aarch64-unknown-linux-gnu that the project already has?

I've raised: #1774 to that effect.

[mre]

Closing because it got superseded #1774.