From: Diwaker Gupta <diwaker.lists@gmail.com>
To: xen-devel@lists.xensource.com
Subject: compile problems with tip
Date: Thu, 25 Aug 2005 11:20:35 -0700 [thread overview]
Message-ID: <891be9410508251120dc349c8@mail.gmail.com> (raw)
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
next reply other threads:[~2005-08-25 18:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-25 18:20 Diwaker Gupta [this message]
2005-08-25 18:33 ` compile problems with tip 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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=891be9410508251120dc349c8@mail.gmail.com \
--to=diwaker.lists@gmail.com \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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.