[Pkg-xen-devel] Trying to compile/pack the Xen 4 for Debian fail...

Fri Apr 16 19:20:49 UTC 2010

$ apt-file search libxenctrl.so
libxen3: /usr/lib/libxenctrl.so.3.2
libxen3: /usr/lib/libxenctrl.so.3.2.0
libxen3-dev: /usr/lib/libxenctrl.so
xenner: /usr/lib/xenner/libxenctrl.so.3.2
xenner: /usr/lib/xenner/libxenctrl.so.3.2.0

looks like libxen3-dev is the most likely candidate..

Where did you find this xen-4.0.0 with a debian/ directory?  It does't
look like it came from svn://svn.debian.org/svn/pkg-xen/

Cheers,

C.J.

On Fri, 2010-04-16 at 15:40 -0300, Martinx - ジェームズ wrote:
> Guys,
> 
> 
>  I'm trying to compile the Xen 4.0.0 via debian/rules makefile but I
> got this:
> 
> 
> administrativo at 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 at 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 at 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'
> ......
> 
> 
>  I'm not planning to make this a oficial Debian Xen package but, if
> someone help me, will be great!
>  Thanks in advance!
> 
> 
> Regards,
> Thiago
> 
> 
> _______________________________________________
> Pkg-xen-devel mailing list
> Pkg-xen-devel at lists.alioth.debian.org
> http://lists.alioth.debian.org/mailman/listinfo/pkg-xen-devel

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part
URL: <http://lists.alioth.debian.org/pipermail/pkg-xen-devel/attachments/20100416/5c71d0e3/attachment.pgp>