From: Attilio Rao <attilio.rao@citrix.com>
To: Tim Deegan <tim@xen.org>
Cc: "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: Build failure in OVMF
Date: Thu, 22 Mar 2012 15:20:31 +0000 [thread overview]
Message-ID: <4F6B433F.3070505@citrix.com> (raw)
In-Reply-To: <20120322145559.GJ37468@ocelot.phlegethon.org>
On 22/03/12 14:55, Tim Deegan wrote:
> At 12:59 +0000 on 22 Mar (1332421197), Tim Deegan wrote:
>
>>> cp Build/OvmfX64/DEBUG_GCC44/FV/OVMF.fd ovmf.bin
>>> cp: cannot stat `Build/OvmfX64/DEBUG_GCC44/FV/OVMF.fd': No such file or directory
>>> make[6]: *** [ovmf.bin] Error 1
>>> make[6]: Leaving directory `/local/scratch/tdeegan/xen-unstable.hg/tools/firmware/ovmf-remote'
>>>
> Also, 'make clean' triggers the following code in
> tools/firmware/seabios-dir-remote/tools/test-gcc.sh :
>
> if [ $? -ne 0 ]; then
> echo " Working around no -fwhole-program"> /dev/fd/2
> echo 2
> exit 0
> fi
>
> which truncates std err and mangles my build log. FTW!
>
> # HG changeset patch
> # User Tim Deegan<tim@xen.org>
> # Date 1332428104 0
> # Node ID 6e34d38fda90a3a670fcd231e01d172dee3c3229
> # Parent d5ccb2d1dbd1dce76f9d427073306941d48c3095
> Disable OVMF build - it's not baked yet.
>
> Signed-off-by: Tim Deegan<tim@xen.org>
>
Ack'ed by me.
Attilio
next prev parent reply other threads:[~2012-03-22 15:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-22 12:59 Build failure in OVMF Tim Deegan
2012-03-22 13:07 ` Attilio Rao
2012-03-22 13:15 ` Tim Deegan
2012-03-22 13:58 ` Keir Fraser
2012-03-22 14:08 ` Ian Campbell
2012-03-22 14:48 ` Attilio Rao
2012-03-22 15:23 ` Attilio Rao
2012-03-22 14:55 ` Tim Deegan
2012-03-22 15:04 ` Ian Campbell
2012-03-22 15:16 ` Tim Deegan
2012-03-26 9:37 ` Ian Campbell
2012-03-22 15:20 ` Attilio Rao [this message]
2012-04-02 19:07 ` Jordan Justen
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=4F6B433F.3070505@citrix.com \
--to=attilio.rao@citrix.com \
--cc=tim@xen.org \
--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.