This shows you the differences between two versions of the page.
Owl:kernel-build [2011/04/01 17:45] solar minor edits to "Non-RPM'ed kernel build" |
Owl:kernel-build [2011/08/13 11:09] (current) solar documented just how kernel RPM build fails when the version strings are not in sync |
||
---|---|---|---|
Line 37: | Line 37: | ||
</file> | </file> | ||
- | It is sensible to make minor edits to ''dot-config-i686'' and/or ''dot-config-x86_64'', but please be sure to also adjust the package revision number by editing ''EXTRAVERSION'' in the ''*-owl.diff'' patch file and ''Release'' in ''kernel.spec'' (these must be kept in sync, or the build will fail). For example, you might change ''EXTRAVERSION'' from ''-238.5.1.el5.028stab085.2.owl3'' to ''-238.5.1.el5.028stab085.2.owl3.local1'' and ''Release'' from ''%ovzversion.owl3'' to ''%ovzversion.owl3.local1'' (instead of ''local'', you may use your nickname or your network/company/project name). This is to avoid confusion with Owl official kernel revisions and to allow you to install your RPMs alongside the official ones. | + | It is sensible to make minor edits to ''dot-config-i686'' and/or ''dot-config-x86_64'', but please be sure to also adjust the package revision number by editing ''EXTRAVERSION'' in the ''*-owl.diff'' patch file and ''Release'' in ''kernel.spec'' (these must be kept in sync, or the build will fail with ''File not found: /usr/src/world/rpm-work-1/buildroot/lib/modules/2.6.18-...'' errors). For example, you might change ''EXTRAVERSION'' from ''-238.5.1.el5.028stab085.2.owl3'' to ''-238.5.1.el5.028stab085.2.owl3.local1'' and ''Release'' from ''%ovzversion.owl3'' to ''%ovzversion.owl3.local1'' (instead of ''local'', you may use your nickname or your network/company/project name). This is to avoid confusion with Owl official kernel revisions and to allow you to install your RPMs alongside the official ones. |
For non-trivial kernel configuration changes (or just to be safe), you may prefer to do a non-RPM'ed kernel build (then either actually use the resulting kernel or just roll your build-tested changes back into the native tree for building an RPM package). | For non-trivial kernel configuration changes (or just to be safe), you may prefer to do a non-RPM'ed kernel build (then either actually use the resulting kernel or just roll your build-tested changes back into the native tree for building an RPM package). |