diff options
author | Scott Rifenbark <scott.m.rifenbark@intel.com> | 2012-05-30 13:14:28 -0700 |
---|---|---|
committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2012-05-31 21:16:55 +0100 |
commit | 69536d42f1a5a532b6aeae04b59511abfeaeaedc (patch) | |
tree | 26c17f78d5dc0c8e783146e3df52309d3623dfe7 /documentation | |
parent | a23636b6aac5fc3336b548535ae1fd7b46b89dfc (diff) | |
download | poky-69536d42f1a5a532b6aeae04b59511abfeaeaedc.tar.gz |
documentation/dev-manual/dev-manual-kernel-appendix.xml: Updated Note
Updated a note to include information about what happens if you do a
kernel build and have your machine compatible with every possible
kernel. This extra information is useful for rational.
Reported-by: Bruce Ashfield <bruce.ashfield@windriver.com>
(From yocto-docs rev: e631ec44be49d456add6a53ff3db89016d187370)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'documentation')
-rw-r--r-- | documentation/dev-manual/dev-manual-kernel-appendix.xml | 12 |
1 files changed, 8 insertions, 4 deletions
diff --git a/documentation/dev-manual/dev-manual-kernel-appendix.xml b/documentation/dev-manual/dev-manual-kernel-appendix.xml index db6629da2f..6b87eaa427 100644 --- a/documentation/dev-manual/dev-manual-kernel-appendix.xml +++ b/documentation/dev-manual/dev-manual-kernel-appendix.xml | |||
@@ -442,15 +442,19 @@ | |||
442 | </para> | 442 | </para> |
443 | 443 | ||
444 | <note> | 444 | <note> |
445 | Before attempting to build the modified kernel, there is one more set of changes you | 445 | <para>Before attempting to build the modified kernel, there is one more set of changes you |
446 | need to make in the <filename>meta-kernel-dev</filename> layer. | 446 | need to make in the <filename>meta-kernel-dev</filename> layer. |
447 | Because all the kernel <filename>.bbappend</filename> files are parsed during the | 447 | Because all the kernel <filename>.bbappend</filename> files are parsed during the |
448 | build process regardless of whether you are using them or not, you should either | 448 | build process regardless of whether you are using them or not, you should either |
449 | comment out the <filename>COMPATIBLE_MACHINE</filename> statements in all | 449 | comment out the <filename>COMPATIBLE_MACHINE</filename> statements in all |
450 | unused <filename>.bbappend</filename> files. | 450 | unused <filename>.bbappend</filename> files, or simply remove (or rename) all the files |
451 | Alternatively, you can simply remove all the files | ||
452 | except the one your are using for the build | 451 | except the one your are using for the build |
453 | (i.e. <filename>linux-yocto_3.2.bbappend</filename> in this example). | 452 | (i.e. <filename>linux-yocto_3.2.bbappend</filename> in this example).</para> |
453 | <para>If you do not make one of these two adjustments, your machine will be compatible | ||
454 | with all the kernel recipes in the <filename>meta-kernel-dev</filename> layer. | ||
455 | When your machine is comapatible with all the kernel recipes, the build attempts | ||
456 | to build all kernels in the layer. | ||
457 | You could end up with build errors blocking your work.</para> | ||
454 | </note> | 458 | </note> |
455 | </section> | 459 | </section> |
456 | 460 | ||