commit: ff567fa404228cb9a302b379e88f553497ea38d6 Author: Sam James <sam <AT> gentoo <DOT> org> AuthorDate: Mon Jan 24 14:36:50 2022 +0000 Commit: Sam James <sam <AT> gentoo <DOT> org> CommitDate: Mon Jan 24 14:36:50 2022 +0000 URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=ff567fa4
profiles/base: mask sys-libs/glibc[custom-cflags] It's far too dangerous and leads to both build-time failures for glibc itself and runtime crashes for other programs depending on the flags used. Mask it so people have to actually unmask it in order to footgun themselves. (USE=custom-cflags in make.conf may or may not be advisible (rather than setting it per-package in package.use), but it's generally not going to be as dangerous for most/all packages as it is for glibc, so it makes sense to make it harder to do it for just glibc.) Signed-off-by: Sam James <sam <AT> gentoo.org> profiles/base/package.use.mask | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/profiles/base/package.use.mask b/profiles/base/package.use.mask index 8bb3a942ab06..67d7c4ca7ca1 100644 --- a/profiles/base/package.use.mask +++ b/profiles/base/package.use.mask @@ -6,6 +6,13 @@ # This file is only for generic masks. For arch-specific masks (i.e. # mask everywhere, unmask on arch/*) use arch/base. +# Sam James <[email protected]> (2021-01-24) +# USE=custom-cflags is _particularly_ dangerous on sys-libs/glibc and +# can result in not just build-time failures for glibc itself, but +# runtime crashes. The effect of using USE=custom-cflags globally in make.conf +# isn't the same as it is for just glibc specifically. +sys-libs/glibc custom-cflags + # Sam James <[email protected]> (2022-01-23) # Java bindings are broken with OpenJDK 11+ and we're not # aware of any consumers. bug #713866
