Link error of call get_system_scheduler()
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
Research direction
No source files or tests are named. Start by reproducing the linker failure with exec::get_system_scheduler() on the listed platforms and compare it with exec::static_thread_pool; done means the provided scheduler example links and runs without the missing __query_system_context_interface symbol.
Written by the indexing model from the issue text.
Description
Description:
I'm encountering an issue when using exec::get_system_scheduler() in my code. The code compiles successfully when using exec::static_thread_pool, but it fails when using exec::get_system_scheduler().
Code:
void l3_scheduler() {
stdexec::scheduler auto sch = exec::get_system_scheduler();
stdexec::sender auto computation =
stdexec::schedule(sch) | stdexec::then([] {
fmt::println("Hello, from a different thread");
});
stdexec::sync_wait(std::move(computation));
}
The error message is as follows:
"__query_system_context_interface(__uuid const&)", referenced from:
l3_scheduler() in main.cpp.o
ld: symbol(s) not found for architecture arm64
The following code works without issues:
exec::static_thread_pool pool(8);
auto sch = pool.get_scheduler();
Environment:
-
macOS: M1 MacBook Pro (arm64)
-
Ubuntu: x86 architecture
-
Compiler: clang++-19
Steps to Reproduce:
-
Use stdexec::scheduler with exec::get_system_scheduler().
-
Attempt to compile the code on macOS M1 or Ubuntu (x86).
-
Observe the linker error.
- Dominant language
- C++
- Stars
- 2.4k
- Forks
- 270
- Avg merge
- 2d 16h
- Merged PRs (30d)
- 43
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 NVIDIA/stdexec
-
inline_scheduler's namespace-scope static_assert fails under nvcc (private nested __sender access) Open
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
-
Difficulty 4/5 3-5 days Newbie friendliness 65/100
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 ·