WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

[Xen-devel] Trying to compile Xen 4 for a Debian package fail

To: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] Trying to compile Xen 4 for a Debian package fail
From: Martinx - ジェームズ <thiagocmartinsc@xxxxxxxxx>
Date: Fri, 16 Apr 2010 03:09:59 -0300
Delivery-date: Thu, 15 Apr 2010 23:11:36 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:from:date:received :message-id:subject:to:content-type; bh=QF77IUwWMaUHi9AtMr0xyiOQce0IjyJUQ8XekwKaeZs=; b=SJPkFQwwSzh1dy+LRVWWs5KPl2j2udsUcYJX/FX/YJptSpm8tUtDbSLnaJC/yHnzye S+iCM9tKAJwV1JnQTj79ZN8mAma3CHsMjL7qGDxfNQ0GoqYNqfLv5wyoRujdCZPcvlUE 9vDckdkF0DH67dapMjnFm+1fmOPPa9ox8IhWg=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:from:date:message-id:subject:to:content-type; b=G7nwnrP+fSuQHUswkSuQpwVkz35ryJe+uPrkR7hUF9hmByeVBu5joosMHz/Uasgvnd LnoqZS5bp7PPv47lQ4oyo9JVr/0SzZEd0SDWzCnqTDKX0wAK5p5vXFXQqSm8Xd5BPKdX SgaBA90y7+9roIs9HkCJDddqdfsa3atCdvT60=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Guys,

 I'm trying to compile the Xen 4.0.0 via debian/rules makefile but I got this:

administrativo@sid01:~/xen/xen-4/xen-4.0.0$ make -f debian/rules build-tools
.....
make -C lib all
make[7]: Entering directory `/home/administrativo/xen/xen-4/xen-4.0.0/debian/build/build-tools/tools/blktap2/vhd/lib'
make[7]: Nothing to be done for `all'.
make[7]: Leaving directory `/home/administrativo/xen/xen-4/xen-4.0.0/debian/build/build-tools/tools/blktap2/vhd/lib'
make[6]: Leaving directory `/home/administrativo/xen/xen-4/xen-4.0.0/debian/build/build-tools/tools/blktap2/vhd'
gcc -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 .vhd-util.d -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -mno-tls-direct-seg-refs -Werror -Wno-unused -I../include -D_GNU_SOURCE -Wp,-MD,.vhd-util.d -o vhd-util vhd-util.o           -L../../tools/libxc -lxenctrl    -L../../tools/libxc -lxenctrl    -Llib -lvhd -luuid
/usr/bin/ld: cannot find -lxenctrl
collect2: ld returned 1 exit status
make[5]: *** [vhd-util] Error 1
make[5]: Leaving directory `/home/administrativo/xen/xen-4/xen-4.0.0/debian/build/build-tools/tools/blktap2/vhd'
make[4]: *** [subdir-all-vhd] Error 2
make[4]: Leaving directory `/home/administrativo/xen/xen-4/xen-4.0.0/debian/build/build-tools/tools/blktap2'
make[3]: *** [subdirs-all] Error 2
make[3]: Leaving directory `/home/administrativo/xen/xen-4/xen-4.0.0/debian/build/build-tools/tools/blktap2'
make[2]: *** [subdir-all-blktap2] Error 2
make[2]: Leaving directory `/home/administrativo/xen/xen-4/xen-4.0.0/debian/build/build-tools/tools'
make[1]: *** [subdirs-all] Error 2
make[1]: Leaving directory `/home/administrativo/xen/xen-4/xen-4.0.0/debian/build/build-tools/tools'
make: *** [debian/stamps/build-tools] Error 2

 BUT, if I run:

administrativo@sid01:~/xen/xen-4/xen-4.0.0$ make -C debian/build/build-tools/tools/blktap2/vhd
make: Entering directory `/home/administrativo/xen/xen-4/xen-4.0.0/debian/build/build-tools/tools/blktap2/vhd'
make[1]: Entering directory `/home/administrativo/xen/xen-4/xen-4.0.0/debian/build/build-tools/tools/blktap2/vhd'
make -C lib all
make[2]: Entering directory `/home/administrativo/xen/xen-4/xen-4.0.0/debian/build/build-tools/tools/blktap2/vhd/lib'
make[2]: Nothing to be done for `all'.
make[2]: Leaving directory `/home/administrativo/xen/xen-4/xen-4.0.0/debian/build/build-tools/tools/blktap2/vhd/lib'
make[1]: Leaving directory `/home/administrativo/xen/xen-4/xen-4.0.0/debian/build/build-tools/tools/blktap2/vhd'
gcc -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 .vhd-util.d -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -mno-tls-direct-seg-refs -Werror -Wno-unused -I../include -D_GNU_SOURCE -Wp,-MD,.vhd-util.d -o vhd-util vhd-util.o    -Llib -lvhd -luuid
gcc -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 .vhd-update.d -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -mno-tls-direct-seg-refs -Werror -Wno-unused -I../include -D_GNU_SOURCE -Wp,-MD,.vhd-update.d -o vhd-update vhd-update.o    -Llib -lvhd -luuid
make: Leaving directory `/home/administrativo/xen/xen-4/xen-4.0.0/debian/build/build-tools/tools/blktap2/vhd'
administrativo@sid01:~/xen/xen-4/xen-4.0.0$

