Build fails on ARM windows 11 with "No matching toolchains found for types: @@aspect_bazel_lib+//lib:copy_to_directory_toolchain_type"

[corneliusroemer]

I've tried to build the client from source on windows 11 ARM but am getting a build error in CI and locally on a VM (through Parallels on my macbook).

Key error seems to be:

ERROR: C:/users/cr/code/datasets/client/openapi/BUILD:40:22: While resolving toolchains for target //openapi:gofiles.v2.go (10dcefc): No matching toolchains found for types:
  @@aspect_bazel_lib+//lib:copy_to_directory_toolchain_type

Full log:

 bazelisk build apps/public/Datasets/...
(01:17:21) INFO: Current date is 2025-05-28
(01:17:22) WARNING: C:/users/cr/code/datasets/client/MODULE.bazel:16:24: The module extension go_deps defined in @gazelle//:extensions.bzl reported incorrect imports of repositories via use_repo():

Not imported, but reported as direct dependencies by the extension (may cause the build to fail):
    com_github_stretchr_testify, ke_bou_monkey

Fix the use_repo calls by running 'bazel mod tidy'.
(01:17:39) ERROR: C:/users/cr/code/datasets/client/openapi/BUILD:40:22: While resolving toolchains for target //openapi:gofiles.v2.go (10dcefc): No matching toolchains found for types:
  @@aspect_bazel_lib+//lib:copy_to_directory_toolchain_type
To debug, rerun with --toolchain_resolution_debug='@@aspect_bazel_lib+//lib:copy_to_directory_toolchain_type'
For more information on platforms or toolchains see https://bazel.build/concepts/platforms-intro.
(01:17:39) ERROR: Analysis of target '//apps/public/Datasets/v2/datasets/flags:flags' failed; build aborted: Analysis failed
(01:17:39) INFO: Elapsed time: 18.611s, Critical Path: 3.62s
(01:17:39) INFO: 1 process: 1 internal.
(01:17:39) ERROR: Build did NOT complete successfully
(01:17:39) FAILED:
    Fetching repository @@gazelle++go_deps+com_github_antihax_optional; starting 16s
    Fetching repository @@gazelle++go_deps+com_github_thediveo_enumflag; starting 16s
    Fetching repository @@gazelle++go_deps+com_github_spf13_pflag; starting 16s
    Fetching repository @@gazelle++go_deps+com_github_spf13_cobra; starting 16s
    Fetching repository @@gazelle++go_deps+com_github_araddon_dateparse; starting 16s
    Fetching repository @@gazelle++go_deps+org_golang_x_text; starting 16s
    Fetching repository @@gazelle++go_deps+org_golang_x_exp; starting 16s
    Fetching repository @@gazelle++go_deps+com_gitlab_metakeule_fmtdate; starting 16s ... (14 fetches)

It's reproducible in ci, not an artifact of VM emulation:

https://github.com/corneliusroemer/datasets/actions/runs/15287836003/job/43001614955#step:5:50

[ericcox1]

Hi @corneliusroemer,

Thanks for opening this issue. We'll investigate soon and I will comment on this thread with any updates.

Best,
Eric

[corneliusroemer]

Thanks! This isn't super important, just thought I log this here in case someone else comes across it and figures out a solution.

I'm kind of curious as well how you manage to build the binaries without the error!

[BradHolmes]

We cross-build all binaries on linux-amd64 hosts. Based on the error message, I see that aspect-bazel-lib does not support windows arm64 at this time. There is a closed issue with a request just 2 days ago to re-open it. bazel-contrib/bazel-lib#1076