Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[compile error] #if #endif pairs did not match in boost\assert.hpp

Open
#29 11 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
20/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
cpp
Domain
compilers

Research direction

Start by inspecting boost/assert.hpp and reproducing the reported preprocessing error with the stated Windows 11, VS2022 or vc143, and nvcc from CUDA 11.6 setup. Compare the NVCC include-path and preprocessing behavior with the working Visual Studio case; done means identifying whether the mismatch is in Boost.Assert or the compilation environment and documenting a reproducible cause.

Written by the indexing model from the issue text.

Description

When I tried to compile PCL(PointCloudLibrary) with the Boost file compiled by myself, the error showed that #if #endif pairs did not match and the error was reported in the assert.hpp file from Boost, so I checked the file in VS2022 and didn't see any error prompt. I have compared the latest version of Boost compiled files, and every line is the same. (Because it is necessary to compile part of the code with NVCC, NVCC always prompts that the *.hpp file of Boost cannot be found. Even though I have completely set it in path and CMake, I changed the include directory to a pure English absolute path, but I think this should not be the reason. ) I hope to get an answer, thank you very much!
My platform: Windows11
Compiler: vs2022 (or vc143) & nvcc (from cuda 11.6)

Dominant language
C++
Stars
35
Forks
77
PR merge metrics
No merged PRs in 30d

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.

More from boostorg/assert

All issues in boostorg/assert

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.