From: Henry N. <hen...@ar...> - 2010-09-15 19:50:46
|
On 15.09.2010 19:16, Sergei Zhirikov wrote: > On 2010-09-14 22:20, Henry Nestler wrote: >> On 14.09.2010 22:05, Sergei Zhirikov wrote: >>> On 2010-09-14 20:19, Sergei Zhirikov wrote: >>>> On 2010-09-14 01:35, Henry Nestler wrote: >>>>> On 12.09.2010 21:59, Sergei Zhirikov wrote: >>>>>> make[1]: *** No rule to make target `arch/x86/pci/copci.o', needed by `arch/x86/pci/built-in.o'. Stop. >>>>>> make: *** [arch/x86/pci] Error 2 >>>>> [...] >>>> >>> I've managed to use coLinux build system without Python. It was actually quite easy, as Python is not really necessary. Shame that 'configure' treats it as a strict requirement. >> Yes, kernel can build without Python. I hope you found doc/building, and >> the bin/build-kernel.sh for simple kernel build. >> >> [...] > Thanks for trying to help. I've figured out what the problem was. All I had to do is manually create a symbolic link 'arch/i386 -> x86' in the kernel source directory *before* applying the coLinux patches. > > Apparently, some time between 2.6.22 and 2.6.26 the Linux code that used to be in arch/i386 moved to arch/x86. However coLinux patches continue using arch/i386, so if the symlink does not exist at the time of applying the patches a directory arch/i386 is created with only coLinux files in it. That causes subsequent build to fail. Ah, yes. That is true. Sorry for trouble with that. As long kernel 2.6.22 exist with more recent kernels, we had to merge both patches via softlink. Since kernel 2.6.22 was removed inside coLinux 0.7.8, this softlink was removed from bin/build-kernel.sh, and no longer need. By the while: The comouse.c was fixed in source of coLinux 0.7.8 now. -- Henry N. |