openvinotoolkit / openvinotoolkit/npu_compiler

Mysterious build failure on naming style check.

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

Nobody has claimed this yet.

Dominant language
MLIR
Stars
100
Forks
50
Avg merge
3h 57m
Merged PRs (30d)
1

Description

I'm currently working on OpenVino commit c01cd93e24d1cd78bfbb401eed51c08fb93e0816 with tagname 2025.2.0 and trying to build this project with commit d5d219ee0ffa5c6a0e3af6b99675b94e28e25583(tag: npu_ud_2025_24_rc1). I followed the build on Linux instructions. On step 2.1, the last cmake command failed with the following error:

[  0%] [ncc naming style] src/common/util/include/openvino/util/variant_visitor.hpp
cd /home/tjm/.cache/pikaur/build/openvino/build-x86_64/src/common/util && /sbin/cmake -D Python3_EXECUTABLE=/sbin/python3.13 -D NCC_PY_SCRIPT=/home/tjm/.cache/pikaur/build/openvino/cmake/developer_package/ncc_naming_style/ncc/ncc.py -D INPUT_FILE=/home/tjm/.cache/pikaur/build/openvino/src/common/util/include//openvino/util/variant_visitor.hpp -D OUTPUT_FILE=/home/tjm/.cache/pikaur/build/openvino/build-x86_64/ncc_naming_style/src/common/util/include/openvino/util/variant_visitor.hpp.ncc_style -D DEFINITIONS= -D CLANG_LIB_PATH=/usr/lib/libclang.so -D STYLE_FILE=/home/tjm/.cache/pikaur/build/openvino/cmake/developer_package/ncc_naming_style/openvino.style -D ADDITIONAL_INCLUDE_DIRECTORIES=/home/tjm/.cache/pikaur/build/openvino/src/common/util/include/ -D EXPECTED_FAIL=FALSE -P /home/tjm/.cache/pikaur/build/openvino/cmake/developer_package/ncc_naming_style/ncc_run.cmake
Total number of errors = 1

/home/tjm/.cache/pikaur/build/openvino/src/common/util/include//openvino/util/variant_visitor.hpp:14:1: "<deduction guide for VariantVisitor>(Ts...)" does not match "^(operator.+|[\w]+|SoPtr.+|Impl<.*>)$" associated with FunctionTemplate

CMake Error at /home/tjm/.cache/pikaur/build/openvino/cmake/developer_package/ncc_naming_style/ncc_run.cmake:44 (message):
  [ncc naming style] Naming style check failed for
  /home/tjm/.cache/pikaur/build/openvino/src/common/util/include//openvino/util/variant_visitor.hpp


make[3]: *** [src/common/util/CMakeFiles/openvino_util_ncc_check.dir/build.make:192: ncc_naming_style/src/common/util/include/openvino/util/variant_visitor.hpp.ncc_style] Error 1
make[3]: *** Deleting file 'ncc_naming_style/src/common/util/include/openvino/util/variant_visitor.hpp.ncc_style'
make[3]: Leaving directory '/home/tjm/.cache/pikaur/build/openvino/build-x86_64'
make[2]: *** [CMakeFiles/Makefile2:21995: src/common/util/CMakeFiles/openvino_util_ncc_check.dir/all] Error 2
make[2]: Leaving directory '/home/tjm/.cache/pikaur/build/openvino/build-x86_64'
make[1]: *** [CMakeFiles/Makefile2:129451: build-modules/npu_compiler/src/vpux_driver_compiler/src/vpux_compiler_l0/CMakeFiles/npu_driver_compiler.dir/rule] Error 2
make[1]: Leaving directory '/home/tjm/.cache/pikaur/build/openvino/build-x86_64'
make: *** [Makefile:29661: npu_driver_compiler] Error 2

The error message suggests that there is a source code lint issue with the latest release. If the latest release is not production-ready, which stable release should I expect a successful build?

Contributor guide

Open the contributing guide

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 with the Linux build instructions in src/vpux_driver_compiler/docs/how_to_build_driver_compiler_on_linux.md and reproduce step 2.1 at the reported commits. Inspect src/common/util/include/openvino/util/variant_visitor.hpp and the ncc naming-style command output. Done means determining whether this is a release regression and identifying the release or change that permits a successful build.

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
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.