xen client initiative compile errors
|
View:
New views
9 Messages
—
Rating Filter:
Alert me
|
 |
xen client initiative compile errors
by Ben Guthro-2
::
Rate this Message:
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? B _______________________________________________ Xen-devel mailing list Xen-devel@... http://lists.xensource.com/xen-devel |
|
|
|
|
|
Re: xen client initiative compile errors
by Jean Guyader-2
::
Rate this Message:
The build works on 64 bits machine but with a 32 bits installation (or chroot).
2009/4/3 Ben Guthro <ben.guthro@...>: > 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@...>: >> > 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@... http://lists.xensource.com/xen-devel |
|
|
RE: xen client initiative compile errors
by Ian Pratt-3
::
Rate this Message:
> So...what you are saying is that 64bit machines are not currently
> supported by the xen client initiative? No. XCI uses a 64b Xen with 32b dom0, which is the optimal combination for both size and performance. XenServer and some of the other server distributions of Xen have used this approach successfully for several years -- i.e. it's by far the most widely tested. Ian > 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@...>: > > > 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@... > http://lists.xensource.com/xen-devel _______________________________________________ Xen-devel mailing list Xen-devel@... http://lists.xensource.com/xen-devel |
|
|
RE: xen client initiative compile errors
by Ben Guthro-2
::
Rate this Message:
my mistake, I clearly misunderstood.
I'll try to get over to this build environment, or build up a chroot to test On Fri, 2009-04-03 at 18:40 +0100, Ian Pratt wrote: > > So...what you are saying is that 64bit machines are not currently > > supported by the xen client initiative? > > No. XCI uses a 64b Xen with 32b dom0, which is the optimal combination for both size and performance. XenServer and some of the other server distributions of Xen have used this approach successfully for several years -- i.e. it's by far the most widely tested. > > Ian > > > > 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@...>: > > > > 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@... > > http://lists.xensource.com/xen-devel > _______________________________________________ Xen-devel mailing list Xen-devel@... http://lists.xensource.com/xen-devel |
|
|
Re: xen client initiative compile errors
by Gary Grebus
::
Rate this Message:
On Fri, 2009-04-03 at 11:41 -0400, Ben Guthro wrote:
> 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) It's trying to build a binary using the 32-bit uclibc targeted compiler (from the toolchain build), but it's configured as if building for the 64 bit native environment (-DTARGET_amd64 -DSYS_linux). I tried overriding the ARCH and SYSTEM for that target on the appropriate make command in package/xenclient/ocaml/ocaml.mk but the build failed later trying to run the assembler (running native vs. toolchain version?). At that point I punted and tried building in a 32-bit Fedora 10 environment. It goes wrong later trying to download the version of grub specified in target/x86/grub2/grub2.mk. That version doesn't appear to be on the debian mirrors anymore, so I tried the next newer version: GRUB2_VERSION:=1.96+20090317 Everything built successfully, but then I run into problems executing the last step of the manual install process. The install-bootloader script errors out running grub-install. The grub-install command complains error: cannot seek `/dev/sda' error: cannot seek `/dev/sda' grub-probe: error: no mapping exists for `xenclient-config' ... and stat: invalid option -- c BusyBox v1.13.1 (2009-04-02 20:55:22 EDT) multi-call binary Usage: stat [OPTION] FILE... Display file (default) or filesystem status Options: -f Display filesystem status -L Dereference links -t Display info in terse form I'd guess that's a problem with the different version of grub, but I could had something else wrong too. /gary > > Has anyone else run into this issue? > > B > > > _______________________________________________ > Xen-devel mailing list > Xen-devel@... > http://lists.xensource.com/xen-devel _______________________________________________ Xen-devel mailing list Xen-devel@... http://lists.xensource.com/xen-devel |
|
|
Re: xen client initiative compile errors
by Jean Guyader-2
::
Rate this Message:
2009/4/3 Gary Grebus <ggrebus@...>:
> On Fri, 2009-04-03 at 11:41 -0400, Ben Guthro wrote: >> 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) > > It's trying to build a binary using the 32-bit uclibc targeted compiler > (from the toolchain build), but it's configured as if building for the > 64 bit native environment (-DTARGET_amd64 -DSYS_linux). > > I tried overriding the ARCH and SYSTEM for that target on the > appropriate make command in package/xenclient/ocaml/ocaml.mk but the > build failed later trying to run the assembler (running native vs. > toolchain version?). > > At that point I punted and tried building in a 32-bit Fedora 10 > environment. > > It goes wrong later trying to download the version of grub specified in > target/x86/grub2/grub2.mk. That version doesn't appear to be on the > debian mirrors anymore, so I tried the next newer version: > > GRUB2_VERSION:=1.96+20090317 > > Everything built successfully, but then I run into problems executing > the last step of the manual install process. The install-bootloader > script errors out running grub-install. The grub-install command > complains > > error: cannot seek `/dev/sda' > error: cannot seek `/dev/sda' > grub-probe: error: no mapping exists for `xenclient-config' > > ... and > > stat: invalid option -- c > BusyBox v1.13.1 (2009-04-02 20:55:22 EDT) multi-call binary > > Usage: stat [OPTION] FILE... > > Display file (default) or filesystem status > > Options: > -f Display filesystem status > -L Dereference links > -t Display info in terse form > > > I'd guess that's a problem with the different version of grub, but I > could had something else wrong too. > > /gary > > >> >> Has anyone else run into this issue? >> >> B >> >> Hi, Some other folk got exacly the same error message, I'll try to upgrade the grub version we use. The "cannot seek" error message is harmless, as well as the stat error (busybox doesn't support the -c option). Thanks, -- Jean Guyader _______________________________________________ Xen-devel mailing list Xen-devel@... http://lists.xensource.com/xen-devel |
|
|
|
|
|
Re: xen client initiative compile errors
by Jean Guyader-2
::
Rate this Message:
2009/4/10 ktckd <ktckd9@...>:
> Hi All > > I am trying to build xenclient on Fedora 8(64bit) and ended up getting the > same error. I went through the replies but couldn't figure out much on how > to work around this problem. I have the following questions in mind: > Is there a 32bit oeml installation package? > Do we have to setup 32bit chroot on Fedora8 64bit? If yes, how can we do it? > > I would appreciate it if someone can provide a detailed solution to this > problem? > > Thanks > Hi, Right now the fastest solution would be to setup a 32b chroot. Jean. _______________________________________________ Xen-devel mailing list Xen-devel@... http://lists.xensource.com/xen-devel |
| Free embeddable forum powered by Nabble | Forum Help |
