Created attachment 686925 [details] ebuild environment file Building Gentoo from scratch in a clean VM fails when portage tries to build =dev/vcs-2.26.2 (current package). The bug was identified. The environment file declares the Makefile variable QUIET as "false" (l. 226). This in turn causes a bug in work/git-2.26.2/templates/Makefile, l.36, target boilerplates.made: $(QUIET)umask 022 (...) which is resolved as: falseumask 022 This is caused by the fact that the ebuild environment file wrongly masks and prevails over the internal Makefile conditional define: ifdef V QUIET = @ endif Proposed solution: change the ebuild environment file at line 226: - QUIET="false" + QUIET="" Currently this looks like a major bug as git is overly ubiquitous in developers' platforms.
Created attachment 686928 [details] emerge_info
Created attachment 686931 [details] emerge -pqv
Created attachment 686934 [details] build log
This sounds strange, I see no reference to QUIET in the env file on this end, plus 2.26.2 been stable since April 2020. fwiw I can reproduce if I "QUIET=false emerge -1 dev-vcs/git" which I see as not much different than doing CC=false, please verify that your environment is clean and/or try to see where this is coming from, e.g. grep -r QUIET /etc/portage
To clarify, the environment file is just reflecting what you have set (rather than setting it). That means it would be there if QUIET=false was exported before running emerge.
Correct. Although quite clean, the environment had a QUIET=false export before building started. Ideally it would be preferable to protect git Makefiles against such scoping issues but this is more a job for git code maintainers than for Gentoo's. Issue solved. Thanks.
