[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-devel] qemu option


  • To: xen-devel@xxxxxxxxxxxxx
  • From: IAN DELANEY <della5@xxxxxxxxxxxx>
  • Date: Thu, 3 Apr 2014 09:56:07 +0800
  • Delivery-date: Thu, 03 Apr 2014 06:57:50 +0000
  • List-id: Xen developer discussion <xen-devel.lists.xen.org>

It appears that the build of qemu and hvm capable options has gone from
optional to obligatory.

From the gentoo ebuild;

.../app-emulation/xen-tools $ ebuild xen-tools-4.3.2.ebuild clean
install

 * Fixing shebang in usr/sbin/xen-ringwatch
 * Fixing shebang in usr/sbin/xenmon.py
>>> Completed installing xen-tools-4.3.2
>>>    into /mnt/gen2/TmpDir/portage/app-emulation/xen-tools-4.3.2/image/

It completes the build without issue.


Then;

.../app-emulation/xen-tools $ ebuild xen-tools-4.4.0.ebuild clean
install

make[1]: Entering directory
'/mnt/gen2/TmpDir/portage/app-emulation/xen-tools-4.4.0/work/xen-4.4.0/tools'
if test
-d 
/mnt/gen2/TmpDir/portage/app-emulation/xen-tools-4.4.0/work/xen-4.4.0/tools/../tools/qemu-xen
 ;
then \ mkdir -p qemu-xen-dir; \ else \ export GIT=git; \
        
/mnt/gen2/TmpDir/portage/app-emulation/xen-tools-4.4.0/work/xen-4.4.0/tools/../scripts/git-checkout.sh
/mnt/gen2/TmpDir/portage/app-emulation/xen-tools-4.4.0/work/xen-4.4.0/tools/../tools/qemu-xen
qemu-xen-4.4.0 qemu-xen-dir ; \ fi
if test
-d 
/mnt/gen2/TmpDir/portage/app-emulation/xen-tools-4.4.0/work/xen-4.4.0/tools/../tools/qemu-xen
 ;
then \
source=/mnt/gen2/TmpDir/portage/app-emulation/xen-tools-4.4.0/work/xen-4.4.0/tools/../tools/qemu-xen;
\ else \ source=.; \ fi; \
cd qemu-xen-dir; \
$source/configure --enable-xen --target-list=i386-softmmu \
        --enable-debug --enable-trace-backend=stderr \
        --prefix=/usr \
        --source-path=$source \
        
--extra-cflags="-I/mnt/gen2/TmpDir/portage/app-emulation/xen-tools-4.4.0/work/xen-4.4.0/tools/../tools/include
\
-I/mnt/gen2/TmpDir/portage/app-emulation/xen-tools-4.4.0/work/xen-4.4.0/tools/../tools/libxc
\
-I/mnt/gen2/TmpDir/portage/app-emulation/xen-tools-4.4.0/work/xen-4.4.0/tools/../tools/xenstore
\
-I/mnt/gen2/TmpDir/portage/app-emulation/xen-tools-4.4.0/work/xen-4.4.0/tools/../tools/xenstore/compat
\ " \
--extra-ldflags="-L/mnt/gen2/TmpDir/portage/app-emulation/xen-tools-4.4.0/work/xen-4.4.0/tools/../tools/libxc
\
-L/mnt/gen2/TmpDir/portage/app-emulation/xen-tools-4.4.0/work/xen-4.4.0/tools/../tools/xenstore"
\ --bindir=/usr/lib/xen/bin \ --datadir=/usr/share/qemu-xen \
--localstatedir=/var \ --disable-kvm \ --disable-docs \
--disable-guest-agent \ --python=python2.7 \
        ; \
make all

ERROR: pixman not present. Your options:
         (1) Preferred: Install the pixman devel package (any recent
             distro should have packages as Xorg needs pixman too).
         (2) Fetch the pixman submodule, using:
             git submodule update --init pixman

make[2]: Entering directory
'/mnt/gen2/TmpDir/portage/app-emulation/xen-tools-4.4.0/work/xen-4.4.0/tools/qemu-xen-dir'
make[2]: *** No rule to make target 'all'.  Stop. make[2]: Leaving
directory
'/mnt/gen2/TmpDir/portage/app-emulation/xen-tools-4.4.0/work/xen-4.4.0/tools/qemu-xen-dir'
Makefile:178: recipe for target 'subdir-all-qemu-xen-dir' failed
make[1]: *** [subdir-all-qemu-xen-dir] Error 2 make[1]: Leaving
directory
'/mnt/gen2/TmpDir/portage/app-emulation/xen-tools-4.4.0/work/xen-4.4.0/tools' 
/mnt/gen2/TmpDir/portage/app-emulation/xen-tools-4.4.0/work/xen-4.4.0/tools/../tools/Rules.mk:100:
recipe for target 'subdirs-all' failed make: *** [subdirs-all] Error 2
make: Leaving directory
'/mnt/gen2/TmpDir/portage/app-emulation/xen-tools-4.4.0/work/xen-4.4.0/tools'
 * ERROR: app-emulation/xen-tools-4.4.0::gentoo failed (compile phase):
 *   emake failed

pixman is not installed and the 4.3.2 version builds, then the 4.4.0
release fails on configure in the absence of pixman.

The options are;

1. Install pixman, or
2. Install pixman.

On inquiring @ ##xen, I was more confused when a user informed me his
build also failed, but in the 4.3.2 version, in the absence of an
installed pixman, however all things are not equal since he clearly
uses a different distro.  The configure run is presumably different.

It appears the configure options have sustained some re-writing.  It
appears the build dictates a default selection of a qemu / hvm capable
build.  Is this by accident or intent?

See https://bugs.gentoo.org/show_bug.cgi?id=506072

Thx in anticipation.

-- 
kind regards

Ian Delaney

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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.