From: Attilio Rao <attilio.rao@citrix.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>,
Ian Campbell <Ian.Campbell@citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: [PATCH] [PATCH v3] Fetch the OVMF repository from specific git mirror and enable it
Date: Sat, 17 Mar 2012 22:33:02 +0000 [thread overview]
Message-ID: <4F65111E.8030507@citrix.com> (raw)
In-Reply-To: <20320.35396.254724.585442@mariner.uk.xensource.com>
On 14/03/12 12:08, Ian Jackson wrote:
> Attilio Rao writes ("[Xen-devel] [PATCH] [PATCH v3] Fetch the OVMF repository from specific git mirror and enable it"):
>
>> Signed-off-by: Attilio Rao<attilio.rao@citrix.com>
>>
> cp ovmf-makefile ovmf/Makefile;
> Switched to a new branch 'dummy'
> cp seabios-config seabios-dir/.config;
> make subdirs-all
> make[4]: Entering directory `/u/iwj/work/xen-unstable-tools.hg/tools/firmware'
> make[5]: Entering directory `/u/iwj/work/xen-unstable-tools.hg/tools/firmware'
> make -C ovmf all
> make[6]: Entering directory `/u/iwj/work/xen-unstable-tools.hg/tools/firmware/ovmf-remote'
> make[6]: warning: -jN forced in submake: disabling jobserver mode.
> OvmfPkg/build.sh -a X64
> Initializing workspace
> /u/iwj/work/xen-unstable-tools.hg/tools/firmware/ovmf-remote/BaseTools
> Unable to find expected bin path under $EDK_TOOLS_PATH!
>
>> /u/iwj/work/xen-unstable-tools.hg/tools/firmware/ovmf-remote/BaseTools/Bin/Linux-i486
>>
> make[6]: *** [ovmf.bin] Error 1
> make[6]: Leaving directory `/u/iwj/work/xen-unstable-tools.hg/tools/firmware/ovmf-remote'
>
I think I see the issue here. Are you running with i486 as an arch?
This is a deficiency of the OVMF support, because it has some wrappers
to build appropriately the firmware which are OS and architectures
specific and it does support Linux-i686 and Linux-x86_64 but not Linux-i486.
I'm not sure about what we should do here, possible options include:
- Verify that, on all i486,i586,etc. we can eventually use i686 and
unify the script to do that
- Check if it is possible (it doesn't seem to be already present, but I
will dig further) if we can "cross-compile" the compiling OS and family
and use a mechanism to offer that
In any case we should check for the presence of the right wrapper and
skip ovmf, spitting out an informative error, if this is really the case.
Do you have feedback on the matter?
Attilio
next prev parent reply other threads:[~2012-03-17 22:33 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-01 19:28 [PATCH] [PATCH v3] Fetch the OVMF repository from specific git mirror and enable it Attilio Rao
2012-03-14 12:08 ` Ian Jackson
2012-03-14 13:14 ` Attilio Rao
2012-03-17 22:33 ` Attilio Rao [this message]
2012-03-19 16:36 ` Ian Jackson
2012-03-19 17:40 ` Attilio Rao
2012-03-19 17:50 ` Attilio Rao
2012-03-20 10:06 ` Christoph Egger
2012-03-20 10:47 ` Attilio Rao
2012-03-20 11:04 ` Christoph Egger
2012-03-20 11:11 ` Roger Pau Monné
2012-03-20 11:09 ` Attilio Rao
2012-03-20 11:57 ` Christoph Egger
2012-03-20 12:12 ` Attilio Rao
2012-03-20 13:52 ` Christoph Egger
2012-03-20 16:30 ` Ian Jackson
2012-03-20 16:44 ` Christoph Egger
2012-03-14 13:10 ` Ian Campbell
2012-03-14 13:14 ` Attilio Rao
2012-03-14 14:11 ` Ian Jackson
2012-03-14 14:21 ` Ian Campbell
2012-03-20 11:16 ` Roger Pau Monné
2012-03-20 11:28 ` Attilio Rao
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=4F65111E.8030507@citrix.com \
--to=attilio.rao@citrix.com \
--cc=Ian.Campbell@citrix.com \
--cc=Ian.Jackson@eu.citrix.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).