Re: [coLinux-users] CoLinux 0.7.7.1 + kernel 2.6.26.8 won't build

[Sergei Z. <sf...@ya...>]

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 don't know why you have this error. I can only say, that the patches
>>>> and config in source of coLinux version 0.7.7.1 can clean build kernel
>>>> 2.6.26.8, used gcc 4.4.1
>>>> Please try to remove or rename the both directories
>>>> linux-2.6.26.8-source and linux-2.6.26.8-build. Than start a fresh build
>>>> with default config.
>>>>
>>> I'm using gcc 4.4.3. I suppose I should have mentioned this in the beginning. I'm not using the coLinux configure/make. I'm applying the kernel patches by hand and running make in the kernel directory. This worked just fine for older coLinux/kernel. What else does coLinux make do besides applying the patches and default config?
>>>
>>> Unfortunately, I can't use the coLinux build system, because I don't have Python installed (and, to be honest, I'm not looking forward to installing it just to run a single script, as it would mean building it from source).
>>>
>> 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.
>
> CoLinux demons and Windows driver can't build without Python. But, this
> typcal user does not need to rebuild.
>
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.