I'm using the profile
Code: Select all
[12] default/linux/amd64/17.1/desktop/systemd (stable)
Code: Select all
[12] default/linux/amd64/17.1/desktop/systemd (stable)
Code: Select all
# Sam James <sam@gentoo.org> (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
sys-devel/gcc custom-cflags
Code: Select all
mkdir -p /etc/portage/profile/use.mask
## nano /etc/portage/profile/use.mask/glibc
-custom-cflags
##
Code: Select all
USE="custom-cflags"
Thanks for the heads-up!fedeliallalinea wrote:You can unmasking use flag with package.use, but at your own risk because if it's masked there is a reason .

In this way you unmask use flag globally, maybe is better to use package.use.mask to specify only one package (sorry in my previous post I wrongly linked the file to unmask the use flags).EliasJonsson wrote:Thanks, tried that but it still didn't work as the use flag was masked. Had to the unmask the use flag by:Code: Select all
mkdir -p /etc/portage/profile/use.mask ## nano /etc/portage/profile/use.mask/glibc -custom-cflags ##