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

Merge bitcoin/bitcoin#32266: depends: Avoid `warning: "_FORTIFY_SOURCE" redefined` for `libevent`

Public commit record

What the developer wrote

Authored by merge-script

81/100 · Strong
Merge bitcoin/bitcoin#32266: depends: Avoid `warning: "_FORTIFY_SOURCE" redefined` for `libevent`

fe71a4b139f3a142468c2e931775813bc8f9d2ad depends: Avoid `warning: "_FORTIFY_SOURCE" redefined` for `libevent` (Hennadii Stepanov)

Pull request description:

On Alpine Linux 3.12.3, compiling the `libevent` package produces multiple warnings:
```
$ gmake -C depends -j $(nproc) libevent
<snip>
<command-line>: warning: "_FORTIFY_SOURCE" redefined
<built-in>: note: this is the location of the previous definition
<snip>
```

This PR fixes these warnings.

ACKs for top commit:
shahsb:
ACK https://github.com/bitcoin/bitcoin/pull/32266/commits/fe71a4b139f3a142468c2e931775813bc8f9d2ad
maflcko:
lgtm ACK fe71a4b139f3a142468c2e931775813bc8f9d2ad
theuni:
utACK fe71a4b139f3a142468c2e931775813bc8f9d2ad

Tree-SHA512: 0a3ffb2a4cf811bce93addac8e5394cf6b3d79a46245cbdd8488771b9b51e56f66cd9222548138041e69183d52ad4b909d3d1441593f9d79d557d6c000fb324b
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference
The short version

What changed, and why it matters

This commit is a routine build-system cleanup. It removes harmless compiler warnings about a duplicated security-hardening macro (_FORTIFY_SOURCE) when compiling the libevent dependency on Alpine Linux. It does not change how Bitcoin Core runs or how it protects user funds.

Recommended action

No security action required. Treat as a normal build-hygiene merge.

Security signals we found

01

Build-system hardening macro _FORTIFY_SOURCE is mentioned, but the change does not weaken it.

02

No changes to consensus, wallet, cryptography, P2P, RPC, or any runtime component.

03

Large unrelated file additions in the diff are infrastructure/CI/template files, not part of the security-relevant change.

Risk score

Why this scored 15/100

Our methodology →
Potential impact 0/30
Exploitability 0/25
Stealth signal 0/15
Affected reach 0/15
Confidence 10/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.