Improve cross ci

The cross-compiling toolchain is outdated, and musl.cc is no longer maintained😵‍💫. Toward the end of the year, when the Linux ARM CI instance reaches GA, we might consider removing cross-compiling CI. Alternatively, we could use the aarch64-linux-gnu toolchain that comes with Debian/Ubuntu, or we could maintain our own cutting-edge musl cross-compiling toolchain.

Originally posted by @c8ef in #5090 (comment)

The good news is that Linux & Windows Arm CI is now generally available. The downside is that it is currently only accessible to team and enterprise customers. I'm not sure if we have access to these machines.🤓

windows arm ci.

xmake-repo/.github/workflows/windows.yml

Line 15 in c02fc3a

arch: [x64, x86, arm64]

No, I mean a native ARM Windows machine, not cross-compiling on an x86 Windows server.

See also: https://github.blog/changelog/2024-09-03-github-actions-arm64-linux-and-windows-runners-are-now-generally-available

https://github.blog/news-insights/product-news/arm64-on-github-actions-powering-faster-more-efficient-build-systems/#get-started-using-arm-hosted-runners-today

We expect to begin offering Arm runners for open source projects by the end of the year

https://github.com/xmake-io/xmake-repo/actions/runs/10812519041/job/29994350373?pr=5059
Any idea?

Not sure what happened.🥶The official CI for libffi does not cover the musl toolchain. Perhaps consider switching to the GNU toolchain and trying again?

#5230

The linker behavior of this toolchain is very strange.

https://github.com/xmake-io/xmake-repo/actions/runs/10812519041/job/29994350373?pr=5059 Any idea?

See xmake-io/xmake#5639
Test package: #5337