I am playing with adding packages in a monster rootfs. Bitbake tries to be helpful when putting together the rootfs and tells me: WARNING: log_check: There is a warn message in the logfile WARNING: log_check: Matched keyword: [warn] … and an additional line about the warning. It does NOT tell me however which logfile or even which recipe caused that warning, so I have to manually grep through my whole work directory to figure out which recipe caused the warning. This seems to be a totally useless extra step. bitbake SHOULD tell me in which recipe and logfile the warning occurred so that I don't have to grep through Gigabytes to find the issue.
The warning messages shown are a start but definitely need something more to locate exactly where the problem is and to test a fix correctly. Right now I am not entirely sure what to run to reproduce this. Need a bigger output of this command, the configuration for this image and the packages added. Any logs for this that you can attach are welcomed too.
You haven't specified which version you're using, but I'd guess it's an older version before we added the recipe and task name to every warning/error message printed, so that part should be solved. In any event, you will find this definitely comes from the do_rootfs log of the image you're building (though I guess you may possibly be building more than one image at once). For Humberto's benefit - I am working on tidying up the log_check double warning issue under bug 8223; I do have a set of patches for that already.
The problem was observed in an NXP/Freescale version of a poky 1.8.1 setup per poky/meta-yocto/conf/distro/poky.conf The offending log message is generated in _log_check_warn() in poky/meta/lib/oe/rootfs.py. The problem is that it tells you that "something" happened, but doesn't give you any indication which package caused it or how to figure out which package caused it. it doesn#t even tell you which logfile caused it. I see it has been fixed in a poky 2.0 setup.
(In reply to comment #3) > I see it has been fixed in a poky 2.0 setup. Good news. In case you know the commit ID that fixed it, please include it in a comment. Leo