Skip to content

compat.mimalloc: no link names for an ok image; no -latomic - #659

Merged
Sunrisepeak merged 1 commit into
mainfrom
compat-mimalloc-openkal
Nov 1, 2026
Merged

Sunrisepeak merged 1 commit into
mainfrom
compat-mimalloc-openkal

Conversation

@Sunrisepeak

Copy link
Copy Markdown
Member

compat.mimalloc: an ok image names nothing at its link, and Linux no longer names -latomic.

  • An ok image (<arch>-openkal) read the linux block, and its link failed on -lpthread and -lrt: the image's C library supplies threads and clocks, and an image imports kal_* alone. A new openkal block names no link flags. The key is written out (ldflags = {}), because a block with no key is read as no block.
  • -latomic is gone from the linux block. Upstream links it only where it finds the library, and mimalloc's atomics are lock-free on every architecture this index builds for. The LLVM toolchain, above a C library of the graph, has no such archive.
  • Found while embedding 3.6.1 in openkal-musl 0.26 (mcpp design 2026-11-02 part 3, §7.1). mimalloc-tests passes locally, and openkal-musl's examples/strings builds and runs as an x86_64 ok image with this descriptor.

Co-authored-by: speak-agent 248744407+speak-agent@users.noreply.github.com

Co-authored-by: speak-agent <248744407+speak-agent@users.noreply.github.com>
@Sunrisepeak
Sunrisepeak merged commit 4487e21 into main Nov 1, 2026
18 checks passed
@Sunrisepeak
Sunrisepeak deleted the compat-mimalloc-openkal branch November 1, 2026 20:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant