NetBSD Build Errors
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- cpp
- Domain
- operating-systems
Research direction
Start by reviewing libs/filesystem/src/directory.cpp around line 273 and src/posix/close_handles.cpp around line 188, then reproduce the reported build on NetBSD. Investigate the dirfd compilation errors and verify that Boost Process builds successfully after the related pull request is considered.
Written by the indexing model from the issue text.
Description
Got someone else online to test boost process for me on their NetBSD machine and these are the errors they got:
In file included from ../../../../libs/filesystem/src/directory.cpp:38:
../../../../libs/filesystem/src/directory.cpp: In function ‘int boost::filesystem::detail::{anonymous}::dir_itr_fd(const boost::filesystem::detail::dir_itr_imp&, boost::system::error_code&)’:
../../../../libs/filesystem/src/directory.cpp:273:16: error: expected id-expression before ‘(’ token
273 | int fd = ::dirfd(static_cast< DIR* >(imp.handle));
| ^~~~~
In file included from ../../src/posix/close_handles.cpp:88:
../../src/posix/close_handles.cpp: In function ‘void boost::process::v2::posix::detail::close_all(const std::vector<int>&, boost::system::error_code&)’:
../../src/posix/close_handles.cpp:188:21: error: expected id-expression before ‘(’ token
188 | auto dir_fd = ::dirfd(dir.get());
| ^~~~~
Note, the above errors should be all that's left hopefully once my recent pull request gets merged.
Special thanks to @NishiOwO for testing boost process on NetBSD using my pull request's branch.
- 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 ·