microsoft / microsoft/BitNet

Build Fails on Windows 10: CMake Cannot Locate `clang` / `clang++` Compiler

Open
#554 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C++
Stars
40.3k
Forks
3.7k
PR merge metrics
No merged PRs in 30d

Description

Environment

  • OS: Windows 10
  • Command: python setup_env.py -md models/BitNet-b1.58-2B-4T -q i2_s

Problem

When running the setup script, CMake fails to identify and locate the C/C++ compilers (clang / clang++). The build does not proceed beyond the configuration phase.

I also referenced #513 for potential solutions, but the suggestions there did not resolve the issue in my environment.

Error Output
-- The C compiler identification is unknown
-- The CXX compiler identification is unknown

CMake Error at CMakeLists.txt:2 (project):
  The CMAKE_C_COMPILER:
    clang
  is not a full path and was not found in the PATH.  Perhaps the extension is
  missing?
  Tell CMake where to find the compiler by setting either the environment
  variable "CC" or the CMake cache entry CMAKE_C_COMPILER to the full path to
  the compiler, or to the compiler name if it is in the PATH.

CMake Error at CMakeLists.txt:2 (project):
  The CMAKE_CXX_COMPILER:
    clang++
  is not a full path and was not found in the PATH.  Perhaps the extension is
  missing?
  Tell CMake where to find the compiler by setting either the environment
  variable "CXX" or the CMake cache entry CMAKE_CXX_COMPILER to the full path
  to the compiler, or to the compiler name if it is in the PATH.

-- Configuring incomplete, errors occurred!
Root Cause

The script attempts to use the ClangCL toolset on Windows with explicitly set clang / clang++ compilers. However, on some Windows environments:

  1. ClangCL is not installed or not properly configured.
  2. clang / clang++ are not present in the system PATH, causing CMake to fail.

Solution

I made two modifications in setup_env.py, after which the build completed successfully.

Change 1: Switch CMake Generator from ClangCL to MinGW Makefiles

Original:

OS_EXTRA_ARGS = {
    "Windows": ["-T", "ClangCL"],
}

Modified:

OS_EXTRA_ARGS = {
    "Windows": ["-G", "MinGW Makefiles"],
}

The -T ClangCL option requires a specific Clang installation that is compatible with MSVC. If this toolchain is not properly set up, CMake cannot locate the compiler.

Switching to MinGW Makefiles allows CMake to use the default system compiler (typically gcc/g++ from MinGW) without requiring ClangCL.

Change 2: Remove Explicit clang / clang++ Compiler Specification

Original:

run_command([
    "cmake", "-B", "build",
    _COMPILER_EXTRA_ARGS[arch],
    OS_EXTRA_ARGS.get(platform.system(), []),
    "-DCMAKE_C_COMPILER=clang",
    "-DCMAKE_CXX_COMPILER=clang++"
], log_step="generate_build_files")

Modified:

run_command([
    "cmake", "-B", "build",
    _COMPILER_EXTRA_ARGS[arch],
    OS_EXTRA_ARGS.get(platform.system(), [])
], log_step="generate_build_files")

The -DCMAKE_C_COMPILER=clang and -DCMAKE_CXX_COMPILER=clang++ flags forced CMake to look for Clang in PATH, which was not available.

Removing these flags allows CMake to auto-detect the default compiler provided by the MinGW Makefiles generator.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start in setup_env.py and inspect the Windows OS_EXTRA_ARGS and CMake compiler arguments, then review CMakeLists.txt and reproduce with python setup_env.py -md models/BitNet-b1.58-2B-4T -q i2_s. Done means CMake locates a Windows C/C++ compiler and the build completes beyond configuration without requiring unavailable clang or clang++ paths.

Written by the indexing model from the issue text.

Assessment

Tech stack
cmake, cpp, python
Domain
build-system
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
52/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.