From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Anthony Wright <anthony@overnetdata.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: What is tools/firmware/rombios/32bit/... used for?
Date: Mon, 28 Jul 2014 23:58:36 +0100 [thread overview]
Message-ID: <53D6D59C.2090803@citrix.com> (raw)
In-Reply-To: <53D6BD4C.9090708@overnetdata.com>
On 28/07/2014 22:14, Anthony Wright wrote:
> I'm trying to build xen on a pure 64 bit system, but the build is
> failing when it tries to build
> tools/firmware/rombios/32bit/tcgbios/tcgbios.c with the error:
>
> /usr/include/gnu/stubs.h:7:27: fatal error: gnu/stubs-32.h: No such file
> or directory
>
> From reading around the error, it's caused by a lack of a 32 bit libc
> which would make sense as I only have a 64 bit libc on the system at the
> moment. To reduce the size of the distro (see my earlier Perl dependency
> post), I'd prefer to avoid having to build a 32 bit libc. I therefore
> wondered what tcgbios does and what the impact of failing to build the
> 32 bit support for it would be?
>
> thanks,
>
> Anthony.
hvmloader is a 32bit binary. It is the first bit of code executed in
any HVM domain and has the job of preparing certain architectural bits
for the BIOS, followed by dropping into 16bit mode to execute the
provided BIOS image. Irrespective of the rest of your install, it does
have to be built as a 32bit ELF file, as 32bit is the start mode of HVM
domains.
There is no way of avoiding the need for a 32bit set of headers if you
want to build the base components Xen needs to function.
~Andrew
next prev parent reply other threads:[~2014-07-28 22:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-28 21:14 What is tools/firmware/rombios/32bit/... used for? Anthony Wright
2014-07-28 22:58 ` Andrew Cooper [this message]
2014-07-29 8:44 ` Ian Campbell
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=53D6D59C.2090803@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=anthony@overnetdata.com \
--cc=xen-devel@lists.xen.org \
/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.