Re: [Xen-devel] xen client initiative compile errors

[Jean Guyader <jean.guyader@xxxxxxxxx>]

The build works on 64 bits machine but with a 32 bits installation (or chroot).

2009/4/3 Ben Guthro <ben.guthro@xxxxxxxxxxxxxxxxxxx>:
> So...what you are saying is that 64bit machines are not currently
> supported by the xen client initiative?
>
> Seems a little restrictive, considering just about every machine sold
> now is 64 bits...
>
> I guess I'll move on to something else.
>
>
> On Fri, 2009-04-03 at 17:58 +0200, Jean Guyader wrote:
>> 2009/4/3 Ben Guthro <ben.guthro@xxxxxxxxxxxxxxxxxxx>:
>> > So...I'm trying to build the xen client initiative code found here:
>> > http://xenbits.xen.org/xenclient/
>> >
>> > However, I'm running into compile errors:
>> >  gcc -I../byterun -DCAML_NAME_SPACE -DNATIVE_CODE -DTARGET_amd64
>> > -DSYS_linux  -O -Wall -D_FILE_OFFSET_BITS=64 -D_REENTRANT
>> > -fno-stack-protector   -c -o signals_asm.o signals_asm.c
>> > signals_asm.c: In function 'segv_handler':
>> > signals_asm.c:188: error: 'REG_CR2' undeclared (first use in this
>> > function)
>> > signals_asm.c:188: error: (Each undeclared identifier is reported only
>> > once
>> > signals_asm.c:188: error: for each function it appears in.)
>> > signals_asm.c:194: error: 'REG_RIP' undeclared (first use in this
>> > function)
>> > signals_asm.c:199: error: 'REG_R14' undeclared (first use in this
>> > function)
>> > signals_asm.c:200: error: 'REG_R15' undeclared (first use in this
>> > function)
>> > make[3]: *** [signals_asm.o] Error 1
>> >
>> > Am I missing something in my build environment that the configure
>> > scripts didn't complain about?
>> > I'm building on Ubuntu 8.04 (gcc 4.2.4)
>> >
>> > Has anyone else run into this issue?
>> >
>>
>> Hi,
>>
>> Yep, you got that because you are using a 64 bits system.
>> Ocaml doesn't like to be compile in 64 bits. Our dom0 is 32 bits and
>> we need 32 bits caml code.
>> The 64 bits version for ocamlopt doesn't support to generate 32 bits
>> code. So we have to compile a 32 bits version of ocamlopt.
>>
>> You definitely need to come with a better solution than that.
>>
>> Thanks,
>
>

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel