mirror of
https://git.yoctoproject.org/poky
synced 2026-05-02 18:32:15 +02:00
documentation: Rename of poky-ref-manual folder to ref-manual.
Changing the folder that holds the YP Reference Manual to be "ref-manual". This will help with confustion over the manual's intended purpose. (From yocto-docs rev: 1106442964b5080cb0b6b3bd3af32e9407c0f7c1) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
committed by
Richard Purdie
parent
af19d889ef
commit
ed0a240e16
@@ -0,0 +1,27 @@
|
||||
<html>
|
||||
<head>
|
||||
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
|
||||
<title>2.3.1.<2E>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.<2E>Debugging Build Failures">
|
||||
<link rel="prev" href="usingpoky-debugging.html" title="2.3.<2E>Debugging Build Failures">
|
||||
<link rel="next" href="usingpoky-debugging-taskrunning.html" title="2.3.2.<2E>Running Specific Tasks">
|
||||
</head>
|
||||
<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="2.3.1.<2E>Task Failures">
|
||||
<div class="titlepage"><div><div><h3 class="title">
|
||||
<a name="usingpoky-debugging-taskfailures"></a>2.3.1.<2E>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>
|
||||
Reference in New Issue
Block a user