Re: [arch-general] Why taking so long?
Ray Rashif writes: > In the latest kernel, there is 'make localmodconfig' for precisely > this problem. Thanks to all of you, I recorded everything so I'll try next time. By the way I had to mask the kernel26 build (even if I don't use it) because broadcom-wl is always a bit too late and it wouldn't work with the new kernel. Could I just tell arch that I want to use the other kernel instead??
Re: [arch-general] Why taking so long?
On 31/01/2010, Andrea Fagiani wrote: > On 01/30/2010 01:37 PM, Heiko Baums wrote: >> Am Sat, 30 Jan 2010 13:11:26 +0100 >> schrieb Andrea Crotti: >> >> >>> Sometimes (only twice actually) I had to recompile the kernel with ice >>> support from aur. >>> Now compiling the kernel is not a short job, but it looks like it >>> really compiles EVERYTHING! >>> >>> Maybe putting my .config somewhere it will not do it, how do you >>> manage it? >>> >> I guess this is the easiest way to compile your own kernel: >> >> 1. cp -R /var/abs/core/kernel26 /var/abs/local/kernel26- >> >> 2. Edit these variables in the PKGBUILD: >> pkgbase (to your package name) >> pkgname (copy the original one and replace kernel26* with >> kernel26-*) >> >> 3. Add the patches you like to the PKGBUILD. >> >> 4. Remove the comments of these lines: >> #make menuconfig # CLI menu for configuration (or the other options) >> #msg "Stopping build" >> #return 1 >> >> 5. Run makepkg -g and replace the md5sums in the PKGBUILD. >> >> 6. Run makepkg and configure your kernel. (You don't need to change >> CONFIG_LOCALVERSION, this is done by the PKGBUILD automatically.) >> >> 7. >> cd /var/abs/local/kernel26-/src/linux- >> diff -u .config.old .config >> cd ../.. >> Make the changes to the files config and config.x86_64 manually. >> >> or >> >> cd /var/abs/local/kernel26- >> cp src/linux-/.config ./config >> or >> cp src/linux-/.config ./config.x86_64 >> (depending on your CPU) >> >> 8. Run makepkg -g and replace the md5sums in the PKGBUILD. >> >> 9. Edit the PKGBUILD and comment the lines from 4. >> >> 10. Run makepkg and install the built package. >> >> 11. Finished! >> >> If you want to publish your kernel package in AUR then you >> unfortunately need to revert the PKGBUILD from a split to a single >> package. >> >> Greetings, >> Heiko >> >> > Or, you could just edit the kernel26-ice PKGBUILD and enable the > /menuconfig/ variable so that it triggers menuconfig in the build() > section, there you can either modify the configuration on the run or > load an alternate config file; just be sure to save the edited config to > /.conf/ig . > > Andrea > In the latest kernel, there is 'make localmodconfig' for precisely this problem. -- GPG/PGP ID: B42DDCAD
Re: [arch-general] Why taking so long?
On 01/30/2010 01:37 PM, Heiko Baums wrote: Am Sat, 30 Jan 2010 13:11:26 +0100 schrieb Andrea Crotti: Sometimes (only twice actually) I had to recompile the kernel with ice support from aur. Now compiling the kernel is not a short job, but it looks like it really compiles EVERYTHING! Maybe putting my .config somewhere it will not do it, how do you manage it? I guess this is the easiest way to compile your own kernel: 1. cp -R /var/abs/core/kernel26 /var/abs/local/kernel26- 2. Edit these variables in the PKGBUILD: pkgbase (to your package name) pkgname (copy the original one and replace kernel26* with kernel26-*) 3. Add the patches you like to the PKGBUILD. 4. Remove the comments of these lines: #make menuconfig # CLI menu for configuration (or the other options) #msg "Stopping build" #return 1 5. Run makepkg -g and replace the md5sums in the PKGBUILD. 6. Run makepkg and configure your kernel. (You don't need to change CONFIG_LOCALVERSION, this is done by the PKGBUILD automatically.) 7. cd /var/abs/local/kernel26-/src/linux- diff -u .config.old .config cd ../.. Make the changes to the files config and config.x86_64 manually. or cd /var/abs/local/kernel26- cp src/linux-/.config ./config or cp src/linux-/.config ./config.x86_64 (depending on your CPU) 8. Run makepkg -g and replace the md5sums in the PKGBUILD. 9. Edit the PKGBUILD and comment the lines from 4. 10. Run makepkg and install the built package. 11. Finished! If you want to publish your kernel package in AUR then you unfortunately need to revert the PKGBUILD from a split to a single package. Greetings, Heiko Or, you could just edit the kernel26-ice PKGBUILD and enable the /menuconfig/ variable so that it triggers menuconfig in the build() section, there you can either modify the configuration on the run or load an alternate config file; just be sure to save the edited config to /.conf/ig . Andrea
Re: [arch-general] Why taking so long?
Am Sat, 30 Jan 2010 13:11:26 +0100 schrieb Andrea Crotti : > Sometimes (only twice actually) I had to recompile the kernel with ice > support from aur. > Now compiling the kernel is not a short job, but it looks like it > really compiles EVERYTHING! > > Maybe putting my .config somewhere it will not do it, how do you > manage it? I guess this is the easiest way to compile your own kernel: 1. cp -R /var/abs/core/kernel26 /var/abs/local/kernel26- 2. Edit these variables in the PKGBUILD: pkgbase (to your package name) pkgname (copy the original one and replace kernel26* with kernel26-*) 3. Add the patches you like to the PKGBUILD. 4. Remove the comments of these lines: #make menuconfig # CLI menu for configuration (or the other options) #msg "Stopping build" #return 1 5. Run makepkg -g and replace the md5sums in the PKGBUILD. 6. Run makepkg and configure your kernel. (You don't need to change CONFIG_LOCALVERSION, this is done by the PKGBUILD automatically.) 7. cd /var/abs/local/kernel26-/src/linux- diff -u .config.old .config cd ../.. Make the changes to the files config and config.x86_64 manually. or cd /var/abs/local/kernel26- cp src/linux-/.config ./config or cp src/linux-/.config ./config.x86_64 (depending on your CPU) 8. Run makepkg -g and replace the md5sums in the PKGBUILD. 9. Edit the PKGBUILD and comment the lines from 4. 10. Run makepkg and install the built package. 11. Finished! If you want to publish your kernel package in AUR then you unfortunately need to revert the PKGBUILD from a split to a single package. Greetings, Heiko
Re: [arch-general] Why taking so long?
On Sat, Jan 30, 2010 at 07:13, pyther wrote: > Likely everything is being compiled in the kernel. The idea behind this is > so you can take the binary and distribute it to anyone and have it work on > their systems (with different hardware). > > if you want to use your own config and select what you want have a look at > this wiki guide: > http://wiki.archlinux.org/index.php/Custom_Kernel_Compilation_with_ABS > > ~pyther > I don't think this wiki page has been updated since the big PKGBUILD rewrite. It should be *much* simpler now than that guide implies. The page needs a total overhaul by someone who knows this inside and out.
Re: [arch-general] Why taking so long?
On 01/30/2010 07:11 AM, Andrea Crotti wrote: Sometimes (only twice actually) I had to recompile the kernel with ice support from aur. Now compiling the kernel is not a short job, but it looks like it really compiles EVERYTHING! Maybe putting my .config somewhere it will not do it, how do you manage it? Thanks Likely everything is being compiled in the kernel. The idea behind this is so you can take the binary and distribute it to anyone and have it work on their systems (with different hardware). if you want to use your own config and select what you want have a look at this wiki guide: http://wiki.archlinux.org/index.php/Custom_Kernel_Compilation_with_ABS ~pyther
