xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Egger <Christoph.Egger@amd.com>
To: Fantu <fantonifabio@tiscali.it>
Cc: xen-devel@lists.xensource.com
Subject: Re: Build error of libxl in xen-unstable changeset 25374
Date: Wed, 23 May 2012 11:14:42 +0200	[thread overview]
Message-ID: <4FBCAA82.1000100@amd.com> (raw)
In-Reply-To: <1337763885533-5709086.post@n5.nabble.com>

On 05/23/12 11:04, Fantu wrote:

> 
> Fantu wrote
>>
>> I have built on clean system with xen-unstable 25374 and stops with this
>> error:
>> gcc  -O1 -fno-omit-frame-pointer -m64 -g -fno-strict-aliasing -std=gnu99
>> -Wall -Wstrict-prototypes -Wdeclaration-after-statement
>> -Wno-unused-but-set-variable   -D__XEN_TOOLS__ -MMD -MF .libxl.o.d 
>> -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -fno-optimize-sibling-calls
>> -Werror -Wno-format-zero-length -Wmissing-declarations
>> -Wno-declaration-after-statement -Wformat-nonliteral -I. -fPIC -pthread
>> -I/mnt/vm/xen/xen-unstable.hg/tools/libxl/../../tools/libxc
>> -I/mnt/vm/xen/xen-unstable.hg/tools/libxl/../../tools/include
>> -I/mnt/vm/xen/xen-unstable.hg/tools/libxl/../../tools/libxc
>> -I/mnt/vm/xen/xen-unstable.hg/tools/libxl/../../tools/include
>> -I/mnt/vm/xen/xen-unstable.hg/tools/libxl/../../tools/xenstore
>> -I/mnt/vm/xen/xen-unstable.hg/tools/libxl/../../tools/include
>> -I/mnt/vm/xen/xen-unstable.hg/tools/libxl/../../tools/blktap2/control
>> -I/mnt/vm/xen/xen-unstable.hg/tools/libxl/../../tools/blktap2/include
>> -I/mnt/vm/xen/xen-unstable.hg/tools/libxl/../../tools/include -include
>> /mnt/vm/xen/xen-unstable.hg/tools/libxl/../../tools/config.h  -c -o
>> libxl.o libxl.c 
>> libxl.c: In function âlibxl_primary_console_execâ:
>> libxl.c:1233:9: error: case value â4294967295â not in enumerated type
>> âlibxl_domain_typeâ [-Werror=switch]
>> cc1: all warnings being treated as errors
>> make[3]: *** [libxl.o] Error 1
>> make[3]: Leaving directory `/mnt/vm/xen/xen-unstable.hg/tools/libxl'
>> make[2]: *** [subdir-install-libxl] Error 2
>> make[2]: Leaving directory `/mnt/vm/xen/xen-unstable.hg/tools'
>> make[1]: *** [subdirs-install] Error 2
>> make[1]: Leaving directory `/mnt/vm/xen/xen-unstable.hg/tools'
>> make: *** [install-tools] Error 2
>>
>> Previous build with changeset 25326 was working
>>
> I have found the bug, is on this patch:
> http://xenbits.xen.org/hg/xen-unstable.hg/rev/8dce7a4121b9
> I tried removing this patch (hg backout -r 25364) solves the problem

See the thread subjected with
'libxl: Introduce LIBXL_DOMAIN_TYPE_INVALID to make gcc happy'

Christoph


-- 
---to satisfy European Law for business letters:
Advanced Micro Devices GmbH
Einsteinring 24, 85689 Dornach b. Muenchen
Geschaeftsfuehrer: Alberto Bozzo, Andrew Bowd
Sitz: Dornach, Gemeinde Aschheim, Landkreis Muenchen
Registergericht Muenchen, HRB Nr. 43632


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

  reply	other threads:[~2012-05-23  9:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-21 12:13 Build error of libxl in xen-unstable changeset 25374 Fantu
2012-05-23  9:04 ` Fantu
2012-05-23  9:14   ` Christoph Egger [this message]
2012-05-23  9:15   ` Dario Faggioli
2012-05-25 14:31   ` cyberhawk001

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=4FBCAA82.1000100@amd.com \
    --to=christoph.egger@amd.com \
    --cc=fantonifabio@tiscali.it \
    --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).