final step of build (`mimalloc-test-stress-dynamic`) fails on Amazon Linux 2

Open
#1,158 0 comments 0 reactions 0 assignees View on GitHub

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

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from microsoft/mimalloc

All issues in microsoft/mimalloc

Similar issues

More C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.