From: Mohit Dhingra <mohitdhingras@gmail.com>
To: xen-devel@lists.xensource.com
Subject: Xen Source code build
Date: Sun, 1 Apr 2012 11:04:29 +0530 [thread overview]
Message-ID: <CAGkgU9Ufs_LS-4RQj_3vbe4OognkJqxTCf1mJsUam_Tc0Qoe_g@mail.gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 2935 bytes --]
*Hello All,*
I am a newbie to Linux and Xen. I tried compiling Xen Source code (I want
to make some changes and see how it works), but it failed on my system as
it couldn't find gnu-stubs32.h. Later, on looking at Makefile, I figured
out that for x86_64, it is not yet supported !!
Then I installed "32-bit" emulation utility for x86-64.
and I tried compiling by "linux32" terminal.
Here, I get following error :
make[5]: Entering directory `/srv/xen-4.1.2/tools/blktap/drivers'
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 .block-qcow2.o.d
-D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -mno-tls-direct-seg-refs -Werror
-Wno-unused -I../lib
-I/srv/xen-4.1.2/tools/blktap/drivers/../../../tools/libxc
-I/srv/xen-4.1.2/tools/blktap/drivers/../../../tools/include
-I/srv/xen-4.1.2/tools/blktap/drivers/../../../tools/xenstore
-I/srv/xen-4.1.2/tools/blktap/drivers/../../../tools/include -I
../../libaio/src -I ../../memshr -D_GNU_SOURCE -DUSE_GCRYPT -DMEMSHR -c -o
block-qcow2.o block-qcow2.c
cc1: warnings being treated as errors
block-qcow2.c: In function ‘bdrv_pread’:
block-qcow2.c:238:4: error: format ‘%#llx’ expects type ‘long long unsigned
int’, but argument 5 has type ‘__off_t’
make[5]: *** [block-qcow2.o] Error 1
block-qcow2.c
------------------------------------------------------------------------------------------------------------------
static int bdrv_pread(int fd, int64_t offset, void *buf, int count)
{
int ret;
if (lseek(fd, offset, SEEK_SET) == -1) {
DPRINTF("bdrv_pread failed seek (%#"PRIx64").\n", offset);
return -1;
}
ret = read(fd, buf, count);
if (ret < 0) {
if (lseek(fd, 0, SEEK_END) >= offset) {
DPRINTF("bdrv_pread read failed (%#"PRIx64", END =
%#"PRIx64").\n",
offset, lseek(fd, 0, SEEK_END));
return -1;
}
/* Read beyond end of file. Reading zeros. */
memset(buf, 0, count);
ret = count;
} else if (ret < count) {
/* Read beyond end of file. Filling up with zeros. */
memset(buf + ret, 0, count - ret);
ret = count;
}
return ret;
}
------------------------------------------------------------------------------------------------------------------------
Currently, I have following configuration
cadlab:~/Downloads/xen-4.1.2 # uname -a
Linux cadlab 2.6.37.6-0.11-xen #1 SMP 2011-12-19 23:39:38 +0100 x86_64
x86_64 x86_64 GNU/Linux
And, can I contribute towards 64-bit compatibility on Xen source code build.
*
----------------------------
Thanks & Regards
Mohit Dhingra
*
[-- Attachment #1.2: Type: text/html, Size: 3240 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next reply other threads:[~2012-04-01 5:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-01 5:34 Mohit Dhingra [this message]
2012-04-02 8:56 ` Xen Source code build Ian Campbell
2012-04-02 9:21 ` Olaf Hering
2012-04-07 6:25 ` Mohit Dhingra
2012-04-07 7:30 ` Ian Campbell
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=CAGkgU9Ufs_LS-4RQj_3vbe4OognkJqxTCf1mJsUam_Tc0Qoe_g@mail.gmail.com \
--to=mohitdhingras@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).