Where's this unrecognized flag being set?

[spagdoon0411]

Targeting an esp32c3_devkitm. On a west build -b esp32c3_devkitm <application_name> I get an error:

cc1: error: unrecognized command-line option '-mmacosx-version-min=15.1'
ninja: build stopped: subcommand failed.
FATAL ERROR: command exited with status 1: /opt/homebrew/bin/cmake --build /Users/spandan/Projects/cpss/T
OM-OS/build

This seems to be associated with a flag related to MacOS, but I can't tell where it's being set. Here's the head and tail of the command that seems to run on the west build (excluding a bunch of -I imports):

FAILED: zephyr/CMakeFiles/offsets.dir/arch/riscv/core/offsets/offsets.c.o 
ccache /Users/spandan/zephyr-sdk-0.17.0/riscv64-zephyr-elf/bin/riscv64-zephyr-elf-gcc -DCONFIG_APP_BUILD_USE_FLASH_SECTIONS -DCONFIG_IDF_TARGET_ARCH_RISCV -DESP_PLATFORM -DKERNEL -DK_HEAP_MEM_POOL_SIZE=4096 -DPICOLIBC_LONG_LONG_PRINTF_SCANF -D__LINUX_ERRNO_EXTENSIONS__ -D__ZEPHYR__=1 -Dasm=__asm__ -I/Users/spandan/Projects/cpss/TOM-OS/zephyr/kernel/include

... 

-I/Users/spandan/Projects/cpss/TOM-OS/modules/hal/espressif/zephyr/esp32c3/../port/include/boot -isystem /Users/spandan/Projects/cpss/TOM-OS/zephyr/lib/libc/common/include -arch arm64 -isysroot /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX15.2.sdk -mmacosx-version-min=15.1 -fno-strict-aliasing -Os -imacros /Users/spandan/Projects/cpss/TOM-OS/build/zephyr/include/generated/zephyr/autoconf.h -fno-printf-return-value -fno-common -g -fdiagnostics-color=always -mabi=ilp32 -march=rv32imc_zicsr --sysroot=/Users/spandan/zephyr-sdk-0.17.0/riscv64-zephyr-elf/riscv64-zephyr-elf -imacros /Users/spandan/Projects/cpss/TOM-OS/zephyr/include/zephyr/toolchain/zephyr_stdint.h -fno-pic -fno-pie -specs=picolibc.specs -fstrict-volatile-bitfields -std=c99 -fno-lto -MD -MT zephyr/CMakeFiles/offsets.dir/arch/riscv/core/offsets/offsets.c.o -MF zephyr/CMakeFiles/offsets.dir/arch/riscv/core/offsets/offsets.c.o.d -o zephyr/CMakeFiles/offsets.dir/arch/riscv/core/offsets/offsets.c.o -c /Users/spandan/Projects/cpss/TOM-OS/zephyr/arch/riscv/core/offsets/offsets.c

Here's a shallow view of the project.

.
├── CMakeLists.txt
├── README.md
├── boards
│   ├── cpss
│   └── esp32c3_devkitm.overlay
├── build
│   ├── CMakeCache.txt
│   ├── CMakeFiles
│   ├── Kconfig
│   ├── app
│   ├── build.ninja
│   ├── build_info.yml
│   ├── build_info.yml.bak
│   ├── cmake_install.cmake
│   ├── compile_commands.json
│   ├── modules
│   ├── sysbuild_modules.txt
│   ├── zephyr
│   ├── zephyr_modules.txt
│   └── zephyr_settings.txt
├── build.sh
├── compile_commands.json
├── dsdl
│   ├── generate_type_headers.sh
│   ├── generated_dsdl
│   └── public_regulated_data_types
├── kconfig_dump.log
├── manifest
│   └── west.yml
├── modules
│   ├── crypto
│   ├── debug
│   ├── hal
│   └── lib
├── os
│   ├── CMakeLists.txt
│   ├── Kconfig
│   ├── TOM-Core
│   ├── boards
│   ├── boot.cpp
│   └── prj.conf
├── out.txt
├── small_file.c
└── zephyr
    ├── CMakeLists.txt
    ├── CODE_OF_CONDUCT.md
    ├── CONTRIBUTING.rst
    ├── Kconfig
    ├── Kconfig.constants
    ├── Kconfig.zephyr
    ├── LICENSE
    ├── MAINTAINERS.yml
    ├── README.rst
    ├── SDK_VERSION
    ├── VERSION
    ├── arch
    ├── boards
    ├── cmake
    ├── doc
    ├── drivers
    ├── dts
    ├── include
    ├── kernel
    ├── lib
    ├── misc
    ├── module.yml
    ├── modules
    ├── samples
    ├── scripts
    ├── share
    ├── snippets
    ├── soc
    ├── submanifests
    ├── subsys
    ├── tests
    ├── version.h.in
    ├── west.yml
    ├── zephyr-env.cmd
    └── zephyr-env.sh

41 directories, 43 files

Other applications using the same Zephyr SDK and Risc V toolchain in different workspaces build just fine, but sample applications in this workspace run into the same issue.

Would anyone happen to know where I might start to look to find where these flags are being set? Doesn't seem like it's in any of my modified CMakeLists, but I have a pretty big project. Does Zephyr do this?