final step of build (`mimalloc-test-stress-dynamic`) fails on Amazon Linux 2
Maintainers usually reply within 1 day
Nobody has claimed this yet.
- #1159 by @emeryberger — closed without merging
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- c, cmake
- Domain
- build-system
Research direction
Reproduce the failure on Amazon Linux 2 with mkdir build && cd build && cmake .. && make. Inspect the CMake configuration for mimalloc-test-stress-dynamic and the referenced test/test-stress.c; done means the final target links successfully and the complete build finishes.
Written by the indexing model from the issue text.
Description
Bug description
- final step of build (
mimalloc-test-stress-dynamic) fails on Amazon Linux 2
Steps to reproduce:
- clone on Amazon Linux 2 instance, try to build as usual (
mkdir build && cd build && cmake .. && make).
Other information
$ uname -a
Linux xxx.us-east-1.amazon.com xxx.xxx #1 SMP Sat Sep 20 21:53:55 UTC 2025 x86_64 x86_64 x86_64 GNU/Linux
Error message (truncated):
[ 95%] Built target mimalloc-test-stress
[ 97%] Building C object CMakeFiles/mimalloc-test-stress-dynamic.dir/test/test-stress.c.o
[100%] Linking C executable mimalloc-test-stress-dynamic
CMakeFiles/mimalloc-test-stress-dynamic.dir/test/test-stress.c.o: In function `main':
test-stress.c:(.text.startup+0x106): undefined reference to `pthread_create'
test-stress.c:(.text.startup+0x12c): undefined reference to `pthread_join'
collect2: error: ld returned 1 exit status
make[2]: *** [mimalloc-test-stress-dynamic] Error 1
make[1]: *** [CMakeFiles/mimalloc-test-stress-dynamic.dir/all] Error 2
make: *** [all] Error 2
Fix status
PR incoming.
- Dominant language
- C
- Stars
- 13.6k
- Forks
- 1.2k
- Avg merge
- 18h 12m
- Merged PRs (30d)
- 20
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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 microsoft/mimalloc
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Building mimalloc with `-Wundef` compiler flag logs many warnings on undefined macrosPossibly taken @vstinner claimed this 1 day ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
microsoft/mimalloc#1506 · 5 comments ·
Maintainers usually reply within 1 day
-
stale
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
microsoft/mimalloc#1113 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
microsoft/mimalloc#886 · 4 comments · 1 reaction ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
microsoft/mimalloc#368 · 1 comment ·
Maintainers usually reply within 1 day
All issues in microsoft/mimalloc
Similar issues
-
needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
389ds/389-ds-base#8157 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
coolsnowwolf/lede#14305 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
Needs-Triage
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
Maintainers usually reply within 2 days