Closed as not planned
Labels
buildIssues and PRs related to Node.js builds or CI infrastructure.Issues and PRs related to Node.js builds or CI infrastructure.staleIssues and PRs marked stale due to inactivity and scheduled for automatic closure.Issues and PRs marked stale due to inactivity and scheduled for automatic closure.
Description
See in https://ci.nodejs.org/job/node-test-commit-linux/68776/nodes=fedora-latest-x64/consoleFull
LIEF lines have both: -std=gnu++20 -std=gnu++17
Metadata
Metadata
Assignees
Labels
buildIssues and PRs related to Node.js builds or CI infrastructure.Issues and PRs related to Node.js builds or CI infrastructure.staleIssues and PRs marked stale due to inactivity and scheduled for automatic closure.Issues and PRs marked stale due to inactivity and scheduled for automatic closure.
Activity
joyeecheung commentedon Mar 6, 2026
Where does
-std=gnu++20come from? I think for LIEF we can specificallycflags_cc!that, LIEF currently needs to be built with C++17 to avoid namespace conflicts.targos commentedon Mar 7, 2026
I suppose it comes from
common.gypicoursgranja4-commits commentedon Mar 11, 2026
build: fix stray debug string in LIEF defines
build: fix stray debug string in LIEF defines
build: fix stray debug string in LIEF defines
github-actions commentedon Jul 20, 2026
This issue has been marked as stale due to 90 days of inactivity.
It will be automatically closed in 30 days if no further activity occurs. If this is still relevant, please leave a comment or update it to keep it open.
build: remove duplicate C++ standard flags from LIEF