On Tue, 2011-04-19 at 05:00 +0100, Ben Hutchings wrote: [...] > > I've attempted to document this, since it currently does not appear to be. > > See patch to kernel handbook below. I'm sure I'm made errors, so > > corrections, please. > [...] > > Thanks. I'll apply something like that, but change 'is necessary' to > 'may be necessary. I ended up making some more changes and included the new text in the 'applying patches' section. Do you think this covers it? Ben. --- a/chapter-common-tasks.sgml +++ b/chapter-common-tasks.sgml @@ -90,7 +90,7 @@ $ /usr/src/kernel-patches/all/2.6.18/apply/debian 2.6.18-1 </p> </sect1> <sect1> - <heading>Applying patches</heading> + <heading>Applying patches or configuration changes</heading> <p> It is possible to apply extra patches to the source before starting the build. First, you should apply the existing @@ -104,6 +104,27 @@ $ fakeroot debian/rules source (featuresets added). You should apply the extra patches in the appropriate subdirectory. </p> + <p> + To change the configuration before building, for example + for the 686-bigmem flavour on i386, run the commands: + <example> +$ fakeroot make -f debian/rules.gen setup_i386_none_686-bigmem +$ make -C debian/build/build_i386_none_686-bigmem menuconfig + </example> + </p> + <p> + If the patches or configuration changes alter type + definitions for the kernel, the kernel ABI will change and + you must then change the ABI name. This is the part after + the upstream version in package names and in the output of + <tt>uname -r</tt>. It is defined by the <tt>abiname</tt> + in <tt>debian/config/defines</tt>. For example, + <tt>abiname: custom1.0</tt>. Then run the command + <example> +$ fakeroot debian/rules debian/control-real + </example> + to regenerate the package definitions for this ABI name. + </p> </sect1> <sect1> <heading>Building many packages</heading> --- END --- -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse.
Description: This is a digitally signed message part