Make kpkg patch

It must be at least two characters long and must start with an alphanumeric character. This is only relevant for the buildpackage target. Should be a small integer, if used. Please look at a Linux kernel Makefile for details. Please note that although we take care of the list of current kernel configuration contained in the file. This target should not be combined with other targets, since make-kpkg reads in all data before running any target, so the subsequent targets shall be run with the old data, which may not be what you want.

Please note that by default the clean target is not run as root, whic works fine of the command fakeroot was used. However, if previously the build was done using sudo, you need to run make-kpkg clean also under sudo.

However, this requires make-kpkg to be run as root or fakeroot , since --rootcmd will not work. However, this also requires make-kpkg to be run as root or fakeroot , since --rootcmd will not work. XX, so people may take any action they see fit remove arch trees, prune version control directories, find. This has no effect on anything other than the kernel sources that are being packaged -- if the script operates on the current directory and its children, the original source tree should remain intact.

They should point to executables, then that executable shall be run from the temporary top directory of the kernel headers and documentation just before packaging respectively, so people may take any action they see fit.

This also has no effect on anything other than the sources that are being packaged. Please note that if module signatures are enable in the kernel configuration the corresponding image package will not have modules with the debugging link pointing to these debugging symbol files.

In order to turn on debugging links for modules in the image package you need to turn off module signatures. If there is no. If the kernel configuration file has enabled support for modules, modules will be created and installed. If module signatures are not enabled, the resulting modules will have a link to the location of the debugging symbols file for the module, usually installed by the debug package.

If the file. Also, please note that if there are any scripts in. Please see the documentation about hooks in kernel-img. These hooks are variables that can be pointed by the local sysadmin to scripts that add or remove a line from the grub menu list at kernel image install and remove times. Apart from hook variables that the local admin may set, there are a set of directories where packages, or the local admin, may drop in script files.

If they exists, the kernel-image package shall run a run-parts program over the directory including the versioned one , giving the version being installed or removed as an argument, in the corresponding phase of installation or removal. These scripts shall be called with two arguments, the first being the version of the kernel image, and the second argument being the location of the kernel image itself.

No further changes may be made. Toggle useless messages. View this report as an mbox folder , status mbox , maintainer mbox. Report forwarded to debian-bugs-dist lists. Mon, 19 Feb GMT full text , mbox , link. Message 5 received at submit bugs. Information forwarded to debian-bugs-dist lists.

Wed, 07 Mar GMT full text , mbox , link. Message 10 received at bugs. Sat, 10 Mar GMT full text , mbox , link. Message 15 received at bugs. Mon, 12 Mar GMT full text , mbox , link. Message 20 received at bugs. Thu, 17 May GMT full text , mbox , link. If there is no such file, it behaves like make config , a text interface that asks all questions hundreds of them one a time. If the. Compiling and Building the Package.

If you have already compiled once in the directory and wish to recompile with new sources, you must run fakeroot make-kpkg clean. Additionally, this allows generating a package with a new name different --append-to-version setting.

TIP Kernel package headers. It is recommended to edit this file with correct information if you wish to publish your kernel package. Once the kernel configuration is ready, the make-kpkg command provided by Debian compiles the kernel, then generates the corresponding Debian package or packages. Just like make , make-kpkg takes the name of a target to execute as an argument: kernel-image generates a compiled kernel package, kernel-doc a package containing the documentation included with the kernel, kernel-headers a package of kernel header files.

Debian uses certain suffixes to identify standard kernels, compiled specifically for a given processor, or with certain options , , bigmem , -amd64 , -vserver , -vserverbigmem , -openvz , -xen These suffixes are best avoided for local packages, so that they can be easily recognized from official packages issued by the Debian project. The make-kpkg program performs actions normally restricted to the root user when creating the Debian package; however, it can be tricked into working under a normal user's identity, with fakeroot see sidebar TOOL fakeroot.

Compiling External Modules. Some modules are maintained outside of the official Linux kernel. To use them, they must be compiled alongside the matching kernel. A number of common third party modules are provided by Debian in dedicated packages: lustre-source for the Lustre filesystem, qc-usb-source for the drivers for some USB webcams Logitech QuickCam Express , etc.

However, a complete list isn't particularly useful since there is no particular reason for compiling external modules except when you know you need it. In such cases, the device's documentation will typically detail the specific module s it needs to function under Linux.

For example, let's look at the qc-usb-source package: after installation, a. These sources must then be extracted to the working directory:. NOTE Save the settings. When using the make-kpkg modules-image command, it is important to use the same --append-to-version setting used in the previous use of the command probably make-kpkg kernel-image , since its value affects the name of the directory in which the modules are installed, which must correspond to the kernel version.

Note that make-kpkg must still be invoked from the kernel sources directory, even when compiling external modules located in other directories. By default, it tries to create the packages for all the external modules that you extracted at this location. The --added-modules option allows to explicitly choose the external modules to compile. To include more than one, separate them with a comma. TIP Automating the process.

The whole process can be automated with module-assistant. This package was specifically designed to install the required tools and packages, compile an external module, and install it.