thank you for your help .
so ,i think log mechanism is very important for such a large build system.
We may should do better on this point.
On Wed, Feb 15, 2012 at 4:23 AM, jfabernathy <jfaberna...@gmail.com> wrote:
> On 02/14/2012 03:00 PM, Scott Garman wrote:
>>
>> On 02/14/2012 04:47 AM, James Abernathy wrote:
>>>
>>>
>>> On Feb 14, 2012, at 4:04 AM, Lu, Lianhao wrote:
>>>
>>>> James W. wrote on 2012-02-14:
>>>>>
>>>>> How to locate Log file while a error occur.
>>>>
>>>>
>>>> It's under the directory ${WORKDIR}/temp/. Actually when an error
>>>> occurs, you can find the specific log file in the output, something like.
>>>>
>>>> ERROR: Logfile of failure stored in:
>>>>
>>>> /intel/poky/builds/toolchain/tmp/work-shared/gcc-4.6.2+svnr181430-r22/temp/log.do_patch.15156
>>>>
>>>> Best Regards,
>>>> Lianhao
>>>>
>>>>
>>> I have a similar questions. If the error occurs and the console log
>>> information scrolls too far to get back to, how do I find the error log file
>>> then? I know what directory all the logs will be, but is there an easy way
>>> to find the one with the error??
>>
>>
>> In Poky master, we now save the output from bitbake in cooker.log files,
>> kept under build/tmp/. This will be a feature of our upcoming 1.2 release of
>> Yocto.
>>
>> Scott
>>
> Found them! great idea!
>
> Jim A
>
>
>
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
_______________________________________________
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
