Re: [gentoo-portage-dev] ebuild --debug takes forever when FEATURES contains keeptemp: detects QA warnings in build.log

[Amit Dor-Shifer]

I think it's not that I'm getting any specific warning, but rather that 
the warnings get quoted in build.log in debug mode:

amit0 ~ $ cat 
/usr/portage/local/myebuilds/test/test-mkdir/test-mkdir-1.0.ebuild
SRC_URI=""
KEYWORDS="amd64"
# Make sure you have the SLOT variable in the ebuild. If you don't plan 
to use it, don't remove it. Put in SLOT="0".
SLOT="0"
# You must (according to the Gentoo ebuild HOWTO) include the IUSE 
variable even if there are no USE flags in use.
IUSE=""

DEPEND=""
RDEPEND="${DEPEND}"

src_install()
{
    diropts -m0777
        dodir /tmp/test-mkdir
}

amit0 ~ $ rm -fr /var/tmp/portage/test/test-mkdir-1.0/temp/
amit0 ~ $ time (ebuild --debug 
/usr/portage/local/myebuilds/test/test-mkdir/test-mkdir-1.0.ebuild >& 
/tmp/bla install)

real    0m3.456s
user    0m2.527s
sys     0m1.002s
amit0 ~ $ grep -qs ': warning:' 
/var/tmp/portage/test/test-mkdir-1.0/temp/build.log
amit0 ~ $ echo $?
0
amit0 ~ $ grep -m 3 ': warning:' 
/var/tmp/portage/test/test-mkdir-1.0/temp/build.log
+ msgs=(": warning: dereferencing type-punned pointer will break 
strict-aliasing rules$" ": warning: implicit declaration of function " 
": warning: incompatible implicit declaration of built-in function " ": 
warning: is used uninitialized in this function$" ": warning: 
comparisons like X<=Y<=Z do not have their mathematical meaning$" ": 
warning: null argument where non-null required ")
+ [[ -n : warning: dereferencing type-punned pointer will break 
strict-aliasing rules$ ]]
+ m=': warning: dereferencing type-punned pointer will break 
strict-aliasing rules$'
amit0 ~ $ time (ebuild --debug 
/usr/portage/local/myebuilds/test/test-mkdir/test-mkdir-1.0.ebuild >& 
/tmp/bla install)
# preemting ebuild after a ~30 sec. hang

^C^C
real    0m31.257s
user    0m22.578s
sys     0m8.949s

Amit

Zac Medico wrote:
> Amit Dor-Shifer wrote:
>
>> Hi.
>> When I'm executing ebuild --debug /path/to/my/ebuild.ebuild >&
>> /some/file, ebuild keeps dumping QA warnings to /some/file. I think its
>> because its grepping for ": warning :" in build.log, and such messages
>> are quoted into build.log because of the use of --debug.
>>
>
> Maybe we just need to disable that QA check when --debug is enabled.
> What specific QA warnings are you getting?
>