Nunca había hecho lo siguiente, me fui a descargar wine-9.0 lo extraje y compilé, pero ahora no se como proceder para que el programa de ajedrez se abra con este wine … ¿podría alguien indicarme algún tutorial o si no es mucho pedir simplemente decirme como debo proceder?.
Tienes que saber la ruta donde se deposito los ejecutables en la compilación, cada compilación tiene su README donde te lo explica. Si ha sido compilado, normalmente estará en la carpeta /opt
Abres una consola o terminal y pones la ruta
~> ruta_completa/wine
O con Thunar vas a esa carpeta y uno o doble clic para ejecutarlo.
Lo pude compilar en Endeavouros pero ya lo desinstalé, frustrate sistema … lo usaba de ‘conejillo de indias’, no quería experimentar aquí en openSUSE, ahora bien, aquí no lo puedo compilar me dice que faltan librerías de 32 bit y no se como se añaden …
keos@localhost:~/Descargas> cd wine-9.0
keos@localhost:~/Descargas/wine-9.0> ./configure
configure: loading site script /usr/share/site/x86_64-pc-linux-gnu
checking build system type... x86_64-pc-linux-gnu
checking host system type... x86_64-pc-linux-gnu
checking whether make sets $(MAKE)... yes
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether the compiler supports GNU C... yes
checking whether gcc accepts -g... yes
checking for gcc option to enable C11 features... none needed
checking for g++... g++
checking whether the compiler supports GNU C++... yes
checking whether g++ accepts -g... yes
checking for g++ option to enable C++11 features... none needed
checking for cpp... cpp
checking for ld... ld
checking whether gcc -m32 works... no
configure: error: Cannot build a 32-bit program, you need to install 32-bit development libraries.
keos@localhost:~/Descargas/wine-9.0>
No se que será ‘el enlace del codigo fuente’ pero aquí te dejo el README:
INTRODUCTION
Wine is a program which allows running Microsoft Windows programs (including DOS,
Windows 3.x, Win32, and Win64 executables) on Unix. It consists of a program loader
which loads and executes a Microsoft Windows binary, and a library (called Winelib) that
implements Windows API calls using their Unix, X11 or Mac equivalents. The library may
also be used for porting Windows code into native Unix executables.
Wine is free software, released under the GNU LGPL; see the file LICENSE for the details.
QUICK START
From the top-level directory of the Wine source (which contains this file), run:
./configure
make
Then either install Wine:
make install
Or run Wine directly from the build directory:
./wine notepad
Run programs as wine program. For more information and problem resolution, read the
rest of this file, the Wine man page, and especially the wealth of information found at https://www.winehq.org.
REQUIREMENTS
To compile and run Wine, you must have one of the following:
Linux version 2.0.36 or later
FreeBSD 12.4 or later
Solaris x86 9 or later
NetBSD-current
Mac OS X 10.8 or later
As Wine requires kernel-level thread support to run, only the operating systems
mentioned above are supported. Other operating systems which support kernel threads
may be supported in the future.
FreeBSD info: See Wine - FreeBSD Wiki for more information.
Solaris info: You will most likely need to build Wine with the GNU toolchain (gcc, gas, etc.).
Warning : installing gas does not ensure that it will be used by gcc. Recompiling gcc afterinstalling gas or symlinking cc, as and ld to the gnu tools is said to be necessary.
NetBSD info: Make sure you have the USER_LDT, SYSVSHM, SYSVSEM, and SYSVMSG
options turned on in your kernel.
Mac OS X info: You need Xcode/Xcode Command Line Tools or Apple cctools. The
minimum requirements for compiling Wine are clang 3.8 with the MacOSX10.10.sdk and
mingw-w64 v8. The MacOSX10.14.sdk and later can only build wine64.
Supported file systems: Wine should run on most file systems. A few compatibility
problems have also been reported using files accessed through Samba. Also, NTFS does
not provide all the file system features needed by some applications. Using a native Unix
file system is recommended.
Basic requirements: You need to have the X11 development include files installed (called
xorg-dev in Debian and libX11-devel in Red Hat). Of course you also need make (most
likely GNU make). You also need flex version 2.5.33 or later and bison.
Optional support libraries: Configure will display notices when optional libraries are not
found on your system. See Wine · Wiki · wine / wine · GitLab for hints
about the packages you should install. On 64-bit platforms, you have to make sure to
install the 32-bit versions of these libraries.
COMPILATION
To build Wine, do:
./configure
make
This will build the program “wine” and numerous support libraries/binaries. The program
“wine” will load and run Windows executables. The library “libwine” (“Winelib”) can be used
to compile and link Windows source code under Unix.
To see compile configuration options, do ./configure --help.
For more information, see Building Wine · Wiki · wine / wine · GitLab
SETUP
Once Wine has been built correctly, you can do make install; this will install the wine
executable and libraries, the Wine man page, and other needed files.
Don’t forget to uninstall any conflicting previous Wine installation first. Try either dpkg -r
wine or rpm -e wine or make uninstall before installing.
Once installed, you can run the winecfg configuration tool. See the Support area at https://www.winehq.org/ for configuration hints.RUNNING PROGRAMS
When invoking Wine, you may specify the entire path to the executable, or a filename
only.
For example, to run Notepad:
wine notepad (using the search Path as specified in
wine notepad.exe the registry to locate the file)
wine c:\windows\notepad.exe (using DOS filename syntax)
wine ~/.wine/drive_c/windows/notepad.exe (using Unix filename syntax)
wine notepad.exe readme.txt (calling program with parameters)
Wine is not perfect, so some programs may crash. If that happens you will get a crash log
that you should attach to your report when filing a bug.
GETTING MORE INFORMATION
WWW: A great deal of information about Wine is available from WineHQ at https:/ www.winehq.org/ : various Wine Guides, application database, bug tracking. This is
probably the best starting point.
FAQ: The Wine FAQ is located at FAQ · Wiki · wine / wine · GitLab
Wiki: The Wine Wiki is located at https://wiki.winehq.org
Gitlab: Wine development is hosted at https://gitlab.winehq.org
Mailing lists: There are several mailing lists for Wine users and developers; see Forums and Mailing Lists · Wiki · wine / wine · GitLab for more information.
Bugs: Report bugs to Wine Bugzilla at https://bugs.winehq.org Please search the
bugzilla database to check whether your problem is already known or fixed before
posting a bug report.
IRC: Online help is available at channel #WineHQ on irc.libera.chat.
Gracias, todo el problema se resolvió instalando wine32, se me ocurrió esta idea al ver que durante la compilacion de este otro Wine (arriba) pedía librerías 32-bits
you need to install 32-bit development libraries.
Doy por solucionado el asunto en este tema, el primero … me pareció el mas apropiado:
Quizás sea una pregunta ingenua pero si instalo lo que indicas arriba y luego compilo este otro wine-9.0, ¿tendría que desinstalar el wine-32 que me da el sistema?, ¿podría usar los dos y ver cual conviene mas sin quitar a ninguno de los dos …?
– el wine32 abre la app pero muy lento.
Me traslado para la otra máquina ya que allí (aquí ahora) no me funcionó/a lo de instalar wine-32
– hago lo que indicas, pero no funciona, también pide las librerías de 32bits aunque …:
keos@localhost:~> zypper se xorg-x11 | grep devel
| xorg-x11-util-devel | Compatibility metapackage for X11 development | paquete
keos@localhost:~>
keos@localhost:~> cd Descargas
keos@localhost:~/Descargas> ls
CHESS-DOWNLOADS logo.png Stardict wine-9.0.tar.xz
E-SWORD pexels-photo-2055389.jpeg wine-9.0
keos@localhost:~/Descargas> cd wine-9.0
keos@localhost:~/Descargas/wine-9.0> ./configure
configure: loading site script /usr/share/site/x86_64-pc-linux-gnu
checking build system type... x86_64-pc-linux-gnu
checking host system type... x86_64-pc-linux-gnu
checking whether make sets $(MAKE)... yes
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether the compiler supports GNU C... yes
checking whether gcc accepts -g... yes
checking for gcc option to enable C11 features... none needed
checking for g++... g++
checking whether the compiler supports GNU C++... yes
checking whether g++ accepts -g... yes
checking for g++ option to enable C++11 features... none needed
checking for cpp... cpp
checking for ld... ld
checking whether gcc -m32 works... no
configure: error: Cannot build a 32-bit program, you need to install 32-bit development libraries.
keos@localhost:~/Descargas/wine-9.0>
Esto es todo muy extraño y a la vez complicado para mi … me puse a ‘traquetear’, a quitar paquetes relacionados con wine y a hacer refresh y dup, reiniciar y venían otros paquetes en Yast, diferentes de los que tenía inicialmente, y así continué, reinicia … hasta que después de muchas maniobras … vienieron los mismos que tengo en la otra máquina (ver captura del otro hilo) y ya me abren aquí las dos app; la verdad, que alguien me explique … !!
Tienes que instalarlo. Además, los paquetes flex y bison. Tambine las librerías de desarrollo de 32 bits, que las tienes en Yast->Instalar software, en la pestaña Patrones->Desarrollo o similar
PD: Puedes probar las ultimas versiones de wine en el repo de emuladores.
No puedo seguir toda esa información, es complicado para mi … me conformo por el momento conque pueda abrir las apps con lo que me salió de esas maniobras escabrosas que hice; asumo que el sistema en actualizará Wine mas adelante, y espero que entonces funcione …