Cargo build fails on missing jemalloc, ring dependencies.
Describe the bug
Hello,
I've got reth to fail building on Life and DogeOS GNU base (x86_64) apparently because of missing symbols from jemalloc and ring dependencies and possibly others.
These are some of the errors the linker returns:
/usr/bin/ld: reth.e2b465084b0dcf54-cgu.0:(.text._ZN7roaring7treemap8inherent50_$LT$impl$u20$roaring..treemap..RoaringTreemap$GT$14push_unchecked17h28292d492a8b175eE+0x347): undefined reference to `_rjem_sdallocx'
/usr/bin/ld: /tmp/rustcsz5CyQ/libring-532c18b2d1c8de1e.rlib(c322a0bcc369f531-x86_64-mont5-elf.o):/home/dev/.cargo/registry/src/index.crates.io-6f17d22bba15001f/ring-0.17.8/pregenerated/x86_64-mont5-elf.S:24: more undefined references to `ring_core_0_17_8_OPENSSL_ia32cap_P' follow
I'd like to provide more help but reth takes 12 hours or so to build on my machine, so I can hardly be of any help currently.
Steps to reproduce
The Ur universal build recipe I'm using to build reth is at reth-ur.
Platform(s)
Life GNU base (x86_64) DogeOS GNU base (x86_64)
Container Type
Not running in a container
What version/commit are you on?
I'm building reth 1.2.0
What database version are you on?
I still haven't been able to run reth.
Which chain / network are you on?
I am on no chain, because this is a report for a build error.
What type of node are you running?
Archive (default)
What prune config do you use, if any?
No response
If you've built Reth from source, provide the full command you used
The set of commands used to build the program are included in the universal build recipe I've linked.
Code of Conduct
- [x] I agree to follow the Code of Conduct
I wonder if this is some LTO issue, can you try building with "release" profile instead?
@mattsse I've edited the recipe to build with "release", will test when I'll go to sleep because I need the computer right now.
any updates @tallero ?
Sorry @emhane I had completely forgotten, will re-try tonight.
@emhane @mattsse same exact issue with release profile.
Here are the last 10,000 lines of build log.
This is the current version of the build recipe.
This issue is stale because it has been open for 21 days with no activity.
This issue is stale because it has been open for 21 days with no activity.
This issue was closed because it has been inactive for 7 days since being marked as stale.