blob: 709af32619eb99c3b9fd5d85415d0b0d65205c51 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
|
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>2.3.1. Task Failures</title>
<link rel="stylesheet" type="text/css" href="../book.css">
<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
<link rel="up" href="usingpoky-debugging.html" title="2.3. Debugging Build Failures">
<link rel="prev" href="usingpoky-debugging.html" title="2.3. Debugging Build Failures">
<link rel="next" href="usingpoky-debugging-taskrunning.html" title="2.3.2. Running Specific Tasks">
</head>
<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="2.3.1. Task Failures">
<div class="titlepage"><div><div><h3 class="title">
<a name="usingpoky-debugging-taskfailures"></a>2.3.1. Task Failures</h3></div></div></div>
<p>The log file for shell tasks is available in
<code class="filename">${WORKDIR}/temp/log.do_taskname.pid</code>.
For example, the <code class="filename">compile</code> task for the QEMU minimal image for the x86
machine (<code class="filename">qemux86</code>) might be
<code class="filename">tmp/work/qemux86-poky-linux/core-image-minimal-1.0-r0/temp/log.do_compile.20830</code>.
To see what BitBake runs to generate that log, look at the corresponding
<code class="filename">run.do_taskname.pid</code> file located in the same directory.
</p>
<p>
Presently, the output from Python tasks is sent directly to the console.
</p>
</div></body>
</html>
|
