1.86.0 build fails on NetBSD
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 38/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- cpp
- Domain
- build-system, operating-systems
Research direction
Start by examining libs/process/src/ext/cmd.cpp around lines 315 and 326, where the NetBSD build reports that vec cannot convert to boost::process::v2::shell. Reproduce the 1.86.0 build with the shown compiler settings and investigate the return type mismatch. Done means the Process sources compile successfully on NetBSD.
Written by the indexing model from the issue text.
Description
libs/process/src/ext/cmd.cpp: In function 'boost::process::v2::shell boost::process::v2::ext::cmd(boost::process::v2::pid_type, boost::system::error_code&)':
libs/process/src/ext/cmd.cpp:315:61: error: could not convert 'vec' from 'std::vector<std::__cxx11::basic_string<char> >' to 'boost::process::v2::shell'
315 | if (!kd) {BOOST_PROCESS_V2_ASSIGN_LAST_ERROR(ec) return vec;}
| ^~~
| |
| std::vector<std::__cxx11::basic_string<char> >
libs/process/src/ext/cmd.cpp:326:12: error: could not convert 'vec' from 'std::vector<std::__cxx11::basic_string<char> >' to 'boost::process::v2::shell'
326 | return vec;
| ^~~
| |
| std::vector<std::__cxx11::basic_string<char> >
"g++" -fvisibility-inlines-hidden -pthread -O3 -finline-functions -Wno-inline -Wall -fvisibility=hidden -DBOOST_ALL_NO_LIB=1 -DBOOST_ASIO_NO_DEPRECATED -DBOOST_ATOMIC_STATIC_LINK=1 -DBOOST_COBALT_USE_STD_PMR=1 -DBOOST_FILESYSTEM_STATIC_LINK=1 -DBOOST_PROCESS_SOURCE=1 -DNDEBUG -I"." -c -o "bin.v2/libs/process/build/gcc-12/release/arm_64/link-static/pch-off/threading-multi/visibility-hidden/ext/cmd.o" "libs/process/src/ext/cmd.cpp"
- 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
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
google/libultrahdr#485 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
godotengine/godot#123776 ·
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 60/100
-
good first issue
Difficulty 1/5 Under an hour Newbie friendliness 90/100
-
good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
ros2/common_interfaces#344 ·