...it finishes without problems...

 I'm not a programmer so, I appreciate any help...

 The debian/rules file runs the same command, I guess, look:

-- some content of debian/rules:
$(STAMPS_DIR)/build-tools: $(STAMPS_DIR)/setup-tools
        $(MAKE) -C $(DIR)/tools
        touch $@

build-tools:: $(STAMPS_DIR)/build-tools
--

 Also, if I manually run "$(MAKE) -C $(DIR)/tools" from the same subdir as: "make -C debian/build/build-tools/tools" it works too, look:

......
make[6]: Leaving directory `/home/administrativo/xen/xen-4/xen-4.0.0/debian/build/build-tools/tools/blktap2/vhd/lib'
make[5]: Leaving directory `/home/administrativo/xen/xen-4/xen-4.0.0/debian/build/build-tools/tools/blktap2/vhd'
gcc -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 .vhd-util.d -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -mno-tls-direct-seg-refs -Werror -Wno-unused -I../include -D_GNU_SOURCE -Wp,-MD,.vhd-util.d -o vhd-util vhd-util.o    -Llib -lvhd -luuid
gcc -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 .vhd-update.d -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -mno-tls-direct-seg-refs -Werror -Wno-unused -I../include -D_GNU_SOURCE -Wp,-MD,.vhd-update.d -o vhd-update vhd-update.o    -Llib -lvhd -luuid
make[4]: Leaving directory `/home/administrativo/xen/xen-4/xen-4.0.0/debian/build/build-tools/tools/blktap2/vhd'
make[3]: Leaving directory `/home/administrativo/xen/xen-4/xen-4.0.0/debian/build/build-tools/tools/blktap2'
make[3]: Entering directory `/home/administrativo/xen/xen-4/xen-4.0.0/debian/build/build-tools/tools/blktap2'
make -C drivers all
make[4]: Entering directory `/home/administrativo/xen/xen-4/xen-4.0.0/debian/build/build-tools/tools/blktap2/drivers'
Makefile:35: === libgcrypt not installed: falling back to libcrypto ===
make[4]: Nothing to be done for `all'.
make[4]: Leaving directory `/home/administrativo/xen/xen-4/xen-4.0.0/debian/build/build-tools/tools/blktap2/drivers'
make[3]: Leaving directory `/home/administrativo/xen/xen-4/xen-4.0.0/debian/build/build-tools/tools/blktap2'
make[2]: Leaving directory `/home/administrativo/xen/xen-4/xen-4.0.0/debian/build/build-tools/tools/blktap2'
make[1]: Leaving directory `/home/administrativo/xen/xen-4/xen-4.0.0/debian/build/build-tools/tools'
make[1]: Entering directory `/home/administrativo/xen/xen-4/xen-4.0.0/debian/build/build-tools/tools'
make -C libfsimage all
make[2]: Entering directory `/home/administrativo/xen/xen-4/xen-4.0.0/debian/build/build-tools/tools/libfsimage'
......

 Thanks in advance!

Regards,
Thiago
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
<Prev in Thread] Current Thread [Next in Thread>