Created attachment 894595 [details] emerge --info net-misc/nextcloud-client With USE="lto", `net-misc/nextcloud-client` builds but fails at runtime with a segmentation fault. I tested the following versions: - net-misc/nextcloud-client-3.12.3 (which is currently masked under ~amd64) - net-misc/nextcloud-client-3.11.1 (currently showing as stable in Portage) Both exhibited the problem. I could not test 3.13.0 because of #930943. The runtime seg. fault ceases to occur if LTO is disabled for the `net-misc/nextcloud-client` package by adding `-Wno-error=odr -Wno-error=lto-type-mismatch -Wno-error=strict-aliasing -fno-lto` as recommended in the wiki. (Since it is a runtime fault, presumably only the last of those flags is salient.) `emerge --info` output is attached, with the fix applied. The only difference between the failure case and those shown is the addition of the no-lto flags, above.
There is an upstream bug for this but it was closed due to inactivity: https://github.com/nextcloud/desktop/issues/2790 See also: https://github.com/nextcloud/desktop/issues/3090 https://github.com/nextcloud/desktop/issues/4924
