You are not logged in.
I uninstalled wine 1.6.2 and installed wine 1.8.6 from the source tarball using the following method.
Downloaded source tarball from https://dl.winehq.org/wine/source/1.8/ and opened terminal in the downloaded directory.
Installed all the necessary libraries needed for ./configure like gcc 32 bit libraries, flex, bison and Xlib/xfree86l ; and libfreetype6-dev for ./configure --enable-win64
$ sudo ./configure
$ ./configure --enable-win64
$ sudo make && sudo make install
Everything went well, but I am unable to find the wine application. Running wine name.exe returns,
bash: wine: command not found
On the other hand, wine64 is found.
wine64 name.exe
starts the application.
It seems I have a pure wine64 set up. I didn't activate multiarch (below code) at the beginning of installation since I had already done for the previous installations. I thought, once activated, that's enough.
dpkg --add-architecture i386 && apt update
Will redoing the installation, with the above code help me build a WoW64 setup?
Last edited by linux_user (2017-01-09 05:05:14)
"Blind faith to authority is the greatest enemy of truth."
Offline
At the moment, after some .net and gecko installation, wine64 app.exe doesn't run anything. Quite tired of this wine thing. I am looking to uninstall it.
toor@linux:~$ sudo apt-get remove wine64
Reading package lists... Done
Building dependency tree
Reading state information... Done
Package 'wine64' is not installed, so not removed
The following packages were automatically installed and are no longer required:
libc6-dev:i386 libdmx1 libdrm-dev libexpat1-dev libfontenc-dev libfreetype6:i386
libfs-dev libfs6 libice-dev libpciaccess-dev libpixman-1-dev libpng12-0:i386
libpng12-dev:i386 libsm-dev libxcb-dri2-0-dev libxcb-dri3-dev libxcb-glx0-dev
libxcb-present-dev libxcb-randr0-dev libxcb-render0-dev libxcb-shape0-dev
libxcb-sync-dev libxcb-xfixes0-dev libxres1 libxshmfence-dev linux-libc-dev:i386
x11proto-bigreqs-dev x11proto-composite-dev x11proto-damage-dev x11proto-dmx-dev
x11proto-dri2-dev x11proto-dri3-dev x11proto-fixes-dev x11proto-fonts-dev
x11proto-gl-dev x11proto-present-dev x11proto-randr-dev x11proto-record-dev
x11proto-render-dev x11proto-resource-dev x11proto-scrnsaver-dev
x11proto-video-dev x11proto-xcmisc-dev x11proto-xext-dev
x11proto-xf86bigfont-dev x11proto-xf86dga-dev x11proto-xf86dri-dev
x11proto-xf86vidmode-dev x11proto-xinerama-dev zlib1g-dev:i386
Use 'apt-get autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
toor@linux:~$
Not surprising since I installed it from source tarball. Any help in removing wine64/wine completely?
Last edited by linux_user (2017-01-08 20:01:34)
"Blind faith to authority is the greatest enemy of truth."
Offline
I installed it from source tarball. Any help in removing wine64/wine completely?
Go to the source directory and try
sudo make uninstall
If that doesn't work, go through the Makefile to find out where it dropped stuff.
I haven't looked at the tarball myself, ofc
EDIT: Also, in future, *do not* use `sudo` for the ./configure and make steps, it is only needed for the `make install` command.
Last edited by Head_on_a_Stick (2017-01-08 20:06:47)
Offline
Go to the source directory and try
sudo make uninstall
Ok, I have a question. Should the extracted directory be still there in the system after the installation. In my case, I extracted the tar.bz2 to /downloads/ and after I installed, I deleted the folder from /downloads/ much like I do with installers.
Perhaps this is why it doesn't run.
"Blind faith to authority is the greatest enemy of truth."
Offline
Should the extracted directory be still there in the system after the installation.
It doesn't need to be present for the installed binary to run but it is certainly useful if you want to get rid of it
You can just download the tarball again and ./configure it to create the Makefile that will be used when you run `sudo make uninstall`
I don't know why the program doesn't work for you though, sorry.
I would always advise using the repositories rather than source tarballs, for reasons that I'm sure are by now obvious to you...
Offline
Ah I see... however I reinstalled wine (now copied to the /opt/ foder). Running wine64 app.exe for the first time resulted in this,
toor@linux:~/Downloads/HotForex_MT4-SV$ wine64 terminal.exe
err:secur32:SECUR32_initSchannelSP TLS library not found, SSL connections will fail
err:winediag:SECUR32_initNTLMSP ntlm_auth was not found or is outdated. Make sure that ntlm_auth >= 3.0.25 is in your path. Usually, you can find it in the winbind package of your distribution.
fixme:dwmapi:DwmIsCompositionEnabled 0x6d41fd70
fixme:iphlpapi:NotifyIpInterfaceChange (family 0, callback 0x69e6babb, context 0x892e40, init_notify 0, handle 0x122e1f0): stub
fixme:iphlpapi:CancelMibChangeNotify2 (handle (nil)): stub
wine: configuration in '/home/toor/.wine' has been updated.
toor@linux:~/Downloads/HotForex_MT4-SV$
Back to prompt. Nothing happens since then. (Note that terminal.exe is a Windows executable program and not to be confused with shell).
Guess, I'll have to give up and use the repositories.
Last edited by linux_user (2017-01-09 05:15:47)
"Blind faith to authority is the greatest enemy of truth."
Offline
This looks relevant:
err:winediag:SECUR32_initNTLMSP ntlm_auth was not found or is outdated. Make sure that ntlm_auth >= 3.0.25 is in your path. Usually, you can find it in the winbind package of your distribution.
Do you have the winbind package installed?
Offline