[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] RE: [Xen-devel] compile problems with tip
The current tip is 6420, but yours... I'm confused. -Xin >-----Original Message----- >From: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx >[mailto:xen-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of >Diwaker Gupta >Sent: 2005年8月26日 2:21 >To: xen-devel@xxxxxxxxxxxxxxxxxxx >Subject: [Xen-devel] compile problems with tip > >I've been having compile problems since this morning. My last pull was: > >changeset: 6465:b4b3f6be5226adfb127bc32fd5cca27f2ed473f7 >parent: 6464:6ac24e39c9a44fa6866ebb9ff2e47684fab5ad54 >parent: 6447:f7cdd99d11065bf684002bce8415eda97f09e5df >user: cl349@xxxxxxxxxxxxxxxxxxxx >date: Thu Aug 25 10:27:49 2005 >summary: merge? > >The errors I get when compiling: > CC arch/xen/i386/kernel/init_task.o >arch/xen/i386/kernel/init_task.c:17: error: initializer >element is not constant >arch/xen/i386/kernel/init_task.c:17: error: (near initialization for >`init_mm.pgd') >arch/xen/i386/kernel/init_task.c:17: error: initializer >element is not constant >arch/xen/i386/kernel/init_task.c:17: error: (near initialization for >`init_mm.mm_users') >arch/xen/i386/kernel/init_task.c:17: error: initializer >element is not constant >arch/xen/i386/kernel/init_task.c:17: error: (near initialization for >`init_mm.mm_count') >arch/xen/i386/kernel/init_task.c:17: error: initializer >element is not constant >arch/xen/i386/kernel/init_task.c:17: error: (near initialization for >`init_mm.mmap_sem.wait_lock') >arch/xen/i386/kernel/init_task.c:17: error: initializer >element is not constant >arch/xen/i386/kernel/init_task.c:17: error: (near initialization for >`init_mm.mmap_sem.wait_list') >arch/xen/i386/kernel/init_task.c:17: error: initializer >element is not constant >arch/xen/i386/kernel/init_task.c:17: error: (near initialization for >`init_mm.mmap_sem') >arch/xen/i386/kernel/init_task.c:17: error: initializer >element is not constant >arch/xen/i386/kernel/init_task.c:17: error: (near initialization for >`init_mm.page_table_lock') >arch/xen/i386/kernel/init_task.c:17: error: initializer >element is not constant >arch/xen/i386/kernel/init_task.c:17: error: (near initialization for >`init_mm.mmlist') >arch/xen/i386/kernel/init_task.c:17: error: initializer >element is not constant >arch/xen/i386/kernel/init_task.c:17: error: (near initialization for >`init_mm.cpu_vm_mask') >arch/xen/i386/kernel/init_task.c:17: error: initializer >element is not constant >arch/xen/i386/kernel/init_task.c:17: error: (near initialization for >`init_mm.default_kioctx.users') >arch/xen/i386/kernel/init_task.c:17: error: initializer >element is not constant >arch/xen/i386/kernel/init_task.c:17: error: (near initialization for >`init_mm.default_kioctx.wait.lock') >arch/xen/i386/kernel/init_task.c:17: error: initializer >element is not constant >arch/xen/i386/kernel/init_task.c:17: error: (near initialization for >`init_mm.default_kioctx.wait.task_list') >arch/xen/i386/kernel/init_task.c:17: error: initializer >element is not constant >arch/xen/i386/kernel/init_task.c:17: error: (near initialization for >`init_mm.default_kioctx.wait') >arch/xen/i386/kernel/init_task.c:17: error: initializer >element is not constant >arch/xen/i386/kernel/init_task.c:17: error: (near initialization for >`init_mm.default_kioctx.ctx_lock') >arch/xen/i386/kernel/init_task.c:17: error: initializer >element is not constant >arch/xen/i386/kernel/init_task.c:17: error: (near initialization for >`init_mm.default_kioctx') >make[4]: *** [arch/xen/i386/kernel/init_task.o] Error 1 >make[3]: *** [arch/xen/i386/kernel] Error 2 >make[3]: Leaving directory `/root/myxen/linux-2.6.12-xen0' > >Is anyone else seeing these? >-- >Web/Blog/Gallery: http://floatingsun.net > >_______________________________________________ >Xen-devel mailing list >Xen-devel@xxxxxxxxxxxxxxxxxxx >http://lists.xensource.com/xen-devel > _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-devel
|
![]() |
Lists.xenproject.org is hosted with RackSpace, monitoring our |