* compile problems with tip
@ 2005-08-25 18:20 Diwaker Gupta
2005-08-25 18:33 ` Christian Limpach
0 siblings, 1 reply; 4+ messages in thread
From: Diwaker Gupta @ 2005-08-25 18:20 UTC (permalink / raw)
To: xen-devel
I've been having compile problems since this morning. My last pull was:
changeset: 6465:b4b3f6be5226adfb127bc32fd5cca27f2ed473f7
parent: 6464:6ac24e39c9a44fa6866ebb9ff2e47684fab5ad54
parent: 6447:f7cdd99d11065bf684002bce8415eda97f09e5df
user: cl349@firebug.cl.cam.ac.uk
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
^ permalink raw reply [flat|nested] 4+ messages in thread
* RE: compile problems with tip
@ 2005-08-25 18:26 Li, Xin B
2005-08-25 18:29 ` Stephan Diestelhorst
0 siblings, 1 reply; 4+ messages in thread
From: Li, Xin B @ 2005-08-25 18:26 UTC (permalink / raw)
To: Diwaker Gupta, xen-devel
The current tip is 6420, but yours... I'm confused.
-Xin
>-----Original Message-----
>From: xen-devel-bounces@lists.xensource.com
>[mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of
>Diwaker Gupta
>Sent: 2005年8月26日 2:21
>To: xen-devel@lists.xensource.com
>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@firebug.cl.cam.ac.uk
>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@lists.xensource.com
>http://lists.xensource.com/xen-devel
>
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: compile problems with tip
2005-08-25 18:26 Li, Xin B
@ 2005-08-25 18:29 ` Stephan Diestelhorst
0 siblings, 0 replies; 4+ messages in thread
From: Stephan Diestelhorst @ 2005-08-25 18:29 UTC (permalink / raw)
To: xen-devel; +Cc: Diwaker Gupta, Li, Xin B
> The current tip is 6420, but yours... I'm confused.
> -Xin
Bear in mind that those short numbers may be different for each
user (depending on your local repo-history)! In general you should use the
longer hash, which ought to be consistent between different machines
Cheers,
Stephan
> >-----Original Message-----
> >From: xen-devel-bounces@lists.xensource.com
> >[mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of
> >Diwaker Gupta
> >Sent: 2005年8月26日 2:21
> >To: xen-devel@lists.xensource.com
> >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@firebug.cl.cam.ac.uk
> >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@lists.xensource.com
> >http://lists.xensource.com/xen-devel
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: compile problems with tip
2005-08-25 18:20 compile problems with tip Diwaker Gupta
@ 2005-08-25 18:33 ` Christian Limpach
0 siblings, 0 replies; 4+ messages in thread
From: Christian Limpach @ 2005-08-25 18:33 UTC (permalink / raw)
To: Diwaker Gupta; +Cc: xen-devel
On 8/25/05, Diwaker Gupta <diwaker.lists@gmail.com> wrote:
> I've been having compile problems since this morning. My last pull was:
You need to recreate your linux-2.6.12-xen[0U] trees or at least run
mkbuildtree over them again since a while back (Aug 19, changeset
74044b8186a9b66eeeb684915e741c0ed9ed0e8b)
arch/xen/i386/kernel/init_task.c was added to the sparse tree.
christian
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2005-08-25 18:33 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2005-08-25 18:20 compile problems with tip Diwaker Gupta
2005-08-25 18:33 ` Christian Limpach
-- strict thread matches above, loose matches on Subject: below --
2005-08-25 18:26 Li, Xin B
2005-08-25 18:29 ` Stephan Diestelhorst
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.