summaryrefslogtreecommitdiffstats
path: root/documentation/poky-ref-manual/usingpoky.xml
diff options
context:
space:
mode:
authorScott Rifenbark <scott.m.rifenbark@intel.com>2011-08-29 07:30:04 -0700
committerRichard Purdie <richard.purdie@linuxfoundation.org>2011-08-30 17:27:39 +0100
commitfdbc652b084a41097158a96e6720f16b6cae7d3a (patch)
tree8b92aad0e9b2a64300945957e0070547cb6a4455 /documentation/poky-ref-manual/usingpoky.xml
parent4a394120869a395d702761e8cab262e43eed0542 (diff)
downloadpoky-fdbc652b084a41097158a96e6720f16b6cae7d3a.tar.gz
documentation/poky-ref-manual: Removed "spitz" machine example.
This machine is out of date. I replaced both occurences with "qemux86", which is more relevant to YP. (From yocto-docs rev: 8fe6feccc25f594a444b5177d1192899b3cbdd9c) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'documentation/poky-ref-manual/usingpoky.xml')
-rw-r--r--documentation/poky-ref-manual/usingpoky.xml8
1 files changed, 4 insertions, 4 deletions
diff --git a/documentation/poky-ref-manual/usingpoky.xml b/documentation/poky-ref-manual/usingpoky.xml
index 976f7f4c11..97fb558432 100644
--- a/documentation/poky-ref-manual/usingpoky.xml
+++ b/documentation/poky-ref-manual/usingpoky.xml
@@ -247,11 +247,11 @@
247 247
248 <para>The log file for shell tasks is available in 248 <para>The log file for shell tasks is available in
249 <filename>${WORKDIR}/temp/log.do_taskname.pid</filename>. 249 <filename>${WORKDIR}/temp/log.do_taskname.pid</filename>.
250 For example, the <filename>compile</filename> task of busybox 1.01 on the ARM spitz 250 For example, the <filename>compile</filename> task for the QEMU minimal image for the x86
251 machine might be 251 machine (<filename>qemux86</filename>) might be
252 <filename>tmp/work/armv5te-poky-linux-gnueabi/busybox-1.01/temp/log.do_compile.1234</filename>. 252 <filename>tmp/work/qemux86-poky-linux/core-image-minimal-1.0-r0/temp/log.do_compile.20830</filename>.
253 To see what BitBake runs to generate that log, look at the corresponding 253 To see what BitBake runs to generate that log, look at the corresponding
254 <filename>run.do_taskname.pid </filename> file located in the same directory. 254 <filename>run.do_taskname.pid</filename> file located in the same directory.
255 </para> 255 </para>
256 256
257 <para> 257 <para>