From: Robin van Leeuwen <robin.van.leeuwen@nl.nyklogistics.com>
To: xen-devel@lists.xensource.com
Subject: xen unstable build domU kenel fails on entry.S
Date: Sun, 04 Sep 2005 14:26:36 +0200 [thread overview]
Message-ID: <431AE7FC.2070809@nl.nyklogistics.com> (raw)
amd64:/usr/src/xen-unstable.hg#hg tip
changeset: 6597:a1de77c1486c5f35884e9f578b7f33b6bd75c362
tag: tip
user: shand@ubuntu.eng.hq.xensource.com
date: Sat Sep 3 03:36:29 2005
summary: Enable 'live' migration from a tools pov; prior to this the
'live' flag was
Which option in make ARCH=xen menuconfig should i disable to get rid of the
following compile error of domU linux-2.6.12-domU?
-------------------
arch/xen/x86_64/kernel/entry.S: Assembler messages:
arch/xen/x86_64/kernel/entry.S:468: Error: CFI instruction used without
previous .cfi_startproc
arch/xen/x86_64/kernel/entry.S:468: Error: junk at end of line, first
unrecognized character is `-'
arch/xen/x86_64/kernel/entry.S:495: Error: CFI instruction used without
previous .cfi_startproc
arch/xen/x86_64/kernel/entry.S:495: Error: junk at end of line, first
unrecognized character is `6'
arch/xen/x86_64/kernel/entry.S:495: Error: CFI instruction used without
previous .cfi_startproc
arch/xen/x86_64/kernel/entry.S:495: Error: no such instruction: `rbx,5*8'
arch/xen/x86_64/kernel/entry.S:495: Error: CFI instruction used without
previous .cfi_startproc
arch/xen/x86_64/kernel/entry.S:495: Error: no such instruction: `rbp,4*8'
arch/xen/x86_64/kernel/entry.S:495: Error: CFI instruction used without
previous .cfi_startproc
arch/xen/x86_64/kernel/entry.S:495: Error: no such instruction: `r12,3*8'
arch/xen/x86_64/kernel/entry.S:495: Error: CFI instruction used without
previous .cfi_startproc
arch/xen/x86_64/kernel/entry.S:495: Error: no such instruction: `r13,2*8'
arch/xen/x86_64/kernel/entry.S:495: Error: CFI instruction used without
previous .cfi_startproc
arch/xen/x86_64/kernel/entry.S:495: Error: no such instruction: `r14,1*8'
arch/xen/x86_64/kernel/entry.S:495: Error: CFI instruction used without
previous .cfi_startproc
arch/xen/x86_64/kernel/entry.S:495: Error: no such instruction: `r15,0*8'
arch/xen/x86_64/kernel/entry.S:500: Error: CFI instruction used without
previous .cfi_startproc
arch/xen/x86_64/kernel/entry.S:500: Error: junk at end of line, first
unrecognized character is `-'
arch/xen/x86_64/kernel/entry.S:527: Error: .cfi_endproc without
corresponding .cfi_startproc
arch/xen/x86_64/kernel/entry.S:804: Error: previous CFI entry not closed
(missing .cfi_endproc)
make[4]: *** [arch/xen/x86_64/kernel/entry.o] Error 1
make[3]: *** [arch/xen/x86_64/kernel] Error 2
make[3]: Leaving directory `/usr/src/xen-unstable.hg/linux-2.6.12-xenU'
make[2]: *** [build] Error 2
make[2]: Leaving directory `/usr/src/xen-unstable.hg'
make[1]: *** [linux-2.6-xenU-build] Error 2
make[1]: Leaving directory `/usr/src/xen-unstable.hg'
make: *** [kernels] Error 1
amd64:/usr/src/xen-unstable.hg# cd linux-2.6.12-xenU/
-------------------------------
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
next reply other threads:[~2005-09-04 12:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-04 12:26 Robin van Leeuwen [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-09-03 16:23 xen unstable build domU kenel fails on entry.S Robin van Leeuwen
2005-09-04 17:05 ` Robin van Leeuwen
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=431AE7FC.2070809@nl.nyklogistics.com \
--to=robin.van.leeuwen@nl.nyklogistics.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.