I need someone's expertise. I have compiled wine 1.4-1 in a Xubuntu 12.04 beta, running on virtual machine (obviously a 32bit system, since it's VM). Steps i took: Code: 1. installed development packages by running http://winezeug.googlecode.com/svn/trunk/install-wine-deps.sh (as instructed on http://wiki.winehq.org/Wine64) 2. apt-get build-dep wine 3. apt-get install patch libpulse-dev checkinstall 4. ./configure --enable-win64 5. make depend && make 6. checkinstall (which created the .deb package) Everything compiled correctly and seemd OK; I installed the package on Debian Wheezy, again no errors occured. But the command "wine" can't be run, says the command cannot be found. I guess the problem is in the fact it installed into wrong directory. How to overcome this issue?
layr wrote:> I have compiled wine 1.4-1 in a Xubuntu 12.04 beta, running on virtual machine (obviously a 32bit system, since it's VM).Huh? 64 bit VMs are certainly possible.> > > Code: > > 4. ./configure --enable-win64 > >What you built is 64 bit Wine.
Martin Gregorie wrote:> Useful to know: "which wine" or "which wine64" shows if its in $PATHThanks for the tip. Code: laur at debian:~$ which wine64 /usr/local/bin/wine64 So I guess the problem is in the fact wine installed into /usr/local/bin instead of /usr/bin/. Is there any way to change that?
L. Rahyen wrote:> > It looks like you installed it by running "make install".Nope, I created the .deb package under virtual machine and installed it on main system via dpkg -i
> Nope, I created the .deb package under virtual machine and installed it on > main system via dpkg -iTry: ./configure --prefix=/usr ...to set the prefix to /usr instead of /usr/local manually.
L. Rahyen wrote:> > Try: > ./configure --prefix=/usr > ...to set the prefix to /usr instead of /usr/local manually.Just to make sure - I'll compile the .deb again from source by running ./configure --prefix=/usr --enable-win64?
Martin Gregorie, appreciate your input, but I'm afraid I'm not quite following you. etc/profile already contains /usr/local/bin as a PATH variable, so that shouldn't be a problem. Just tried with the modified .deb - it installed wine into usr/bin, but nothing changed for that matter. Code: laur at debian:/$ type wine64 wine64 is hashed (/usr/local/bin/wine64) What would this mean? (PS if anyone happens to have an amd64 architecture .deb package, let me know :D)
Martin Gregorie wrote:> > What does "man type" tell you about it?Code: laur at debian:~$ man type No manual entry for type Martin Gregorie wrote:> I'm running 32bit versions of Linux and wine: since I've got just 4GB of > RAM installed I see no reason to run 64bit versions of anything.I have only 3GB of ram. The reason I want the 64bit version is when I tried installing 32bit 1.2.3 package I had compiled for other system, the installer said it was of a wrong architecture.
What is the type manpage for? Can's see it's relevance to this issue.
Anyway, man builtins returned this for type:
Code:
type [-aftpP] name [name ...]
With no options, indicate how each name would be interpreted if
used as a command name. If the -t option is used, type prints a
string which is one of alias, keyword, function, builtin, or
file if name is an alias, shell reserved word, function,
builtin, or disk file, respectively. If the name is not found,
then nothing is printed, and an exit status of false is
returned. If the -p option is used, type either returns the
name of the disk file that would be executed if name were speci
fied as a command name, or nothing if ``type -t name''
would not
return file. The -P option forces a PATH search for each name,
even if ``type -t name'' would not return file. If a
command is
hashed, -p and -P print the hashed value, not necessarily the
file that appears first in PATH. If the -a option is used, type
prints all of the places that contain an executable named name.
This includes aliases and functions, if and only if the -p
option is not also used. The table of hashed commands is not
consulted when using -a. The -f option suppresses shell func
tion lookup, as with the command builtin. type returns true if
all of the arguments are found, false if any are not found.
Martin, could you share your .deb package? Perhaps the fault lies simply in my
compilations.
layr wrote:> bash: wine: command not found > laur at debian:/usr/bin$ wine64You need both wine-64bit and wine-32bit installed. Otherwise Wine and most windows programs will not work properly. And no, you can run 32-bit Wine on 64-bit system.
Your issue is that you are never compiling the 32-bit component of wine which is required for a vast majority of software that is run in wine. This is what I got out of a conversation with Scott Ritchie (package maintainer of wine in Ubuntu) a few weeks ago and how I build wine. ~/wine-git - git source ~/wine32 - out-of-tree build directory for 32 bit components ~/wine64 - out-of-tree build directory for 64 bit components # Compile the 64 bit components cd ~/wine64 ../wine-git/configure --enable-win64 make # Compile the 32 bit components # Do this from a separate amd64 chroot since multiarch isn't mature enough in the current Pangolin beta to allow all the dev packages for wine in both archs to be installed simultaneously cd ~/wine32 ../wine-git/configure --with-wine64=../wine64 make If you would like to go one step further and build packages, you should package the 32 bit components and 64 bit components separately and then create a dependency between the two packages.
I have builded a shared WoW64 setup as described here http://wiki.winehq.org/Wine64. When I try to install windows application () Code: /opt/wine64/wine /home/taras/Downloads/CiscoIPCommunicatorSetup.exe I get an error:> "The minimum supported processor tu run Cisco IP Communicator is a P3 Pentium-level or compactible processor. The setup will now abort.Code: /opt/wine32/wine /home/taras/Downloads/IE8-WindowsXP-x86-ENU.exe> The installation does not support your system architecture (32/64bits)How can I run application in 32bit mode?