xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Olaf Hering <olaf@aepfle.de>
To: "Pasi Kärkkäinen" <pasik@iki.fi>
Cc: Ian Jackson <Ian.Jackson@eu.citrix.com>,
	Ian Campbell <Ian.Campbell@citrix.com>,
	xen-devel@lists.xen.org
Subject: Re: Xen 4.2.0-rc2: make tools fails on Fedora 17, ipxe build problems with gcc 4.7
Date: Tue, 14 Aug 2012 16:36:49 +0200	[thread overview]
Message-ID: <20120814143649.GA23135@aepfle.de> (raw)
In-Reply-To: <20120813220734.GU19851@reaktio.net>

On Tue, Aug 14, Pasi Kärkkäinen wrote:

> Hello again,
> 
> So to be able to build Xen 4.2.0-rc2 on Fedora 17 with gcc 4.7 
> I had to apply these three patches to ipxe:
> 
> http://lists.ipxe.org/pipermail/ipxe-devel/2012-March/001279.html
> http://lists.ipxe.org/pipermail/ipxe-devel/2012-March/001280.html
> http://permalink.gmane.org/gmane.network.ipxe.devel/1216

Sorry, I just realized that my xen-unstable rpm package still contains a
patches.tar.gz which is extracted in tools/firmware/etherboot. So I did
not notice the build errors in plain xen-unstable.

Olaf

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

  reply	other threads:[~2012-08-14 14:36 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-13 20:39 Xen 4.2.0-rc2: make tools fails on Fedora 17, ipxe isa.c problem Pasi Kärkkäinen
2012-08-13 21:35 ` Pasi Kärkkäinen
2012-08-13 21:39   ` Pasi Kärkkäinen
2012-08-13 21:44     ` Pasi Kärkkäinen
2012-08-13 22:07       ` Xen 4.2.0-rc2: make tools fails on Fedora 17, ipxe build problems with gcc 4.7 Pasi Kärkkäinen
2012-08-14 14:36         ` Olaf Hering [this message]
2012-08-15  8:42         ` Keir Fraser
2012-08-15 10:18           ` Pasi Kärkkäinen
2012-08-13 22:18   ` Xen 4.2.0-rc2: make tools fails on Fedora 17, ipxe isa.c problem M A Young

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=20120814143649.GA23135@aepfle.de \
    --to=olaf@aepfle.de \
    --cc=Ian.Campbell@citrix.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=pasik@iki.fi \
    --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 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).