Arch: Difference between revisions
| Line 26: | Line 26: | ||
</pre> | </pre> | ||
Each time you build a new kernel, the preserved config will be copied into the source directory. <tt>make oldconfig</tt> will give you the opportunity to configure any new options. <tt>make menuconfig</tt> will then allow you to modify the kernel config. If this kernel config ends up different from the preserved config (it always will at least once, due to the version changing), the process will abort. Run <tt>cp src/archlinux-linux/.config ../config</tt> to preserve the new config. Once the config is no longer changing, the process can continue. | Each time you build a new kernel, the preserved config will be copied into the source directory. <tt>make oldconfig</tt> will give you the opportunity to configure any new options. <tt>make menuconfig</tt> will then allow you to modify the kernel config. If this kernel config ends up different from the preserved config (it always will at least once, due to the version changing), the process will abort. Run <tt>cp src/archlinux-linux/.config ../config</tt> to preserve the new config. Once the config is no longer changing, the process can continue. | ||
If you wish to avoid the lengthy build of documentation (it will otherwise dominate your total build time), remove <tt>$pkgbase-docs</tt> from the <tt>pkgname</tt> array. | |||
===New kernel process=== | ===New kernel process=== | ||
* Edit <tt>PKGBUILD</tt> and change <tt>_pkgver</tt>, usually to a string of the form <tt>MAJOR.MINOR.PATCH.arch1</tt> | * Edit <tt>PKGBUILD</tt> and change <tt>_pkgver</tt>, usually to a string of the form <tt>MAJOR.MINOR.PATCH.arch1</tt> | ||