make-kpkg question about version
I just built a new kernel from kenel-sources, plus I built the ls-sensors modules So, to build the kernel and modules I used: $ fakeroot make-kpkg --revision=custom.1.0 --append_to_version=-xfs-athlon kernel_image $ fakeroot make-kpkg --revision=custom.1.0 --append_to_version=-xfs-athlon modules_image If I just used: $ fakeroot make-kpkg modules_image it complains about version mismatch. Now, when I want to run clean: $ make-kpkg clean modules_clean I get: The changelog says we are creating 2.4.21-xfs-athlon, but I thought the version is 2.4.21 make: *** [stamp-debian] Error 1 Which changelog do I need to update? -- Bill Moseley [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: make-kpkg question about version
Bill Moseley wrote: $ fakeroot make-kpkg --revision=custom.1.0 --append_to_version=-xfs-athlon kernel_image $ fakeroot make-kpkg --revision=custom.1.0 --append_to_version=-xfs-athlon modules_image Now, when I want to run clean: $ make-kpkg clean modules_clean I get: The changelog says we are creating 2.4.21-xfs-athlon, but I thought the version is 2.4.21 make: *** [stamp-debian] Error 1 Run the 'clean' target by itself. make-kpkg does not seem to know how to combine that target with other targets. make-kpkg clean make-kpkg modules_clean Bob pgp0.pgp Description: PGP signature
make-kpkg question
Hello! (and Happy New Year!) I run sid here and I usually buildd my kernels in mmy home directory; to build lm-sensors and i2c without becoming root, I decided to unpack the sources in ~/Linux/kernel/modules, and use that directory for MODULE_LOC. The kernel and modules build fine (and I don't have to su or sudo), but although make-kpkg finds the right directories to clean, modules_clean fails (because it calls kdist_clean). To do that, I have to go to each module tree and run debian/rules clean Is this a problem with kernel-package? (already checked the BTS, and it's not there) Or did I unpack the modules in the wrong way? I should use apt-get source i2c lm-sensors (or apt-get source i2c-source lm-sensors-source in the modules directory right?) Thanks, J. $ fakeroot make-kpkg modules_clean test -f stamp-debian || /usr/bin/make -f /usr/share/kernel-package/rules debian test -f .config || /usr/bin/make -f /usr/share/kernel-package/rules .config test ! -f stamp-configure \ /usr/bin/make CROSS_COMPILE= \ ARCH=i386 oldconfig \ /usr/bin/make CROSS_COMPILE= \ ARCH=i386 dep \ /usr/bin/make CROSS_COMPILE= \ ARCH=i386 clean \ touch stamp-configure make: [stamp-configure] Error 1 (ignored) for module in /home/jeronimo/Linux/kernel/modules/* ; do \ if test -d $module; then \ (cd $module; \ if ./debian/rules KVERS=2.4.0-prerelease-ac3 KSRC=/home/jeronimo/Linux/kernel/linux-2.4.0-pre-ac3-reiser \ KMAINT=Jeronimo Pellegrini KEMAIL=[EMAIL PROTECTED] \ KDREV=Custom.1.00 kdist_clean; then\ echo Module $module cleaned; \ else \ echo Module $module failed to clean up; \ echo Hit return to Continue?; \ read ans;\ fi; \ ); \ fi; \ done make[1]: Entering directory `/home/jeronimo/Linux/kernel/modules/i2c-2.5.4' make[1]: *** No rule to make target `kdist_clean'. Stop. make[1]: Leaving directory `/home/jeronimo/Linux/kernel/modules/i2c-2.5.4' Module /home/jeronimo/Linux/kernel/modules/i2c-2.5.4 failed to clean up Hit return to Continue? make: *** [modules_clean] Interrupt -- Jeronimo Pellegrini Institute of Computing - Unicamp - Brazil http://www.ic.unicamp.br/~jeronimo mailto:[EMAIL PROTECTED]mailto:[EMAIL PROTECTED]
Re: make-kpkg question.
you definitely do not want use the patches for 2.2.18 with any other kernel, unless you really know what you are doing (you would have to make sure that the files that the patch changes are unchanged between 2.2.18 and whatever you will use). yah, i know that :) I don't know whether you can use non-debian tarball instead of debian source, but it's easy enough to check - get the kernel-source-2.2.17 and 'standard' kernel tarball for 2.2.17 and compare them - if they are different, you don't want to use tarball instead of kernel package. the problem is that there are lots of superficial differences (readme's etc) and i wasn't sure if it was just a couple text files which were inserted or if there was some greater significance that i was missing. thanks, adam.
Kernel patches (Was: make-kpkg question)
you definitely do not want use the patches for 2.2.18 with any other kernel, unless you really know what you are doing (you would have to make sure that the files that the patch changes are unchanged between 2.2.18 and whatever you will use). This brings up another question: According to what I understand from the docs, if I already have the original 2.2.17 source (apt-get kernel-source-2.2.17), then I can download the newest patch-2.2.18-pre* from kernel.org and use it to get the latest 2.2.18 kernel source tree. Is this correct, and if so, would I then be able to add patches that are intended for 2.2.18 kernels on top of the resulting source tree, and so on, and so on? It's just that a complete kernel source tree is ip to 15 Megs nowadays, whereas the patches are only 2.5 Megs. If the results are the same, then its obviously preferable to save bandwidth (not to mention download time), and use the patches instead. -- Cheers .~. /V\ // \\ /( )\ ^`~ยด^ hugge
Re: Kernel patches (Was: make-kpkg question)
On Fri, Dec 15, 2000 at 01:50:34PM +0100, Peter Hugosson-Miller wrote: you definitely do not want use the patches for 2.2.18 with any other kernel, unless you really know what you are doing (you would have to make sure that the files that the patch changes are unchanged between 2.2.18 and whatever you will use). This brings up another question: According to what I understand from the docs, if I already have the original 2.2.17 source (apt-get kernel-source-2.2.17), then I can download the newest patch-2.2.18-pre* from kernel.org and use it to get the latest 2.2.18 kernel source tree. Is this correct, and if so, would I then be able to add patches that are intended for 2.2.18 kernels on top of the resulting source tree, and so on, and so on? It's just that a complete kernel source tree is ip to 15 Megs nowadays, whereas the patches are only 2.5 Megs. If the results are the same, then its obviously preferable to save bandwidth (not to mention download time), and use the patches instead. The kernel-source-2.2.17 in potato is some pre kernel, iirc, the one in woody should be the final, but check it before attempting to apply 2.2.18 patch (no pre anymore, 2.2.18 is released). -- ,---. Name: Alson van der Meulen Personal: [EMAIL PROTECTED] School: [EMAIL PROTECTED] `---' Go get your backup tape. (You do ha a backup tape?) -
make-kpkg question.
hey. i wanna build my own kernel using make-kpkg with some custom patches (the openwall patch and the sub domain patch from wirex) with the release 2.2.18 kernel (which isn't in debian yet). it looks like i can just put the patches into /usr/src/kernel-patches but my question is do i have to wait for an official debian kernel-source-2.2.18 package to come out or can i just use the 2.2.18pre21 (or even the 2.2.17 one for that matter) and download the official 2.2.18 tarball from kernel.org and use make-kpkg with that? adam.
Re: make-kpkg question.
Adam Shand [EMAIL PROTECTED] writes: AS i wanna build my own kernel using make-kpkg with some custom patches (the AS openwall patch and the sub domain patch from wirex) with the release AS 2.2.18 kernel (which isn't in debian yet). AS AS it looks like i can just put the patches into /usr/src/kernel-patches but AS my question is do i have to wait for an official debian AS kernel-source-2.2.18 package to come out or can i just use the 2.2.18pre21 AS (or even the 2.2.17 one for that matter) and download the official 2.2.18 AS tarball from kernel.org and use make-kpkg with that? You can run make-kpkg on any old kernel tarball, even if the tree isn't the Official Debian Blessed Source. I didn't have any trouble building 2.2.18 with a handful of associated modules that way. :-) -- David Maze [EMAIL PROTECTED] http://www.mit.edu/~dmaze/ Theoretical politics is interesting. Politicking should be illegal. -- Abra Mitchell
Re: make-kpkg question.
Adam Shand wrote: hey. i wanna build my own kernel using make-kpkg with some custom patches (the openwall patch and the sub domain patch from wirex) with the release 2.2.18 kernel (which isn't in debian yet). it looks like i can just put the patches into /usr/src/kernel-patches but my question is do i have to wait for an official debian kernel-source-2.2.18 package to come out or can i just use the 2.2.18pre21 (or even the 2.2.17 one for that matter) and download the official 2.2.18 tarball from kernel.org and use make-kpkg with that? you definitely do not want use the patches for 2.2.18 with any other kernel, unless you really know what you are doing (you would have to make sure that the files that the patch changes are unchanged between 2.2.18 and whatever you will use). I don't know whether you can use non-debian tarball instead of debian source, but it's easy enough to check - get the kernel-source-2.2.17 and 'standard' kernel tarball for 2.2.17 and compare them - if they are different, you don't want to use tarball instead of kernel package. erik
