Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Is the LUK available at all for 64-bit?
Using Ubuntu 9.04 64-bit.
I can only find 32-bit binaries on the downloads page and compiling from source with the "make" command gives this:
make -Wall -C /lib/modules/`uname -r`/build SUBDIRS=`pwd` EXTRA_CFLAGS="-I`pwd`/include" modules
make[1]: Entering directory `/usr/src/linux-headers-2.6.28-11-generic'
CC [M] /home/tim/Desktop/unifiedkernel-0.2.4/module/ke/wait.o
In file included from /home/tim/Desktop/unifiedkernel-0.2.4/module/ke/wait.c:33:
/home/tim/Desktop/unifiedkernel-0.2.4/module/include/apc.h:35:28: error: linux/winternl.h: No such file or directory
In file included from /home/tim/Desktop/unifiedkernel-0.2.4/module/include/win32.h:38,
from /home/tim/Desktop/unifiedkernel-0.2.4/module/include/apc.h:39,
from /home/tim/Desktop/unifiedkernel-0.2.4/module/ke/wait.c:33:
/home/tim/Desktop/unifiedkernel-0.2.4/module/include/win32_process.h:34:32: error: linux/win32_thread.h: No such file or directory
make[2]: *** [/home/tim/Desktop/unifiedkernel-0.2.4/module/ke/wait.o] Error 1
make[1]: *** [_module_/home/tim/Desktop/unifiedkernel-0.2.4/module] Error 2
make[1]: Leaving directory `/usr/src/linux-headers-2.6.28-11-generic'
make: *** [default] Error 2
Probably won't be 64 bit, since 64 bit windows is still very new itself... I'm guessing it's 32 bit only, and it will probably stay that way since the majority of windows software is still 32 bit only. Even if you got it running for 64 bit I'm betting the SysWOW isn't there so no 32 bit programs. =S
I don't think it will be even possible in a short term. As far as I know, LUK still use wine for lots of things, though they plan to move some parts of it into the kernel, note that wine itself can't be compiled as a 64 bits program. It works in 64 bits Linuxes, but only because 64 bits linuxes can run 32 bits programs. Wine hasn't been ported to compile on x86_64 natively.
I don't think it will be even possible in a short term. As far as I know, LUK still use wine for lots of things, though they plan to move some parts of it into the kernel, note that wine itself can't be compiled as a 64 bits program. It works in 64 bits Linuxes, but only because 64 bits linuxes can run 32 bits programs. Wine hasn't been ported to compile on x86_64 natively.
You can, but I don't know if the 64 bit compile runs 32bit and 64 bit or just 64 bit windows apps. I think that's probably the main reason they haven't been working much on the 64 bit version, most applications are still 32 bit. =( a lot of development has to come yet.
You can, but I don't know if the 64 bit compile runs 32bit and 64 bit or just 64 bit windows apps. I think that's probably the main reason they haven't been working much on the 64 bit version, most applications are still 32 bit. =( a lot of development has to come yet.
Yes, when you turn the 64 bits option on it won't be able to run regular windows x86 stuff. I heard about this 64 bits stuff, but I was under the impression that wine itself was a 32 bits binary regardless, maybe I was wrong. Still, it seems like it isn't too mature yet.
Source is neither 32bit or 64bit... basically it doesn't matter if you want to make a 64 bit wine but...that is the problem, as it only seems to run 64 bit code so I don't think devlopment will go very far any time soon.
That would be the ideal status of things. The fact is that not all source code compiles in all architectures. Let's take grub as an example, but there are many more. Lots of programs needed some fixes for amd64 when the arch was emerging, I know because Gentoo was in the front line when that happened Most times it was trivial to fix them, just a few minor inconsistencies in the data types to fix some assumptions that the programmers shouldn't have made in the first place. But some others can take more time to fix, and I assume that's why wine hasn't had a 64 bits version at all until very recent times.
Source *can* be arch-specific, the kernel has bits of arch-specific code, for another example. But even when the code is not arch-specific, the 32 vs. 64 bits can arise due to miss-alignments and other problems that can arise due to the different lengths in the data types.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.