From: Robin van Leeuwen <rvl@ttg-edam.nl>
To: xen-devel <xen-devel@lists.xensource.com>
Subject: Compiling xen-unstable in 32bit chroot on amd64
Date: Thu, 25 Aug 2005 15:37:25 +0000 [thread overview]
Message-ID: <430DE5B5.40003@ttg-edam.nl> (raw)
I've got two computers here one amd64 3500/2GB/debian-amd64-testing
and a amd-duron-900/512mb/debian-testing.
I've setup a 32-bit chroot on my amd64 and want to
compile xen-unstable in the32 bit enviroment to
run xen on the duron. Because compiling after "make mproper"
on the Duron takes about 2 hours, and on the amd64 about 5
miniutes. I'm stuck on compiling in the 32 bit chroot:
---------------
make[2]: Entering directory `/usr/src/xen-unstable.hg/xen'
make[2]: `include/xen/acm_policy.h' is up to date.
make[2]: Leaving directory `/usr/src/xen-unstable.hg/xen'
[ -e include/asm ] || ln -sf asm-x86 include/asm
make -C arch/x86 asm-offsets.s
make[2]: Entering directory `/usr/src/xen-unstable.hg/xen/arch/x86'
gcc -nostdinc -fno-builtin -fno-common -fno-strict-aliasing -iwithprefix
include -Wall -Werror -Wno-pointer-arith -pipe
-I/usr/src/xen-unstable.hg/xen/include
-I/usr/src/xen-unstable.hg/xen/include/asm-x86/mach-generic
-I/usr/src/xen-unstable.hg/xen/include/asm-x86/mach-default -O3
-fomit-frame-pointer -msoft-float -m64 -mno-red-zone -fpic
-fno-reorder-blocks -fno-asynchronous-unwind-tables -DNDEBUG -DVERBOSE
-S -o asm-offsets.s x86_64/asm-offsets.c
cc1: sorry, unimplemented: 64-bit mode not compiled in
x86_64/asm-offsets.c: In function `__dummy__':
x86_64/asm-offsets.c:29: error: structure has no member named `r15'
x86_64/asm-offsets.c:30: error: structure has no member named `r14'
x86_64/asm-offsets.c:31: error: structure has no member named `r13'
x86_64/asm-offsets.c:32: error: structure has no member named `r12'
x86_64/asm-offsets.c:33: error: structure has no member named `rbp'
x86_64/asm-offsets.c:34: error: structure has no member named `rbx'
x86_64/asm-offsets.c:35: error: structure has no member named `r11'
x86_64/asm-offsets.c:36: error: structure has no member named `r10'
x86_64/asm-offsets.c:37: error: structure has no member named `r9'
x86_64/asm-offsets.c:38: error: structure has no member named `r8'
x86_64/asm-offsets.c:39: error: structure has no member named `rax'
x86_64/asm-offsets.c:40: error: structure has no member named `rcx'
x86_64/asm-offsets.c:41: error: structure has no member named `rdx'
x86_64/asm-offsets.c:42: error: structure has no member named `rsi'
x86_64/asm-offsets.c:43: error: structure has no member named `rdi'
x86_64/asm-offsets.c:46: error: structure has no member named `rip'
x86_64/asm-offsets.c:49: error: structure has no member named `rsp'
x86_64/asm-offsets.c:64: error: structure has no member named
`syscall_callback_eip'
make[2]: *** [asm-offsets.s] Error 1
make[2]: Leaving directory `/usr/src/xen-unstable.hg/xen/arch/x86'
make[1]: *** [/usr/src/xen-unstable.hg/xen/xen] Error 2
make[1]: Leaving directory `/usr/src/xen-unstable.hg/xen'
make: *** [xen] Error 2
----------------------
Can sombody help me out?
kind regards,
Robin van Leeuwen
next reply other threads:[~2005-08-25 15:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-25 15:37 Robin van Leeuwen [this message]
2005-08-25 15:51 ` Compiling xen-unstable in 32bit chroot on amd64 Keir Fraser
2005-08-25 16: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=430DE5B5.40003@ttg-edam.nl \
--to=rvl@ttg-edam.nl \
--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.