[GH-ISSUE #65] duplicate symbol: RegisterTtlObjects #37

New issue

Closed

opened 2026-10-26 09:43:54 +00:00 by bsakaguchi · 5 comments

bsakaguchi commented

2026-10-26 09:43:54 +00:00

Owner

Originally created by @iamazy on GitHub (Mar 3, 2025).
Original GitHub issue: https://github.com/deepseek-ai/3FS/issues/65

I compiled 3FS on ubuntu22.04-aarch64, but got error

why x86_86 has no problem :)

Originally created by @iamazy on GitHub (Mar 3, 2025). Original GitHub issue: https://github.com/deepseek-ai/3FS/issues/65 I compiled 3FS on ubuntu22.04-aarch64, but got error ![Image](https://github.com/user-attachments/assets/4fa3a21d-c756-4474-a3ad-2749c2e95bb1) why x86_86 has no problem :)

bsakaguchi closed this issue

2026-10-26 09:43:55 +00:00

bsakaguchi commented

2026-10-26 09:43:56 +00:00

Author

Owner

@iamazy commented on GitHub (Mar 3, 2025):

Maybe the conflict is caused by the fact that both kv and chunk-engine depend on rocksdb, and storage_main also depends on both kv and chunk-engine, and chunk_engine is staticlib that linked by linker

@iamazy commented on GitHub (Mar 3, 2025): Maybe the conflict is caused by the fact that both kv and chunk-engine depend on rocksdb, and storage_main also depends on both kv and chunk-engine, and chunk_engine is staticlib that linked by linker

bsakaguchi commented

2026-10-26 09:43:56 +00:00

Author

Owner

@Nugine commented on GitHub (Mar 4, 2025):

Mention #30 here

@Nugine commented on GitHub (Mar 4, 2025): Mention #30 here

bsakaguchi commented

2026-10-26 09:43:56 +00:00

Author

Owner

@iamazy commented on GitHub (Mar 4, 2025):

@Nugine Hi, I have made a few changes to the 3FS code to adapt it to the aarch64 architecture, but I encountered the problem mentioned above. I believe my issue is different from #30

@iamazy commented on GitHub (Mar 4, 2025): @Nugine Hi, I have made a few changes to the 3FS code to adapt it to the aarch64 architecture, but I encountered the problem mentioned above. I believe my issue is different from #30

bsakaguchi commented

2026-10-26 09:43:56 +00:00

Author

Owner

@SF-Zhou commented on GitHub (Mar 4, 2025):

Maybe the conflict is caused by the fact that both kv and chunk-engine depend on rocksdb, and storage_main also depends on both kv and chunk-engine, and chunk_engine is staticlib that linked by linker

We may need to add another patch here. I'll get it added ASAP.

@SF-Zhou commented on GitHub (Mar 4, 2025): > Maybe the conflict is caused by the fact that both kv and chunk-engine depend on rocksdb, and storage_main also depends on both kv and chunk-engine, and chunk_engine is staticlib that linked by linker We may need to add another patch here. I'll get it added ASAP.

bsakaguchi commented

2026-10-26 09:43:57 +00:00

Author

Owner

@SF-Zhou commented on GitHub (Mar 4, 2025):

I have added another patch for RocksDB (#88). You can pull the latest code from the main branch, then run ./patches/apply.sh, and try compiling again. This patch addresses all currently known symbol conflicts.

@SF-Zhou commented on GitHub (Mar 4, 2025): I have added another patch for RocksDB (#88). You can pull the latest code from the main branch, then run `./patches/apply.sh`, and try compiling again. This patch addresses all currently known symbol conflicts.

bsakaguchi referenced this issue

2026-10-26 09:47:59 +00:00

[PR #37] [MERGED] chore: fix architectures and endianness check #261