ref-manual: Edits to some FAQ entries.
Minor review edits from Max. (From yocto-docs rev: c70de50aeceda60db92c5e488bde8fe910eaeba1) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
parent
a20e75f45b
commit
20581875f2
|
@ -754,7 +754,7 @@
|
|||
</literallayout>
|
||||
Even if the paths look unusual, they both are correct -
|
||||
the first for a target and the second for a native recipe.
|
||||
This paths are a consequence of the
|
||||
These paths are a consequence of the
|
||||
<filename>DESTDIR</filename> mechanism and while they
|
||||
appear strange, they are correct and in practice very effective.
|
||||
</para>
|
||||
|
@ -783,9 +783,9 @@
|
|||
The makefile's hardcoded default value of "/usr/bin" worked
|
||||
most of the time, but not for the recipe's
|
||||
<filename>-native</filename> variant.
|
||||
For example, permissions errors might be caused by a Makefile
|
||||
that ignores <filename>DESTDIR</filename> or uses a different
|
||||
name for that environment variable.
|
||||
For another 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 the build system to see if these kinds of
|
||||
issues exist.
|
||||
</para>
|
||||
|
|
Loading…
Reference in New Issue