27 lines
1.5 KiB
HTML
27 lines
1.5 KiB
HTML
<html>
|
||
<head>
|
||
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
|
||
<title>2.3. Debugging Build 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.html" title="Chapter 2. Using the Yocto Project">
|
||
<link rel="prev" href="usingpoky-install.html" title="2.2. Installing and Using the Result">
|
||
<link rel="next" href="usingpoky-debugging-taskfailures.html" title="2.3.1. Task Failures">
|
||
</head>
|
||
<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="2.3. Debugging Build Failures">
|
||
<div class="titlepage"><div><div><h2 class="title" style="clear: both">
|
||
<a name="usingpoky-debugging"></a>2.3. Debugging Build Failures</h2></div></div></div>
|
||
<p>
|
||
The exact method for debugging build failures depends on the nature of the
|
||
problem and on the system's area from which the bug originates.
|
||
Standard debugging practices such as comparison against the last
|
||
known working version with examination of the changes and the re-application of steps
|
||
to identify the one causing the problem are
|
||
valid for the Yocto Project just as they are for any other system.
|
||
Even though it is impossible to detail every possible potential failure,
|
||
this section provides some general tips to aid in debugging.
|
||
</p>
|
||
</div></body>
|
||
</html>
|