Summary: | =app-office/libreoffice-7.3.4.2[custom-cflags,lto]: cc1plus: error: unrecognized argument to ‘-flto=’ option: ‘thin’ | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | David Kredba <kredba> |
Component: | Current packages | Assignee: | Gentoo Office Team <office> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | answer2019, faber, sam |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | The build.log file - gzipped |
Description
David Kredba
2022-04-12 19:51:31 UTC
Created attachment 770456 [details]
The build.log file - gzipped
Yeah, thin is for Clang only. It's an upstream bug but tbh the huge RAM usage from gcc + full blown LTO might not be sustainable anyway. Would append-ldflags -Wl,--no-keep-memory help with gcc+bfd? (or gcc+gold) the RAM usage will still be 2x higher than with thinlto, but in theory it should bring it a bit down. After waiting six weeks for this bug to get at least CONFIRMED, i looked into it myself since it buggered me on two different machines. I was building libreoffice with disabled lto via package.env and it still fails with this issue. -custom-cflags fixes the issue for the moment. (In reply to Florian Faber from comment #4) > After waiting six weeks for this bug to get at least CONFIRMED FYI: > * USE flags for app-office/libreoffice: > ... > custom-cflags: Build with user-specified CFLAGS (**unsupported**) - Your own investigation in this case is pretty much required - Don't read anything into confirmed/unconfirmed bug status in general Sure, that's why I didn't complain :) But why-o-why does it build with LTO when I explicitely disable LTO (and have custom-cflags set)? # cat /etc/portage/env/no-lto.conf CFLAGS="${CFLAGS} -fno-lto -fno-use-linker-plugin" CXXFLAGS="${CXXFLAGS} -fno-lto -fno-use-linker-plugin" LDFLAGS="${LDFLAGS} -fno-lto -fno-use-linker-plugin" # grep libreoffice /etc/portage/package.env/no-lto app-office/libreoffice no-lto.conf Anyway, -custom-cflags should help the original poster and anybody else who is looking for this issue. The version 7.3.4.2 fails the same way, Summary updated. (In reply to Florian Faber from comment #6) > Sure, that's why I didn't complain :) > > But why-o-why does it build with LTO when I explicitely disable LTO (and > have custom-cflags set)? > > # cat /etc/portage/env/no-lto.conf > CFLAGS="${CFLAGS} -fno-lto -fno-use-linker-plugin" > CXXFLAGS="${CXXFLAGS} -fno-lto -fno-use-linker-plugin" > LDFLAGS="${LDFLAGS} -fno-lto -fno-use-linker-plugin" > > # grep libreoffice /etc/portage/package.env/no-lto > app-office/libreoffice no-lto.conf > > Anyway, -custom-cflags should help the original poster and anybody else who > is looking for this issue. It's because of: >is-flagq "-flto*" && myeconfargs+=( --enable-lto ) -fno-lto matches that. The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=927204470935f67016aeea6f3c285794def9f0a9 commit 927204470935f67016aeea6f3c285794def9f0a9 Author: Sam James <sam@gentoo.org> AuthorDate: 2022-06-11 07:13:38 +0000 Commit: Sam James <sam@gentoo.org> CommitDate: 2022-06-11 07:14:16 +0000 app-office/libreoffice: fix gcc LTO Closes: https://bugs.gentoo.org/838115 Signed-off-by: Sam James <sam@gentoo.org> app-office/libreoffice/libreoffice-7.3.4.2.ebuild | 4 ++++ app-office/libreoffice/libreoffice-7.3.9999.ebuild | 4 ++++ app-office/libreoffice/libreoffice-9999.ebuild | 4 ++++ 3 files changed, 12 insertions(+) (In reply to Florian Faber from comment #6) > Sure, that's why I didn't complain :) > > But why-o-why does it build with LTO when I explicitely disable LTO (and > have custom-cflags set)? > > # cat /etc/portage/env/no-lto.conf > CFLAGS="${CFLAGS} -fno-lto -fno-use-linker-plugin" > CXXFLAGS="${CXXFLAGS} -fno-lto -fno-use-linker-plugin" > LDFLAGS="${LDFLAGS} -fno-lto -fno-use-linker-plugin" > > # grep libreoffice /etc/portage/package.env/no-lto > app-office/libreoffice no-lto.conf > > Anyway, -custom-cflags should help the original poster and anybody else who > is looking for this issue. Could you file a bug for this issue? We'll probably need to just add USE=lto, I guess. |