Bug 830751 – app-misc/tealdeer fails to compile

• Status: RESOLVED FIXED
• Product: GURU

[Description Arctic5824 2022-01-08 04:55:54 UTC]

Emerge said to provide the following:
emerge --info '=app-misc/tealdeer-1.5.0::guru'
http://ix.io/3Lsz

emerge -pqv '=app-misc/tealdeer-1.5.0::guru'
http://ix.io/3LsA

/var/tmp/portage/app-misc/tealdeer-1.5.0/temp/build.log
http://ix.io/3LsC


I have experienced a similar error in the past when using cargo, it might be a missing dependency

[Comment 1 Sam James 2022-01-08 04:58:50 UTC]

Please attach the relevant logs, pastebins expire. Thanks!

[Comment 2 Arctic5824 2022-01-09 00:06:33 UTC]

Created attachment 761666 [details]
build.log

[Comment 3 Arctic5824 2022-01-09 00:06:53 UTC]

Created attachment 761667 [details]
emerge --info '=app-misc⁄tealdeer-1.5.0::guru'

[Comment 4 Arctic5824 2022-01-09 00:07:12 UTC]

Created attachment 761668 [details]
emerge -pqv '=app-misc⁄tealdeer-1.5.0::guru'

[Comment 5 Vladislav Dudar 2022-01-14 12:00:18 UTC]

It looks like you overoptimized your system resulting to the failure, try removing the LTO related and O3 flags from CFLAGS and recompiling. The ebuild should automatically remove the flags in question, I'll push out a fix today.

[Comment 6 James Beddek 2022-01-14 12:12:36 UTC]

(In reply to Vladislav Dudar from comment #5)
> It looks like you overoptimized your system resulting to the failure, try
> removing the LTO related and O3 flags from CFLAGS and recompiling. The
> ebuild should automatically remove the flags in question, I'll push out a
> fix today.

I don't think cargo cares about CFLAGS (for rust-only crates). Only RUSTFLAGS which is unset according to emerge --info.

I wouldn't remove flags until the reporter can confirm it fixes the issue anyways.

[Comment 7 Vladislav Dudar 2022-01-14 13:18:59 UTC]

James, the "ring" crate which is causing the issue in question does some obscure stuff while compiling itself. The entirety of the /crypto directory is written in either C or some other ASM-alike language. Also, I think there's been some similar issue in ::gentoo which got fixed by forcing the ebuild to skip LTO flags, plus another Rust based program had a bug report with it bombing the compile when -O3 is used.

References:
https://github.com/briansmith/ring/tree/main/crypto
https://github.com/InBetweenNames/gentooLTO/issues/781
https://github.com/gentoo/gentoo/commit/78e0d4ea5ceacc407f7c3acdec0b0eb2eff08ef0

[Comment 8 Vladislav Dudar 2022-01-14 20:38:20 UTC]

Fixed in Git but I forgot to mention the bug number in the commit, can someone @ Gentoo dev team close this now? Thanks in advance.

[Comment 9 James Beddek 2022-01-14 23:13:46 UTC]

Thanks for the info, you are correct of course. There's also an upstream bug report about it: https://github.com/briansmith/ring/issues/1444

I'll close this once your commit has been merged into master