mirror of
https://github.com/deepseek-ai/3FS.git
synced 2026-11-05 00:47:47 +00:00
[GH-ISSUE #87] [Build error] Build failed on Ubuntu22.04/Docker following the guide #49
Labels
No labels
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
deepseek-ai/3FS#49
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @6607changchun on GitHub (Mar 4, 2025).
Original GitHub issue: https://github.com/deepseek-ai/3FS/issues/87
I started a container of Ubuntu:22.04 on WSL2, and build 3FS following the guide. But the compiler complained about
constevalerror.Here is the related log:
Other environment infomation:
Clang 14.0
Host Nixos 24.11 on WSL2
I will try clang-17 later and paste the result.
@HelloPtr commented on GitHub (Mar 4, 2025):
i have the same problem
@6607changchun commented on GitHub (Mar 4, 2025):
Quick Reply:
I changed to clang-18, and it seems that everything is well. But I modified dome codes:
CMakeLists.txt(top level): remove '-fcoroutine-ts'.
remove -Werror
some compiler errors.(easy to fix)
The progress completes 30%, and I will paste the following result later.
@6607changchun commented on GitHub (Mar 4, 2025):
Compilation complete, but some modifications are made. I'm not sure whether these modifications preserve the semantic, as some of them are probable breaking changes. I haven't tested the binaries, and have no idea about it works.
Here are my patches for references, of which some modifications are absolutely redundant.
0001-build-change-to-clang-18.patch
0001-build-clickhouse-change-to-clang-18.patch
0001-build-folly-change-to-clang-18.patch
0001-build-jemalloc-change-to-clang-18.patch
0001-build-leveldb-change-to-clang-18.patch
0001-build-rocksdb-change-to-clang-18.patch
Anyway, it works on my computer.
@6607changchun commented on GitHub (Mar 5, 2025):
A hotfix: modification of
executor.setNumthreads()is wrong. It is supposed to be preserved.