Re: Two 2.6.20-rc5-rt2 issues

2007-01-17 Thread Rui Nuno Capela
On Wed, January 17, 2007 06:31, Ingo Molnar wrote: > > * Rui Nuno Capela <[EMAIL PROTECTED]> wrote: > >> Building this already with -rt5, still gives: >> ... >> LD arch/i386/boot/compressed/vmlinux >> OBJCOPY arch/i386/boot/vmlinux.bin >> BUILD arch/i386/boot/bzImage >> Root device is (3, 2

Re: Two 2.6.20-rc5-rt2 issues

2007-01-16 Thread Ingo Molnar
* Rui Nuno Capela <[EMAIL PROTECTED]> wrote: > Building this already with -rt5, still gives: > ... > LD arch/i386/boot/compressed/vmlinux > OBJCOPY arch/i386/boot/vmlinux.bin > BUILD arch/i386/boot/bzImage > Root device is (3, 2) > Boot sector 512 bytes. > Setup is 7407 bytes. > Syst

Re: Two 2.6.20-rc5-rt2 issues

2007-01-16 Thread Rui Nuno Capela
On Tue, January 16, 2007 11:56, Ingo Molnar wrote: > > * Rui Nuno Capela <[EMAIL PROTECTED]> wrote: > >> First one is about building for UP (CONFIG_SMP not set) on my old P4 >> laptop. As it seems, all my build attempts failed at the final link >> stage, with undefined references to paravirt_enabl

Re: Two 2.6.20-rc5-rt2 issues

2007-01-16 Thread Ingo Molnar
* Rui Nuno Capela <[EMAIL PROTECTED]> wrote: > First one is about building for UP (CONFIG_SMP not set) on my old P4 > laptop. As it seems, all my build attempts failed at the final link > stage, with undefined references to paravirt_enable. After disabling > CONFIG_PARAVIRT I get a similar fai