* How to find Log @ 2012-02-14 8:44 James W. 2012-02-14 9:04 ` Lu, Lianhao 0 siblings, 1 reply; 8+ messages in thread From: James W. @ 2012-02-14 8:44 UTC (permalink / raw) To: yocto How to locate Log file while a error occur. ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: How to find Log 2012-02-14 8:44 How to find Log James W. @ 2012-02-14 9:04 ` Lu, Lianhao 2012-02-14 12:47 ` James Abernathy 0 siblings, 1 reply; 8+ messages in thread From: Lu, Lianhao @ 2012-02-14 9:04 UTC (permalink / raw) To: yocto@yoctoproject.org 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 ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: How to find Log 2012-02-14 9:04 ` Lu, Lianhao @ 2012-02-14 12:47 ` James Abernathy 2012-02-14 13:38 ` Autif Khan 2012-02-14 20:00 ` Scott Garman 0 siblings, 2 replies; 8+ messages in thread From: James Abernathy @ 2012-02-14 12:47 UTC (permalink / raw) To: Lu, Lianhao; +Cc: yocto@yoctoproject.org 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 ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: How to find Log 2012-02-14 12:47 ` James Abernathy @ 2012-02-14 13:38 ` Autif Khan 2012-02-14 20:00 ` Scott Garman 1 sibling, 0 replies; 8+ messages in thread From: Autif Khan @ 2012-02-14 13:38 UTC (permalink / raw) To: James Abernathy; +Cc: yocto@yoctoproject.org >>> 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. ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: How to find Log 2012-02-14 12:47 ` James Abernathy 2012-02-14 13:38 ` Autif Khan @ 2012-02-14 20:00 ` Scott Garman 2012-02-14 20:23 ` jfabernathy 1 sibling, 1 reply; 8+ messages in thread From: Scott Garman @ 2012-02-14 20:00 UTC (permalink / raw) To: yocto 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 ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: How to find Log 2012-02-14 20:00 ` Scott Garman @ 2012-02-14 20:23 ` jfabernathy 2012-02-15 1:20 ` James W. 0 siblings, 1 reply; 8+ messages in thread From: jfabernathy @ 2012-02-14 20:23 UTC (permalink / raw) To: yocto 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 ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: How to find Log 2012-02-14 20:23 ` jfabernathy @ 2012-02-15 1:20 ` James W. 2012-02-15 2:26 ` Cui, Dexuan 0 siblings, 1 reply; 8+ messages in thread From: James W. @ 2012-02-15 1:20 UTC (permalink / raw) To: jfabernathy; +Cc: yocto 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 ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: How to find Log 2012-02-15 1:20 ` James W. @ 2012-02-15 2:26 ` Cui, Dexuan 0 siblings, 0 replies; 8+ messages in thread From: Cui, Dexuan @ 2012-02-15 2:26 UTC (permalink / raw) To: James W., jfabernathy; +Cc: yocto@yoctoproject.org 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 ^ permalink raw reply [flat|nested] 8+ messages in thread
end of thread, other threads:[~2012-02-15 2:26 UTC | newest] Thread overview: 8+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 2012-02-14 8:44 How to find Log James W. 2012-02-14 9:04 ` Lu, Lianhao 2012-02-14 12:47 ` James Abernathy 2012-02-14 13:38 ` Autif Khan 2012-02-14 20:00 ` Scott Garman 2012-02-14 20:23 ` jfabernathy 2012-02-15 1:20 ` James W. 2012-02-15 2:26 ` Cui, Dexuan
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.