Open automorphism88 opened 3 years ago
I encountered the same error, and adding -ffat-lto-objects lets it build again.
dev-libs/libgcrypt-1.9.0::gentoo was built with the following:
USE="-doc -o-flag-munging -static-libs" ABI_X86="32 (64) (-x32)"
CFLAGS="-march=skylake -O3 -fgraphite-identity -floop-nest-optimize -fdevirtualize-at-ltrans -fipa-pta -fno-semantic-interposition -flto=auto -fuse-linker-plugin -pipe -falign-functions=32 -ffat-lto-objects -Wl,-O1 -Wl,--as-needed"
CXXFLAGS="-march=skylake -O3 -fgraphite-identity -floop-nest-optimize -fdevirtualize-at-ltrans -fipa-pta -fno-semantic-interposition -flto=auto -fuse-linker-plugin -pipe -falign-functions=32 -ffat-lto-objects -Wl,-O1 -Wl,--as-needed"
LDFLAGS="-Wl,-O1 -Wl,--as-needed -march=skylake -O3 -fgraphite-identity -floop-nest-optimize -fdevirtualize-at-ltrans -fipa-pta -fno-semantic-interposition -flto=auto -fuse-linker-plugin -pipe -falign-functions=32 -ffat-lto-objects"
Add this in your env:
gcry_cv_gcc_arm_platform_as_ok=no
gcry_cv_gcc_aarch64_platform_as_ok=no
or disable other platforms via EXTRA_ECONF (see ./configure --help).
Trying fat-lto-objects failed in configures C compilation test - usual occurrence with fat-lto-objects for a 32/64 multilib build. However applying the following upstream commit (needed to remove the last four hunks for s390 for the ebuild) fixes the LTO build.
Are you still having the same issue?
I don't seem to encounter with this issue on libgcrypt-1.9.2
All fine since the libgcrypt release with previously referenced commit.
I tried to build the libgcrypt 1.9.0 upgrade just now and got this error:
Disabling LTO allowed the build to complete successfully, but I haven't tried all possible combinations of flags to see if there might be a way to make LTO work with different flags. However, I did try disabling ccache, and that didn't help. Output of
emerge --info
is below: