`compiler` configuration option ignored

[frainfreeze]

On fresh Debian 12 install with uv managed venv following tries to use clang:

[build.targets.wheel.hooks.cython.options]
src = "...."
compiler = "gcc"
compile_args = [
  "-O3",
  { platforms = [
    "darwin",...

      /tmp/tmp15_ln98e/tmp/src/....o -I/usr/local/include -O3
      error: command 'clang' failed: No such file or directory

I have also tried following

compiler = [
  { platforms = ["darwin"], value = "clang" },
  { platforms = ["linux"], value = "gcc" }
]

TLDR; I want gcc to be used if clang is not available.

[frainfreeze]

Using this to manually set gcc on linux by default for now.

env = [
  { env = "CC", arg = "gcc", platforms = ["linux"] },
  { env = "CC", arg = "clang", platforms = ["darwin"] }
]

I believe clang pops up because of uv; "The Python binaries uv installs were built using clang so they have CC=clang in their sysconfig. Thus, when using a uv-managed python when clang isn't available, pip also fails to build." astral-sh/uv#8036 (comment)

[TSoli]

Can confirm the compiler options seems to be ignored for me too