Re: [Xen-devel] Compilation error crossbuilding tools.

[Sander Bogaert <sander.bogaert@xxxxxxxxxxxxx>]

On 10 April 2013 14:34, Ian Campbell <Ian.Campbell@xxxxxxxxxx> wrote:
> On Mon, 2013-04-08 at 11:28 +0100, Stefano Stabellini wrote:
>> On Sat, 6 Apr 2013, Sander Bogaert wrote:
>> > On compilation ( followed the wiki ) I get:
>> > ....
>> > arm-linux-gnueabihf-gcc  -O1 -fno-omit-frame-pointer -marm -g
>> > -fno-strict-aliasing -std=gnu99 -Wall -Wstrict-prototypes
>> > -Wdeclaration-after-statement -Wno-unused-but-set-variable
>> > -Wno-unused-local-typedefs   -D__XEN_TOOLS__ -MMD -MF .block-qcow2.o.d
>> >  -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -fno-optimize-sibling-calls
>> >  -Werror -Wno-unused -I../lib
>> > -I/home/user/source/xen/xen-main/tools/blktap/drivers/../../../tools/libxc
>> > -I/home/user/source/xen/xen-main/tools/blktap/drivers/../../../tools/include
>> > -I/home/user/source/xen/xen-main/tools/blktap/drivers/../../../tools/xenstore
>> > -I/home/user/source/xen/xen-main/tools/blktap/drivers/../../../tools/include
>> > -D_GNU_SOURCE -DMEMSHR -I ../../memshr -pthread  -c -o block-qcow2.o
>> > block-qcow2.c
>> > block-qcow2.c: In function 'bdrv_pread':
>> > block-qcow2.c:238:4: error: format '%llx' expects argument of type
>> > 'long long unsigned int', but argument 5 has type '__off_t'
>> > [-Werror=format]
>> > cc1: all warnings being treated as errors
>> > make[5]: *** [block-qcow2.o] Error 1
>> > make[5]: Leaving directory 
>> > `/home/user/source/xen/xen-main/tools/blktap/drivers'
>> > make[4]: *** [subdir-install-drivers] Error 2
>> > make[4]: Leaving directory `/home/user/source/xen/xen-main/tools/blktap'
>> > make[3]: *** [subdirs-install] Error 2
>> > make[3]: Leaving directory `/home/user/source/xen/xen-main/tools/blktap'
>> > make[2]: *** [subdir-install-blktap] Error 2
>> > make[2]: Leaving directory `/home/user/source/xen/xen-main/tools'
>> > make[1]: *** [subdirs-install] Error 2
>> > make[1]: Leaving directory `/home/user/source/xen/xen-main/tools'
>> > make: *** [install-tools] Error 2
>>
>> Reading the error, I think that the appended patch (completely untested)
>> should fix the problem:
>
> blktap(1) shouldn't even be attempted to build on ARM. My series
> "arm: tools: build for arm64 and enable cross-compiling for both arm32
> and arm64" contains "tools: only build blktap1 on x86".

So does this mean I'm building the tools wrong? I'm in a chroot
described by the wiki and my target arch was set correctly.

>
> That series is a prerequisite for cross building and is not yet applied.
>
> Ian.
>
>

After building the tools and copying them to the image file I again
get some error. First of all, for the newer xl tool the debian wheezy
I debootstrapped missed the correct glibc version.
The wiki says the developpers use debian wheezy so I wonder how you
fixed this issue?

root@x200:~# xl
xl: /lib/arm-linux-gnueabihf/libc.so.6: version `GLIBC_2.15' not found
(required by xl)
xl: /lib/arm-linux-gnueabihf/libc.so.6: version `GLIBC_2.15' not found
(required by /usr/lib/libxenlight.so.2.0)

Because I wanted to move on I tried the xm tool, which complains about
missing modules:
root@x200:~# xm
Traceback (most recent call last):
  File "/usr/sbin/xm", line 5, in <module>
    from xen.xm import main
ImportError: No module named xen.xm

My python path:
['', '/usr/lib/python2.7', '/usr/lib/python2.7/plat-linux2',
'/usr/lib/python2.7/lib-tk', '/usr/lib/python2.7/lib-old',
'/usr/lib/python2.7/lib-dynload',
'/usr/local/lib/python2.7/dist-packages',
'/usr/lib/python2.7/dist-packages']

Searching the filesystem the module was nowhere to be found. Shouldn't
it have build in the chroot when I issued 'make dist-tools'?  I
searched the dist/install directory without result:
...s/source/xen/xen-unstable/dist/install (git)-[guest-smp-3] % find .
| grep "xm\|main.py"
./usr/sbin/xm
./etc/xen/xmexample1
./etc/xen/xmexample2
./etc/xen/xm-config.xml
./etc/xen/xmexample.hvm-stubdom
./etc/xen/xmexample.vti
./etc/xen/xmexample3
./etc/xen/xmexample.pv-grub
./etc/xen/xmexample.nbd
./etc/xen/xmexample.hvm

The module just doesn't seem to be there? I just copied the whole
xensource/dist/install directory to my rootfs.

All of this is based on
http://wiki.xen.org/wiki/Xen_ARM_with_Virtualization_Extensions/CrossCompiling
and I'm really just following the steps and doing some additional
research when they fail. Has anyone actually build the tools following
that guide?

Thanks

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