diff --git a/documentation/ref-manual/usingpoky.xml b/documentation/ref-manual/usingpoky.xml
index 99912ff14e..f70c1966e1 100644
--- a/documentation/ref-manual/usingpoky.xml
+++ b/documentation/ref-manual/usingpoky.xml
@@ -163,9 +163,8 @@
BitBake User Manual.
-
-
- Task Failures
+
+ Viewing Logs from Failed Tasks
The log file for shell tasks is available in
${WORKDIR}/temp/log.do_taskname.pid.
@@ -183,6 +182,58 @@
+
+ Viewing Variable Values
+
+ BitBake's -e option is used to display
+ variable values after parsing.
+ The following command displays the variable values after the
+ configuration files (i.e. local.conf,
+ bblayers.conf, and so forth) have been
+ parsed:
+
+ $ bitbake -e
+
+ The following command displays variable values after a specific
+ recipe has been parsed.
+ The variables include those from the configuration as well:
+
+ $ bitbake -e recipename
+
+
+ Each recipe has its own private set of variables (datastore).
+ Internally, after parsing the configuration, a copy of the
+ resulting datastore is made prior to parsing each recipe.
+ This copying implies that variables set in one recipe will
+ not be visible to other recipes.
+
+ Likewise, each task within a recipe gets a private
+ datastore based on the recipe datastore, which means that
+ variables set within one task will not be visible to
+ other tasks.
+
+
+
+
+ In the output of bitbake -e, each variable is
+ preceded by a description of how the variable got its value,
+ including temporary values that were later overriden.
+ This description also includes variable flags (varflags) set on
+ the variable.
+ The output can be very helpful during debugging.
+
+
+
+ Variables that are exported to the environment are preceded by
+ export in the output of
+ bitbake -e.
+ See the following example:
+
+ export CC="i586-poky-linux-gcc -m32 -march=i586 --sysroot=/home/ulf/poky/build/tmp/sysroots/qemux86"
+
+
+
+
Running Specific Tasks
@@ -319,7 +370,6 @@
-
Dependency Graphs
@@ -410,23 +460,6 @@
-
- Variables
-
- You can use the -e BitBake option to
- display the parsing environment for a configuration.
- The following displays the general parsing environment:
-
- $ bitbake -e
-
- This next example shows the parsing environment for a specific
- recipe:
-
- $ bitbake -e recipename
-
-
-
-
Recipe Logging Mechanisms