fix: mips-* disabled, moka uses atomic64 by default

- ref #1793 - https://github.com/moka-rs/moka#compile-errors-on-some-32-bit-platforms
shadowsocks · Dec 1, 2024 · 95971a9 · 95971a9
1 parent ce138db
commit 95971a9
Showing 1 changed file with 9 additions and 6 deletions.
diff --git a/.github/workflows/build-release.yml b/.github/workflows/build-release.yml
@@ -46,22 +46,25 @@ jobs:
             toolchain: stable
           - target: aarch64-unknown-linux-musl
             toolchain: stable
-          - target: mips-unknown-linux-gnu
-            toolchain: nightly
+          # FIXME: moka uses atomic64 by default
+          # - target: mips-unknown-linux-gnu
+          #   toolchain: nightly
           # cross mips-*-musl images are disabled
           # - target: mips-unknown-linux-musl
           #   toolchain: nightly
-          - target: mipsel-unknown-linux-gnu
-            toolchain: nightly
+          # FIXME: moka uses atomic64 by default
+          # - target: mipsel-unknown-linux-gnu
+          #   toolchain: nightly
+          # cross mips-*-musl images are disabled
           # - target: mipsel-unknown-linux-musl
           #   toolchain: nightly
           # FIXME: ring doesn't support mips64 CPU
           # - target: mips64-unknown-linux-gnuabi64
           #   toolchain: nightly
           # - target: mips64-unknown-linux-muslabi64
           #   toolchain: nightly
-          - target: mips64el-unknown-linux-gnuabi64
-            toolchain: nightly
+          # - target: mips64el-unknown-linux-gnuabi64
+          #   toolchain: nightly
           # FIXME: Link Error. 
           #   = note: mips64el-linux-muslsf-gcc: error: crt1.o: No such file or directory
           #           mips64el-linux-muslsf-gcc: error: crti.o: No such file or directory