Boost.Process V2 doesn't compile with musl library
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 52/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- cpp, linux
- Domain
- build-system, operating-systems
Research direction
Reproduce the failure on Void Linux with musl, then inspect boost/process/v2/posix/detail/close_handles.ipp around lines 128-145, where the compiler reports missing close_range declarations. Done means Boost.Process V2 compiles successfully in that environment without the reported errors.
Written by the indexing model from the issue text.
Description
If I try to build code which works with glibc https://github.com/freeorion/freeorion/pull/5156 it failes to build on Void linux with musl library:
2025-03-11T03:42:09.7575013Z /usr/include/boost/process/v2/posix/detail/close_handles.ipp: In function 'void boost::process::v2::posix::detail::close_all(const std::vector<int>&, boost::system::error_code&)':
2025-03-11T03:42:09.7576711Z /usr/include/boost/process/v2/posix/detail/close_handles.ipp:128:15: error: '::close_range' has not been declared; did you mean 'copy_range'?
2025-03-11T03:42:09.7578069Z 128 | ::close_range(0, whitelist.front() - 1, CLOSE_RANGE_UNSHARE);
2025-03-11T03:42:09.7578554Z | ^~~~~~~~~~~
2025-03-11T03:42:09.7578891Z | copy_range
2025-03-11T03:42:09.7579757Z /usr/include/boost/process/v2/posix/detail/close_handles.ipp:138:19: error: '::close_range' has not been declared; did you mean 'copy_range'?
2025-03-11T03:42:09.7580810Z 138 | ::close_range(mine + 1, next - 1, CLOSE_RANGE_UNSHARE);
2025-03-11T03:42:09.7581305Z | ^~~~~~~~~~~
2025-03-11T03:42:09.7581672Z | copy_range
2025-03-11T03:42:09.7582604Z /usr/include/boost/process/v2/posix/detail/close_handles.ipp:142:11: error: '::close_range' has not been declared; did you mean 'copy_range'?
2025-03-11T03:42:09.7583836Z 142 | ::close_range(whitelist.back() + 1, std::numeric_limits<int>::max(), CLOSE_RANGE_UNSHARE);
2025-03-11T03:42:09.7584466Z | ^~~~~~~~~~~
2025-03-11T03:42:09.7584805Z | copy_range
2025-03-11T03:42:09.7585693Z /usr/include/boost/process/v2/posix/detail/close_handles.ipp:145:11: error: '::close_range' has not been declared; did you mean 'copy_range'?
2025-03-11T03:42:09.7586932Z 145 | ::close_range(0, std::numeric_limits<int>::max(), CLOSE_RANGE_UNSHARE);
2025-03-11T03:42:09.7587491Z | ^~~~~~~~~~~
2025-03-11T03:42:09.7587829Z | copy_range
- Dominant language
- C++
- Stars
- 145
- Forks
- 151
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from boostorg/process
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 1/5 Under an hour Newbie friendliness 72/100
-
Difficulty 1/5 Under an hour Newbie friendliness 68/100
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
All issues in boostorg/process
Similar issues
-
enhancement
Difficulty 1/5 Under an hour Newbie friendliness 88/100
QuantStack/git2cpp#187 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
mlcommons/mobile_app_open#1182 ·
-
Needs-Triage
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
microsoft/winget-cli#6547 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
AXERA-TECH/ax-llm#77 ·