ref-manual: Updated a couple FAQ entries.

(From yocto-docs rev: aa445a20ae68d7648a3ccfb76ec42aa5fb95fe01)

Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
Scott Rifenbark 2014-08-04 07:47:50 +03:00 committed by Richard Purdie
parent 0f24d9c569
commit a1550834e2
1 changed files with 5 additions and 5 deletions

View File

@ -710,7 +710,7 @@
and <filename>sysconfdir</filename> that indicate where
executables, libraries, and data reside when a program is
actually run.
And, they are also expected to respect a
They are also expected to respect a
<filename>DESTDIR</filename> environment variable, which is
prepended to all the other variables when the build system
actually installs the files.
@ -742,7 +742,7 @@
where the first is relatively normal and the second is not:
<note>
Due to these lengthy examples, the paths are artificially
broke across lines for readability.
broken across lines for readability.
</note>
<literallayout class='monospaced'>
/home/maxtothemax/poky-bootchart2/build/tmp/work/i586-poky-linux/zlib/
@ -770,7 +770,7 @@
</question>
<answer>
<para>
This situation results when the OpenEmbedded build system does
This situation results when a build system does
not recognize the environment variables supplied to it by
<ulink url='&YOCTO_DOCS_DEV_URL;#bitbake-term'>BitBake</ulink>.
The incident that prompted this FAQ entry involved a Makefile
@ -780,10 +780,10 @@
The makefile's hardcoded default value of "/usr/bin" worked
most of the time, but not for the recipe's
<filename>-native</filename> variant.
Consequently, permissions errors might be caused by a Makefile
For example, permissions errors might be caused by a Makefile
that ignores <filename>DESTDIR</filename> or uses a different
name for that environment variable.
Check the OpenEmbedded build system to see if these kinds of
Check the the build system to see if these kinds of
issues exist.
</para>
</answer>