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

[Sander Bogaert <sander.bogaert@xxxxxxxxx>]

On 11-04-13 12:22, Ian Campbell wrote:
> On Thu, 2013-04-11 at 11:06 +0100, Sander Bogaert wrote:
>> On 11 April 2013 11:25, Ian Campbell <Ian.Campbell@xxxxxxxxxx> wrote:
>>> On Thu, 2013-04-11 at 10:23 +0100, Sander Bogaert wrote:
>>>> I know but my dom0 is Debian wheezy so it has an older version of
>>>> glibc ( I read Wheezy as dom0 is what other have too ).
>>>
>>> If you are building in a Ubuntu environment then you very likely need to
>>> run in an Ubuntu environment too I'm afraid.
>>>
>>> You could try a newer glibc from Debian's experimental repository, but
>>> YMMV using that...
>>>
>>
>> I think that a part of my message got lost again ( I should only reply
>> inline I guess and not append to the mail? )
> 
> Trimming unnecessary quoted material would help.
> 
>> http://lists.xen.org/archives/html/xen-devel/2013-04/msg00772.html
> 
> I see you are trying to use xm here -- xm/xend are not supported on ARM,
> only xl is supported.
> 
>> The glibc thing shouldn't be related to the python issue I think?
> 
> Correct, they are unrelated.
> 
> There should be no python issue because you shouldn't be trying to use
> anything which uses Python (specifically xend) in the first place. The
> tree referenced from the wiki page includes a patch which disables
> building of the python stuff altogether when cross compiling. Perhaps
> you have some stale python stuff installed from your previous attempts
> with another tree?

I just wanted to report the following, it's not a real issue because I
opted to force my wheezy system to a newer glibc. ( which isn't ideal I
know but other solutions failed ).

I use the correct tree and the new branch ( arm-cross2 ) with which the
wiki was updated today. I issue a make mrproper first and then continue
to build the tools:

$ CONFIG_SITE=/etc/dpkg-cross/cross-config.armhf ./configure
--build=x86_64-unknown-linux-gnu --host=arm-linux-gnueabihf
$ make dist-tools CROSS_COMPILE=arm-linux-gnueabihf- XEN_TARGET_ARCH=arm32


It really seems like xend and xm are still build:

$ find ./dist/install/ | grep "xm\|xend"
./dist/install/usr/sbin/xend
./dist/install/usr/sbin/xm
./dist/install/etc/default/xendomains
./dist/install/etc/init.d/xend
./dist/install/etc/init.d/xendomains
./dist/install/etc/udev/rules.d/xend.rules
./dist/install/etc/xen/xend-pci-quirks.sxp
./dist/install/etc/xen/xmexample1
./dist/install/etc/xen/xmexample2
./dist/install/etc/xen/xm-config.xml
./dist/install/etc/xen/xmexample.hvm-stubdom
./dist/install/etc/xen/xmexample.vti
./dist/install/etc/xen/xend-pci-permissive.sxp
./dist/install/etc/xen/xmexample3
./dist/install/etc/xen/xmexample.pv-grub
./dist/install/etc/xen/xend-config.sxp
./dist/install/etc/xen/xmexample.nbd
./dist/install/etc/xen/xmexample.hvm


> 
>> I can start over and deboostrap an Ubuntu system to have the correct
>> glibc, I was just wondering how other solved it ( wiki states people
>> use Wheezy for dom0 a lot)?
> 
> Those people likely aren't cross compiling in an Ubuntu chroot, they are
> probably building natively on an armhf system running Debian.
> 
> Ian.
> 


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