Monius

Yes, I figure out the jemalloc for musl target with, ```toml //Cargo.toml [target.'cfg(all(target_env = "musl", target_pointer_width = "64"))'.dependencies.jemallocator] version = "0.5" ``` ```rs //main.rs #[cfg(all(target_env = "musl", target_pointer_width = "64"))]...

Yes, it works for ```yml - target: x86_64-unknown-linux-gnu platform: ubuntu-latest - target: aarch64-unknown-linux-gnu platform: ubuntu-latest - target: powerpc64le-unknown-linux-gnu platform: ubuntu-latest - target: s390x-unknown-linux-gnu platform: ubuntu-latest - target: riscv64gc-unknown-linux-gnu platform: ubuntu-latest...

still returns: ```sh Installed package `cross v0.2.5` (executables `cross`, `cross-util`) + cross build --release --bin sample --target powerpc64le-unknown-linux-musl [cross] warning: `cross` does not provide a Docker image for target powerpc64le-unknown-linux-musl,...

And even `mipsel-unknown-linux-gnu` not work, ```yml - target: mipsel-unknown-linux-gnu platform: ubuntu-latest ``` reported that, ```sh Status: Downloaded newer image for ghcr.io/cross-rs/mipsel-unknown-linux-gnu:0.2.5 Compiling proc-macro2 v1.0.93 Compiling unicode-ident v1.0.16 Compiling cfg-if v1.0.0...

I see, looks like they dont support the allocator, ```sh warning: [email protected]+5.3.0-patched: "`background_threads_runtime_support` not supported for `riscv64gc-unknown-linux-musl`" error: failed to run custom build command for `jemalloc-sys v0.5.4+5.3.0-patched` Caused by: process...

And for > > reported that, > > ``` > > Status: Downloaded newer image for ghcr.io/cross-rs/mipsel-unknown-linux-gnu:0.2.5 > > ``` > > That issue is the same issue as the...

>This issue seems to be due to the way jemalloc guess the target. I believe we can adjust setup-cross-toolchain-action to avoid this issue. How to adjust the `setup-cross-toolchain-action` to fix...

Also for s390x, ```yml - target: s390x-unknown-linux-musl platform: ubuntu-latest ``` error reported, ```sh error: toolchain 'nightly-x86_64-unknown-linux-gnu' does not support target 's390x-unknown-linux-musl' note: you can see a list of supported targets...

>riscv64gc-unknown-linux-musl jemalloc configure script issue should be addressed in the latest setup-cross-toolchain-action@v1 Same issue as before, ```sh warning: [email protected]+5.3.0-patched: "`background_threads_runtime_support` not supported for `riscv64gc-unknown-linux-musl`" error: failed to run custom build...

seems not work for this case, ```yml name: build env: GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} CARGO_TERM_COLOR: always on: workflow_call: inputs: path: default: 'Cargo.toml' required: true type: string target: default: 'x86_64-unknown-linux-gnu' required:...