All of lore.kernel.org
 help / color / mirror / Atom feed
From: jfabernathy <jfabernathy@gmail.com>
To: yocto@yoctoproject.org
Subject: Re: How to find Log
Date: Tue, 14 Feb 2012 15:23:56 -0500	[thread overview]
Message-ID: <4F3AC2DC.20001@gmail.com> (raw)
In-Reply-To: <4F3ABD54.7060507@intel.com>

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




  reply	other threads:[~2012-02-14 20:23 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
2012-02-15  1:20         ` James W.
2012-02-15  2:26           ` Cui, Dexuan

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4F3AC2DC.20001@gmail.com \
    --to=jfabernathy@gmail.com \
    --cc=yocto@yoctoproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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.