From: Dario Faggioli <dario.faggioli@citrix.com>
To: merc1984@f-m.fm
Cc: Jan Beulich <JBeulich@suse.com>, Xen-devel@lists.xen.org
Subject: Re: Bug: Compile Fail - v4.4
Date: Wed, 18 Jun 2014 09:59:05 +0200 [thread overview]
Message-ID: <1403078345.16864.268.camel@Solace> (raw)
In-Reply-To: <1403016208.23916.129765593.29296D2B@webmail.messagingengine.com>
[-- Attachment #1.1: Type: text/plain, Size: 2438 bytes --]
On mar, 2014-06-17 at 07:43 -0700, merc1984@f-m.fm wrote:
>
> On Tue, Jun 17, 2014, at 0:51, Jan Beulich wrote:
> > On 16.06.14 at 20:37, <merc1984@f-m.fm>
> > wrote:
> >
> > On Debian Testing, x86_64.
> >
> > I cannot get Xen compiled. I've carefully followed the wiki
> > here:
> > http://wiki.xen.org/wiki/Compiling_Xen_From_Source
> > ... especially WRT dependencies, but no change.
> >
> > You don't mention the most important point here - you're using gcc
> > 4.9.0. A patch for these new warnings was posted already (see
> > http://lists.xenproject.org/archives/html/xen-devel/2014-06/msg01399.html),
> > but in the original shape it wasn't immediately acceptable. An
> > alternative got posted in response a little later. You can pick
> > any (especially if you're not using blktap2), or simply disable
> > building of the blktap code via configure option.
>
> Thank you. Be advised that I got this from the Supported download
> point
> (http://www.xenproject.org/downloads/xen-archives/xen-44-series/xen-440.html), so this is going to keep happening, or users will simply give up.
>
You're right. I tried to ping the discussion containing the proposed fix
already here:
http://lists.xen.org/archives/html/xen-devel/2014-06/msg02065.html
Hopefully, someone will look at the patch soon...
> Also I wish I could make a number of clarifications and updates in the
> wiki, of issues that tripped me up for days.
>
Yeah, please do! Do as Ian said for getting write access and then go
ahead.
Also, next Wednesday is going to be one of our Docs Day:
http://lists.xen.org/archives/html/xen-devel/2014-06/msg02266.html
http://wiki.xenproject.org/wiki/Xen_Document_Days
If you have time, I'd really recommend participating.
In the mean time, if there are issues that you've found in the docs, but
for any reason you can't fix them right away, consider adding them here,
so that they someone can take care of them during the event:
http://wiki.xenproject.org/wiki/Xen_Document_Days/TODO
Regards,
Dario
--
<<This happens because I choose it to happen!>> (Raistlin Majere)
-----------------------------------------------------------------
Dario Faggioli, Ph.D, http://about.me/dario.faggioli
Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK)
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
prev parent reply other threads:[~2014-06-18 7:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-16 18:37 Bug: Compile Fail - v4.4 merc1984
2014-06-17 2:52 ` merc1984
2014-06-17 7:51 ` Jan Beulich
2014-06-17 14:43 ` merc1984
2014-06-17 14:48 ` Ian Campbell
2014-06-18 7:59 ` Dario Faggioli [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=1403078345.16864.268.camel@Solace \
--to=dario.faggioli@citrix.com \
--cc=JBeulich@suse.com \
--cc=Xen-devel@lists.xen.org \
--cc=merc1984@f-m.fm \
/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.