SEO
vBulletin Search Engine Optimization
| |||||||
| Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
02-21-2008, 05:10 AM
| ||||
| ||||
 upgrading to new kernel version I noticed that even though I have been emerging in new vanilla-sources, they have not been getting used. This is because /usr/src/linux is linked to /usr/src/linux-2.4.19. The newer versions are just getting dumped into /usr/src/linux-2.4.XX. My typical approach to building my kernel is to cd to /usr/src/linux and run 'make menuconfig', then 'make dep && make clean bzImage modules modules_install'. So, I would think that I could just copy my config.h from linux-2.4.19 to the new linux-2.4.22, cd to linx-2.4.22, and run 'make dep && make clean...' and it would work fine. No such luck. It dies with: make[2]: *** No rule to make target `/usr/src/linux-2.4.22/include/linux/auto conf.h', needed by `/usr/src/linux-2.4.22/include/linux/modules/signal.ver'. Stop. What am I doing wrong?      |
|
02-21-2008, 05:10 AM
| |||
| |||
| Re: upgrading to new kernel version Wes Gray wrote: > I noticed that even though I have been emerging in new vanilla-sources, > they have not been getting used. This is because /usr/src/linux is linked > to /usr/src/linux-2.4.19. The newer versions are just getting dumped into > /usr/src/linux-2.4.XX. My typical approach to building my kernel is to > cd to /usr/src/linux and run 'make menuconfig', then > 'make dep && make clean bzImage modules modules_install'. So, I would > think that I could just copy my config.h from linux-2.4.19 to the new > linux-2.4.22, cd to linx-2.4.22, and run 'make dep && make clean...' > and it would work fine. No such luck. It dies with: > > make[2]: *** No rule to make target > `/usr/src/linux-2.4.22/include/linux/auto conf.h', needed by > `/usr/src/linux-2.4.22/include/linux/modules/signal.ver'. Stop. > > What am I doing wrong? I've been having the same issue and have begun to think it's a bug. For some reason the link is not being changed to use the new kernel source instead it's insisting on using the last. The work around I've developed is to ulink /usr/src/linux and then create a new link using ln -sf /usr/src/linux/vanilla-2.4.xx. HTH -- Registered Linux User # 286635 |
|
02-21-2008, 05:10 AM
| |||
| |||
| Re: upgrading to new kernel version Whyld-Chyld wrote: > I've been having the same issue and have begun to think it's a bug. For some > reason the link is not being changed to use the new kernel source instead > it's insisting on using the last. > > The work around I've developed is to ulink /usr/src/linux and then create a > new link using ln -sf /usr/src/linux/vanilla-2.4.xx. HTH OK, but how did you copy your kernel configuration from the old dir to the new one? I tried copying config.h over, but it wouldn't build. |
|
02-21-2008, 05:10 AM
| |||
| |||
| Re: upgrading to new kernel version On Mon, 08 Sep 2003 13:40:15 +0000, Wes Gray wrote: >> >> The work around I've developed is to ulink /usr/src/linux and then create a >> new link using ln -sf /usr/src/linux/vanilla-2.4.xx. HTH > > OK, but how did you copy your kernel configuration from the old dir to > the new one? I tried copying config.h over, but it wouldn't build. Do not copy config.h (It's a header file, which is needed), but copy /usr/linux/.config . |
|
02-21-2008, 05:14 AM
| ||||
| ||||
| Re: upgrading to new kernel version Hi, >> Do not copy config.h (It's a header file, which is needed), but copy >> /usr/linux/.config . I think you meant the file /usr/src/linux/.config :-) If you decide to switch to the new development kernel (which works quite stable at my place), you will notice that the symlink to the devel kernel sources is called linux-beta. HTH andi |
Linear Mode
