xen compilation error

xen compilation error

[Dulloor]

[-- Attachment #1.1: Type: text/plain, Size: 2688 bytes --]

Hi,

With the latest sources (from yesterday EST), I get the following error :

gcc -I. -I.. -I/data/xen-devel/xen-unstable.hg/tools/ioemu-dir/target-i386
-I/data/xen-devel/xen-unstable.hg/tools/ioemu-dir -MMD -MP -DNEED_CPU_H
-D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE
-I/data/xen-devel/xen-unstable.hg/tools/ioemu-dir/tcg
-I/data/xen-devel/xen-unstable.hg/tools/ioemu-dir/tcg/i386
-I/data/xen-devel/xen-unstable.hg/tools/ioemu-dir/fpu  -DHAS_AUDIO
-DHAS_AUDIO_CHOICE -DHAS_AUDIO
-I/data/xen-devel/xen-unstable.hg//tools/libxc
-I/data/xen-devel/xen-unstable.hg//tools/xenstore
-I/data/xen-devel/xen-unstable.hg//tools/include
-I/data/xen-devel/xen-unstable.hg//tools/blktap/lib -Wall -O2 -g
-fno-strict-aliasing -O2 -fomit-frame-pointer -m32 -march=i686
-fno-strict-aliasing -std=gnu99 -Wall -Wstrict-prototypes -Wno-unused-value
-Wdeclaration-after-statement  -D__XEN_TOOLS__ -MMD -MF .vga.o.d
-D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE
-D_LARGEFILE64_SOURCE -mno-tls-direct-seg-refs -Wno-unused
-Wno-declaration-after-statement -Wno-pointer-sign  -DCONFIG_PASSTHROUGH
-I../hw  -m32 -DUSE_SSE2=1 -msse2 -Wno-unused
-Wno-declaration-after-statement -Wno-pointer-sign  -DCONFIG_PASSTHROUGH  -c
-o vga.o /data/xen-devel/xen-unstable.hg/tools/ioemu-dir/hw/vga.c
/data/xen-devel/xen-unstable.hg/tools/ioemu-dir/hw/vga.c: In function
'xen_vga_populate_vram':
/data/xen-devel/xen-unstable.hg/tools/ioemu-dir/hw/vga.c:2021: error:
storage size of 'xrfp' isn't known
/data/xen-devel/xen-unstable.hg/tools/ioemu-dir/hw/vga.c:2048: error:
'XENMEM_remove_from_physmap' undeclared (first use in this function)
/data/xen-devel/xen-unstable.hg/tools/ioemu-dir/hw/vga.c:2048: error: (Each
undeclared identifier is reported only once
/data/xen-devel/xen-unstable.hg/tools/ioemu-dir/hw/vga.c:2048: error: for
each function it appears in.)
/data/xen-devel/xen-unstable.hg/tools/ioemu-dir/hw/vga.c: In function
'xen_vga_vram_map':
/data/xen-devel/xen-unstable.hg/tools/ioemu-dir/hw/vga.c:2084: warning:
implicit declaration of function 'xc_domain_memory_translate_gpfn_list'
make[5]: *** [vga.o] Error 1
make[5]: Leaving directory
`/data/xen-devel/xen-unstable.hg/tools/ioemu-remote/i386-dm'
make[4]: *** [subdir-i386-dm] Error 2
make[4]: Leaving directory
`/data/xen-devel/xen-unstable.hg/tools/ioemu-remote'
make[3]: *** [subdir-install-ioemu-dir] Error 2
make[3]: Leaving directory `/data/xen-devel/xen-unstable.hg/tools'
make[2]: *** [subdirs-install] Error 2
make[2]: Leaving directory `/data/xen-devel/xen-unstable.hg/tools'
make[1]: *** [install-tools] Error 2
make[1]: Leaving directory `/data/xen-devel/xen-unstable.hg'
make: *** [world] Error 2


thanks
dulloor

[-- Attachment #1.2: Type: text/html, Size: 2839 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

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

Re: xen compilation error

[Keir Fraser]

On 21/01/2009 18:00, "Dulloor" <dulloor@gmail.com> wrote:

> Hi,
> 
> With the latest sources (from yesterday EST), I get the following error :

Your qemu git tree is out of date. Go into qemu-xen-unstable.git and:
 git-pull -a

 -- Keir

Re: xen compilation error

[Ian Jackson]

Keir Fraser writes ("Re: [Xen-devel] xen compilation error"):
> On 21/01/2009 18:00, "Dulloor" <dulloor@gmail.com> wrote:
> > With the latest sources (from yesterday EST), I get the following error :
> 
> Your qemu git tree is out of date. Go into qemu-xen-unstable.git and:
>  git-pull -a

If you haven't done anything to change things, you're likely to find
your copy of qemu-xen-unstable.git as tools/ioemu-remote in your xen
tree.  So:
  cd tools/ioemu-remote
  git-pull

Ian.

Re: xen compilation error

[Christoph Egger]

On Thursday 22 January 2009 13:03:47 Ian Jackson wrote:
> Keir Fraser writes ("Re: [Xen-devel] xen compilation error"):
> > On 21/01/2009 18:00, "Dulloor" <dulloor@gmail.com> wrote:
> > > With the latest sources (from yesterday EST), I get the following error
> > > :
> >
> > Your qemu git tree is out of date. Go into qemu-xen-unstable.git and:
> >  git-pull -a
>
> If you haven't done anything to change things, you're likely to find
> your copy of qemu-xen-unstable.git as tools/ioemu-remote in your xen
> tree.  So:
>   cd tools/ioemu-remote
>   git-pull

This sort of problem can only happen with nested repositories.
(Makes also hard to make snapshots.)
Can we have ioemu back in the mercurial tree, please?


-- 
---to satisfy European Law for business letters:
Advanced Micro Devices GmbH
Karl-Hammerschmidt-Str. 34, 85609 Dornach b. Muenchen
Geschaeftsfuehrer: Jochen Polster, Thomas M. McCoy, Giuliano Meroni
Sitz: Dornach, Gemeinde Aschheim, Landkreis Muenchen
Registergericht Muenchen, HRB Nr. 43632

Re: xen compilation error

[Ian Jackson]

Christoph Egger writes ("Re: [Xen-devel] xen compilation error"):
> This sort of problem can only happen with nested repositories.
> (Makes also hard to make snapshots.)
> Can we have ioemu back in the mercurial tree, please?

I'm afraid it's not really practical to do the necessary
upstream-tracking and multiple branches with hg, particularly given
that almost everyone else in the qemu world is using git.

If you don't like the nested repositories, you can have side-by-side
repositories by setting CONFIG_QEMU in .config (or wherever else you
like to set things).

Alternatively, we could provide a
  make update
at the top-level of xen-unstable.hg which updated qemu too ?

Ian.

Re: xen compilation error

[Christoph Egger]

On Thursday 22 January 2009 13:21:31 Ian Jackson wrote:
> Christoph Egger writes ("Re: [Xen-devel] xen compilation error"):
> > This sort of problem can only happen with nested repositories.
> > (Makes also hard to make snapshots.)
> > Can we have ioemu back in the mercurial tree, please?
>
> I'm afraid it's not really practical to do the necessary
> upstream-tracking and multiple branches with hg, particularly given
> that almost everyone else in the qemu world is using git.

qemu uses subversion and so do I.

Handling patches with mercurial is easy with the pbranch extension:
http://arrenbrecht.ch/mercurial/pbranch/

> If you don't like the nested repositories, you can have side-by-side
> repositories by setting CONFIG_QEMU in .config (or wherever else you
> like to set things).
>
> Alternatively, we could provide a
>   make update
> at the top-level of xen-unstable.hg which updated qemu too ?

That's nice. Also a 'make snapshot' or 'make archive' would be handy to
quickly make a tarball.



-- 
---to satisfy European Law for business letters:
Advanced Micro Devices GmbH
Karl-Hammerschmidt-Str. 34, 85609 Dornach b. Muenchen
Geschaeftsfuehrer: Jochen Polster, Thomas M. McCoy, Giuliano Meroni
Sitz: Dornach, Gemeinde Aschheim, Landkreis Muenchen
Registergericht Muenchen, HRB Nr. 43632

Re: xen compilation error

[Dulloor]

[-- Attachment #1.1: Type: text/plain, Size: 718 bytes --]

'git-pull' was throwing errors. I had to run 'git-pull -f'. From the net I
see that others faced similar problems too.

-dulloor

On Thu, Jan 22, 2009 at 7:03 AM, Ian Jackson <Ian.Jackson@eu.citrix.com>wrote:

> Keir Fraser writes ("Re: [Xen-devel] xen compilation error"):
> > On 21/01/2009 18:00, "Dulloor" <dulloor@gmail.com> wrote:
> > > With the latest sources (from yesterday EST), I get the following error
> :
> >
> > Your qemu git tree is out of date. Go into qemu-xen-unstable.git and:
> >  git-pull -a
>
> If you haven't done anything to change things, you're likely to find
> your copy of qemu-xen-unstable.git as tools/ioemu-remote in your xen
> tree.  So:
>  cd tools/ioemu-remote
>  git-pull
>
> Ian.
>

[-- Attachment #1.2: Type: text/html, Size: 1240 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

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

Re: xen compilation error

[Ian Jackson]

Dulloor writes ("Re: [Xen-devel] xen compilation error"):
> 'git-pull' was throwing errors. I had to run 'git-pull -f'. From the net I
> see that others faced similar problems too.

That's strange.  It suggests our history went backwards or soemthing.
We normally avoid doing that.

Ian.