I know that using custom-cflags comes with some risks, but since glibc developers don't seem to have any plans to support lto, it would make things easier for users if lto flags were filtered out even with custom-cflags. Reproducible: Always
Created attachment 864660 [details] glibc build log
Sure, can do. But I'd also recommend just not doing that.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=4913f0a16e3cf0065d7e6de18e414882423f7d72 commit 4913f0a16e3cf0065d7e6de18e414882423f7d72 Author: Sam James <sam@gentoo.org> AuthorDate: 2023-06-26 15:31:49 +0000 Commit: Sam James <sam@gentoo.org> CommitDate: 2023-06-26 15:31:49 +0000 sys-libs/glibc: always filter-lto, even w/ USE=custom-cflags Closes: https://bugs.gentoo.org/909193 Signed-off-by: Sam James <sam@gentoo.org> sys-libs/glibc/glibc-2.31-r7.ebuild | 2 +- sys-libs/glibc/glibc-2.32-r8.ebuild | 2 +- sys-libs/glibc/glibc-2.33-r14.ebuild | 2 +- sys-libs/glibc/glibc-2.34-r14.ebuild | 2 +- sys-libs/glibc/glibc-2.35-r11.ebuild | 2 +- sys-libs/glibc/glibc-2.36-r7.ebuild | 2 +- sys-libs/glibc/glibc-2.36-r8.ebuild | 2 +- sys-libs/glibc/glibc-2.37-r2.ebuild | 2 +- sys-libs/glibc/glibc-2.37-r3.ebuild | 2 +- sys-libs/glibc/glibc-9999.ebuild | 2 +- 10 files changed, 10 insertions(+), 10 deletions(-)