From: "Martinx - ジェームズ" <thiagocmartinsc@gmail.com>
To: xen-devel <xen-devel@lists.xensource.com>
Subject: Trying to compile Xen 4 for a Debian package fail
Date: Fri, 16 Apr 2010 03:09:59 -0300 [thread overview]
Message-ID: <k2n6b7f6eb1004152309ge3a5e3fueb20abea305c8029@mail.gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 6457 bytes --]
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
[-- Attachment #1.2: Type: text/html, Size: 6964 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
next reply other threads:[~2010-04-16 6:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-16 6:09 Martinx - ジェームズ [this message]
2010-04-16 6:33 ` Trying to compile Xen 4 for a Debian package fail Keir Fraser
2010-04-16 16:31 ` Martinx - ジェームズ
2010-04-16 17:47 ` Keir Fraser
2010-04-16 18:23 ` Martinx - ジェームズ
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=k2n6b7f6eb1004152309ge3a5e3fueb20abea305c8029@mail.gmail.com \
--to=thiagocmartinsc@gmail.com \
--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).