warnings after saving .config file under xconfig
Recently I decided to upgrade from kernel 2.6.13 to 2.6.15. I simply the copied the config-2.6.13 to /usr/src/linux-source-2.6.15 as .config and then ran make xconfig. After make kernel changes, when I saved the file and exited from xconfig I got the following warning messages:
Code:
debian:/usr/src/linux-source-2.6.15# cp /boot/config-2.6.13 .config Anyone? |
It's just trying to tell you that your 2.6.13 .config file doesn't address the changes present in your new 2.6.15 kernel. It probably went with whatever the defaults are for those configurations... look them over and see if those are ones you may need, or want. The biggest difference (to me, anyways) going from a 2.6.13 to a 2.6.15 kernel is built in Intel Pro Wireless support.
|
Those are warnings not errors, not running oldconfig will just set them to the default values instead of asking you what you want.
|
Quote:
But if that is the case why does the warning says: "trying to assign nonexistent symbol ACPI_BUS" and so. At first glance it looks as if the new kernel(2.6.15) will not have those options which are listed as nonexistent. I am a bit confused.:scratch: ??? Thank you guys for looking into this.. |
It isn't adding it to the config, but the makefile/kernel has defaults that it will use
|
ok. Does that mean that I don;t need to worry about those warnings. Actually I thought that the new kernel(which is being compiled) won;t have all those options which appeared in the warnings.
|
I would run make oldconfig just because it is the right thing to do.
|
Quote:
If you have time, take a look at this. I really get confused when it comes to this issue. http://www.linuxquestions.org/questi...d.php?t=407097 Thanks |
Well according to that thread menuconfig/xconfig should see that you are using an old config and run oldconfig for you. Either you are not saving you config after running it or it is not doing that. Either way, there is no harm in running make oldconfig and IMHO its the right thing to do.
Consider this. New kernel has a new option, it defaults to compile as a module. This module has a dependency on some feature which you have removed/disabled. Will the make modules generate the module anyway even though it shouldn't? I can't answer that, but if it does can you imagine the headache of tracking down the unresolved symbols? Especially when it is so easy to run make oldconfig. Now considering this is a Debian forum and make-kpkg is "The Debian Way" to compile a kernel, which will run make oldconfig for you, this is a moot point. |
Quote:
Code:
#make clean Thanks once again for all the help. |
Quote:
Thanks |
That is what I would do.
|
thanks dracae a lot. From now on I will try to following the mentioned procedure.
Thank you once again.. |
All times are GMT -5. The time now is 12:32 AM. |