Hello Stefan,

64 bit guests and hosts are currently under active development.  If you 
feel up to it, you can even help us with it.

Regards,

Michael

Stefan Bayer wrote:
> Thanks for advice,
> just wanted to try the binary version. But as you mention this version seems 
> to be buggy for my box, so I checked out source from svn, adopted configure 
> script to use qt library-dir lib64 instead of lib. But now I get following 
> error:
> ....snip...
> kBuild: Compiling r3/alloc-ef-cpp.cpp
> kBuild: 
> Linking 
> /tmp/install/vbox/out/linux.amd64/release/obj/src/VBox/Runtime/RuntimeEFCPP/RuntimeEFCPP.a
> kBuild: Installing RuntimeEFCPP 
> => /tmp/install/vbox/out/linux.amd64/release/lib/RuntimeEFCPP.a
> kBuild: Compiling string/memcpy_alias.c
> kBuild: Compiling string/memset_alias.c
> kBuild: Compiling math/ceill.asm
> yasm: FATAL: unrecognized object format `elf64'
> kmk[3]: *** 
> [/tmp/install/vbox/out/linux.amd64/release/obj/src/VBox/Runtime/RuntimeR3NoCRTGCC/math/ceill.o]
>  
> Error 1
> kmk[3]: Leaving directory `/tmp/install/vbox/src/VBox/Runtime'
> kmk[2]: *** [pass_libraries_before] Error 2
> kmk[2]: Leaving directory `/tmp/install/vbox/src/VBox'
> kmk[1]: *** [pass_libraries_before] Error 2
> kmk[1]: Leaving directory `/tmp/install/vbox/src'
> kmk: *** [pass_libraries_before] Error 2
> 
> maybe I cannot build a version for my x86_64 box :-(
> 
>> Hi Stefan,
>>
>> On Wednesday 17 January 2007 15:35, Stefan Bayer wrote:
>>> I already had installed glibc-devel package (libc6-dev package does not
>>> exist on openSUSE) which provides /usr/include/sys/ioctl.h. I also found
>>> this file in following directories:
>>>
>>> [...]
>>>
>>> It seems that the script searches on a different directory for that file,
>>> I think.
>> Whoops, right. This issue is fixed (it should not include <sys/ioctl.h> but
>> <linux/ioctl.h>). Just update svn.
>>
>> Kind regards,
>>
>> Frank
> 


_______________________________________________
vbox-users mailing list
[email protected]
http://vbox.innotek.de/mailman/listinfo/vbox-users

Reply via email to