Sometime back I faced similar error on my CentOS machine and after googling I fixed it in 2 steps.
1. ln -s /usr/src/kernels/2.6.32-220.el6.x86_64 /lib/modules/2.6.32-220.el6.x86_64/build
2. ln -s /lib/modules/2.6.32-220.el6.x86_64/build /lib/modules/2.6.32-220.el6.x86_64/source
Can someone help me understand why this 2nd symbolic link (source-->build) required?
Thanks,
On 4 December 2013 17:00, Sudip Mukherjee <sudipm.mukherjee@xxxxxxxxx> wrote:
Whats the error?Hi AnilPlease do not top post.For your error , please verify if /lib/modules/2.6.32-220.el6.x86_64/build is really linking to the folder containing the kernel files.RegardsSudipThats the issue the link is not there how to create the link.On your mails please always put cc to the list.Even if it is centos the build file will be there. And it should have a soft link to the folder containing your kernel source files. first please find out where your source file is . In my system it is at /usr/src/kernels/<version>In your it should be /usr/src/kernels/2.6.32-220.el6.x86_64After you find the folder , give the command "sudo ln -s /usr/src/kernels/2.6.32-220.el6.x86_64 /lib/modules/2.6.32-220.el6.x86_64/build"RegardsSudip
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@xxxxxxxxxxxxxxxxx
http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
--
---
< Chandan Jay Sharma >
< Chandan Jay Sharma >
_______________________________________________ Kernelnewbies mailing list Kernelnewbies@xxxxxxxxxxxxxxxxx http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies