Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 863908 - sys-fs/sandboxfs-0.2.0 fails to compile (lto): undefined reference to __rbt_backtrace_create_state
Summary: sys-fs/sandboxfs-0.2.0 fails to compile (lto): undefined reference to __rbt_b...
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: No maintainer - Look at if you want to take care of it
Depends on:
Blocks: lto
  Show dependency tree
Reported: 2022-08-06 06:22 UTC by Agostino Sarubbo
Modified: 2024-03-11 03:24 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---

build.log (build.log,117.52 KB, text/plain)
2022-08-06 06:22 UTC, Agostino Sarubbo

Note You need to log in before you can comment on or make changes to this bug.
Description Agostino Sarubbo gentoo-dev 2022-08-06 06:22:47 UTC

Issue: sys-fs/sandboxfs-0.2.0 fails to compile (lto).
Discovered on: amd64 (internal ref: lto_tinderbox)

This machine uses lto with CFLAGS=-flto -Werror=odr -Werror=lto-type-mismatch -Werror=strict-aliasing

Here is a bit of explanation:

User to find possible runtime issues in packages. It likely means the package is unsafe to build & use with LTO.
For projects using the same identifier but with different types across different files, they must be fixed to be consistent across the codebase.

Used to find possible runtime issues in packages. These bugs are a problem anyway but may be even worse when combined with LTO. C++ code must comply with the One Definition Rule (ODR) - see

Used to find possible runtime issues in packages. These bugs are a problem anyway but may be even worse when combined with LTO.

- If upstream is friendly and still active, file a bug upstream. For emulators, codecs, games, or multimedia packages, it may be worth just applying a workaround instead, as upstreams sometimes aren't receptive to these bugs (VALID FOR ALL).
- Use the new 'filter-lto' from flag-o-matic.eclass as it's likely to be unsafe with LTO (VALID FOR lto-type-mismatch - odr).
- Fix it yourself if interested, of course (VALID FOR ALL).
- Append-flags -fno-strict-aliasing (VALID FOR strict-aliasing).
- Use memcpy() but a union is sometimes suitable too (VALID FOR strict-aliasing).
- -fstrict-aliasing is implied by -O2, so this must be addressed in some form (VALID FOR strict-aliasing).

See also:
Comment 1 Agostino Sarubbo gentoo-dev 2022-08-06 06:22:50 UTC
Created attachment 798151 [details]

build log and emerge --info
Comment 2 Agostino Sarubbo gentoo-dev 2022-08-06 06:22:52 UTC
Error(s) that match a know pattern in addition to what has been reported in the summary:

          /usr/lib/gcc/x86_64-pc-linux-gnu/12.1.1/../../../../x86_64-pc-linux-gnu/bin/ld: backtrace.6a1eaa9c-cgu.3:(.text._ZN9backtrace9symbolize12libbacktrace10syminfo_cb17h240e2c2aba150745E.llvm.2131448326532669379+0x66): undefined reference to `__rbt_backtrace_pcinfo'
          /usr/lib/gcc/x86_64-pc-linux-gnu/12.1.1/../../../../x86_64-pc-linux-gnu/bin/ld: backtrace.6a1eaa9c-cgu.3:(.text._ZN9backtrace9symbolize12libbacktrace7resolve17hb7bcd650ea48c443E+0xd3): undefined reference to `__rbt_backtrace_syminfo'
          backtrace.6a1eaa9c-cgu.3:(.text._ZN9backtrace9symbolize12libbacktrace10syminfo_cb17h240e2c2aba150745E.llvm.2131448326532669379+0x3f): undefined reference to `__rbt_backtrace_create_state'
          backtrace.6a1eaa9c-cgu.3:(.text._ZN9backtrace9symbolize12libbacktrace7resolve17hb7bcd650ea48c443E+0x71): undefined reference to `__rbt_backtrace_create_state'
error: linking with `x86_64-pc-linux-gnu-gcc` failed: exit status: 1
Comment 3 Eli Schwartz 2024-03-11 03:24:49 UTC
Apparently fixed by cargo.eclass, cannot reproduce anymore.