How to find Log

How to find Log

[James W.]

How to locate Log file while a error occur.

Re: How to find Log

[Lu, Lianhao]

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

Re: How to find Log

[James Abernathy]

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??

Jim A

> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto

Re: How to find Log

[Autif Khan]

>>> 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??

This is true - I set my terminal scrollback to 9999 lines to avoid this.

May be that error line should be displayed both before and after the log.

I will see if I can find where this happens and create a patch. But
that will have to wait until after ELC 2012.

Re: How to find Log

[Scott Garman]

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

-- 
Scott Garman
Embedded Linux Engineer - Yocto Project
Intel Open Source Technology Center

Re: How to find Log

[jfabernathy]

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

Re: How to find Log

[James W.]

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 <jfabernathy@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

Re: How to find Log

[Cui, Dexuan]

James W. wrote on 2012-02-15:
> 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.
I think the utility "tee" works pretty fine for me , e.g., I use something like
$ bitbake core-image-minimal | tee my.log.

Thanks,
-- Dexuan