AI-generated analysisPublished automatically and not human-verified. Validated context appears in community notes below.
← Watch feed
Informational 16 Bitcoin

ipc # build: Fix fuzz target CMakeLists.txt for external libmultiprocess

Public commit record

What the developer wrote

Authored by Ryan Ofsky

95/100 · Strong
ipc # build: Fix fuzz target CMakeLists.txt for external libmultiprocess

**What failed:** Build error: 'mp/proxy-io.h' file not found when
building the ipc fuzz target.

**Root cause:** Upstream commit 037ad770714 (fuzz: add IPC round-trip
target) added target_link_libraries(fuzz bitcoin_ipc_fuzz multiprocess)
using the bare 'multiprocess' target, which only exists in subtree
builds. With WITH_EXTERNAL_LIBMULTIPROCESS=ON, no 'multiprocess' cmake
target is defined, so the INTERFACE_INCLUDE_DIRECTORIES from the
installed libmultiprocess headers were never propagated to the fuzz
target, causing the missing-header error.

**Fix:** Changed to 'Libmultiprocess::multiprocess', which is the
canonical namespaced target available in both subtree and external builds.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Explains rationale or failure mode✓ Mentions testing or verification
The short version

What changed, and why it matters

This is a one-line build-system fix for a Bitcoin Core fuzz-testing target. It changes a CMake target name so the correct header paths are found when libmultiprocess is built externally instead of bundled. It does not change runtime behavior, consensus rules, or network code, and there is no security vulnerability being patched.

Recommended action

No security action required. Treat as a normal build fix; ensure CI covers WITH_EXTERNAL_LIBMULTIPROCESS=ON for the ipc fuzz target.

Security signals we found

01

No security-relevant code change: build configuration only

02

No functional, consensus, or network changes

03

No memory safety, cryptography, or permission changes

04

No vendor security disclosure or advisory language in commit

Risk score

Why this scored 16/100

Our methodology →
Potential impact 0/30
Exploitability 0/25
Stealth signal 0/15
Affected reach 2/15
Confidence 9/10
Evidence quality 5/5
Human-validated context

Community notes

Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.

No validated notes yet.

The AI analysis stands alone for now. Submit a note if you can add evidence or important context.