Go to:
Gentoo Home
Documentation
Forums
Lists
Bugs
Planet
Store
Wiki
Get Gentoo!
Gentoo's Bugzilla – Attachment 217363 Details for
Bug 302129
Gentoo Embedded Handbook: Chapter 1: General Improvement Patches
Home
|
New
–
[Ex]
|
Browse
|
Search
|
Privacy Policy
|
[?]
|
Reports
|
Requests
|
Help
|
New Account
|
Log In
[x]
|
Forgot Password
Login:
[x]
[patch]
In cross-compiling-kernel.xml, small wording fix for kernel source installation, and additional explanation for INSTALL_MOD_PATH
0009-In-cross-compiling-kernel.xml-small-wording-fix-for-.patch (text/plain), 2.01 KB, created by
Jacob Godserv
on 2010-01-25 03:13:21 UTC
(
hide
)
Description:
In cross-compiling-kernel.xml, small wording fix for kernel source installation, and additional explanation for INSTALL_MOD_PATH
Filename:
MIME Type:
Creator:
Jacob Godserv
Created:
2010-01-25 03:13:21 UTC
Size:
2.01 KB
patch
obsolete
>From 374a5388cdc8625d4333b9deead70c1553fb88c2 Mon Sep 17 00:00:00 2001 >From: Jacob Godserv <jacobgodserv@gmail.com> >Date: Thu, 21 Jan 2010 13:19:33 -0500 >Subject: [PATCH 9/9] In cross-compiling-kernel.xml, small wording fix for kernel source installation, and additional explanation for INSTALL_MOD_PATH > >--- > .../embedded/handbook/cross-compiling-kernel.xml | 15 +++++++++++---- > 1 files changed, 11 insertions(+), 4 deletions(-) > >diff --git a/xml/htdocs/proj/en/base/embedded/handbook/cross-compiling-kernel.xml b/xml/htdocs/proj/en/base/embedded/handbook/cross-compiling-kernel.xml >index 39f351e..505052e 100644 >--- a/xml/htdocs/proj/en/base/embedded/handbook/cross-compiling-kernel.xml >+++ b/xml/htdocs/proj/en/base/embedded/handbook/cross-compiling-kernel.xml >@@ -25,10 +25,10 @@ compiling is all the same. > > <p> > You should install the kernel into the sysroot so that if you want to >-cross-compile packages which include kernel modules, the process should be >-transparent. If you don't need such packages, then of course the actual place >-where you build the kernel does not matter. Some people build all their >-kernels in <path>/usr/src/</path> for example. >+cross-compile packages which include kernel modules, the process will be >+transparent. Otherwise, the actual place where you build the kernel does >+not matter. Some people build all their kernels in <path>/usr/src/</path> >+for example. > </p> > > </body> >@@ -64,6 +64,13 @@ chop off that trailing <c>gcc</c> and that's what you use: > </p> > > <p> >+There is an additional variable, <c>INSTALL_MOD_PATH</c>, which defines where >+the <path>/lib</path> directory will be created, and all the modules stored. >+While you don't have to transfer the kernel sources to your target device, >+if you build any modules, you'll want this directory. >+</p> >+ >+<p> > There are really two ways you can setup the system. You can modify the > toplevel Makefile or you can override the relevant variables on the command > line. How you do it is largely a matter of taste, so we'll cover both. Pick >-- >1.6.4.4 >
You cannot view the attachment while viewing its details because your browser does not support IFRAMEs.
View the attachment on a separate page
.
View Attachment As Diff
View Attachment As Raw
Actions:
View
|
Diff
Attachments on
bug 302129
:
217350
|
217352
|
217354
|
217356
|
217358
|
217359
|
217360
|
217361
|
217363
|
240005