From: Robin van Leeuwen <rvl@ttg-edam.nl>
To: xen-devel <xen-devel@lists.xensource.com>
Subject: Re: Compiling xen-unstable in 32bit chroot on amd64
Date: Thu, 25 Aug 2005 16:05:54 +0000 [thread overview]
Message-ID: <430DEC62.3030500@ttg-edam.nl> (raw)
In-Reply-To: <d3662eecacf3d4666cf91ba137a77025@cl.cam.ac.uk>
Keir Fraser wrote:On 25 Aug 2005, at 16:37,
Robin van Leeuwen wrote:
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: The build system thinks
you are targetting x86_64.
There are two fixes: either run 'setarch i686', which will change
the output of the uname command, or build Xen with 'make
XEN_COMPILE_ARCH=x86_32'.
-----------------
Thanks, the "make XEN_COMPILE_ARCH=x86_32" works, this saves me
about 5 hours of compiling time per day :-)
Kind regards,
Robin van Leeuwen
prev parent reply other threads:[~2005-08-25 16:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-25 15:37 Compiling xen-unstable in 32bit chroot on amd64 Robin van Leeuwen
2005-08-25 15:51 ` Keir Fraser
2005-08-25 16:05 ` Robin van Leeuwen [this message]
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=430DEC62.3030500@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.