"./configure"? - Question About Wine Installation Opensuse 1

Hello all

I have tried for some time now to make wine work on Opensuse 10.3 x64. My previous attempts on Fedora and Kubuntu worked pretty well...

I have followed all instructions at
http://en.opensuse.org/Wine#Repositories

Installed all needed RPMs
I am able to install wine and I can start winecfg (although it always forgets the mounted "drives") and winefile. Another odd thing is that my ~/.wine folder does not contain a DOS and Windows folder any more after I made a clean re-install...(does Opensuse put these folders somewhere else by default?)

The only piece of information I did not really get on the aforementioned help page was this:

Configure: ./configure --prefix=<where to install wine> --x-libraries=/usr/X11R6/lib --x-includes=/usr/include/X11/ --with-x
[/b]

It seems to be pretty important (since my wine does not want to behave as it should). I am guessing that it is used to make wine use the 32-bit libraries...but WHERE and HOW am I supposed to do this "configure"?

Hi Jens,

You don't need to install Wine this way... there is a package inculded in the YaST -> Software Management.

If you first add the Wine repository using YaST > Community repositories , you can download the latest Wine packages.

After installing just kick off the ' winecfg' command to get your basic setup.
Cheers,
Wj

Hi

Thanks for the reply. This was what I initially did but apparently wine does not run on x64 that well so additional things are needed. The wine installed via Yast or smart does not run correctly. I can start winecfg, winefile and other wine apps via konsole but not install things and they are not included on the program menu or in the file browser (konqueror).

The winecfg also forgets mounted drives when installed via yast or smart. This is why I checked the installation info linked from winehq.
I have now realized that the ./config was something that should be written in the location of an expanded tar file (this could have been explained more in detail, possibly linked to a help section about "make"). Currently running the installation and crossing my fingers...

Nope...that did not work either...

Nope...that did not work either...
[/b]

When installing the OpenSUSE 64bit version I also include the 32bit libraries. Wine runs fine here as packaged. About the mounts not being remembered, I havent neede this setup in combo with a 64bit version, so can't comment on that other then I'll give it a try.

If you want to proceed with the tar -> first ' su - ' to get root rights, unzip the tar if not done so with ' tar zfvx <filename>.tar, cd into the unzipped dir and run the ' ./configure' , make , make install (following the clues in the readme).

Just as an extra note.. the drawback of using tar sources to install is that the uninstall or upgrade process isn't as clean as when using rpm's. Also the software management in YaST won't pick up on what you've installed so things can get messy.

Cheers,
Wj

Thanks for your replies...apparently it has decided not to want to work either way *sighs*.

Too bad. I really like Opensuse in every other aspect.

Hmmm.. well, lets try to get it working then?!

What stage are you at now (with the wine install) and what errors are you getting (if any)?

Do you have the ;
gcc
make
kernel-source
packages installed?

without these configure scripts will run properly seeing they need those packages to have the tools to do their thing.

second : have you tried first installing the 32-bit libraries (in YaST > Software Management select patterns and then 32bit libs).
After having added them try reinstalling the WINE package via Software Management.

If you want to stick with the tar... what stage are you at now?

Cheers,
Wj

I tried the tar file installation and that too had problems.
...so now I installed the kernel-source package (I had not done that before - i did not think that was a requirement) and checked the 32-bit libs.

I re-installed wine via Yats (usually I use Smart because Yats takes a long time scanning the rpm databases)

I still had the same problems as before - wine does not appear on the program menu and is not an option when files are supposed to be executed via Konqueror. winecfg can be started via Konsole and then give these errors:

jenss@jenss:~> winecfg
Warning: the specified Windows directory L"c\windows" is not accessible.
Warning: the specified System directory L"c\windows\\system32" is not accessible.
Warning: could not find DOS drive for current working directory '/home/jenss', starting in the Windows directory.
Warning: the specified Windows directory L"c\windows" is not accessible.
Warning: the specified System directory L"c\windows\\system32" is not accessible.
Warning: could not find DOS drive for current working directory '/', starting in the Windows directory.
err:wineboot:main Cannot set the dir to L"c\windows" (2)
Warning: the specified Windows directory L"c\windows" is not accessible.
Warning: the specified System directory L"c\windows\\system32" is not accessible.
Warning: could not find DOS drive for current working directory '/', starting in the Windows directory.
err:shell:SHGetFolderPathW Failed to create directory L"c\windows\\profiles\\jenss\\Desktop".
err:shell:SHGetFolderPathW Failed to create directory L"c\windows\\profiles\\jenss\\Desktop".
err:winecfg:apply_drive_changes unable to define devicename of 'C:', targetpath of '/home/jenss/.wine/drive_c'
err:winecfg:apply_drive_changes unable to define devicename of 'C:', targetpath of '/home/jenss/.wine/drive_c'
[/b]

I am really confused... wine installed very nicely on x64 versions of both Fedora and Kubuntu.

The last error in the list is when I try to change the drive within the winecfg window... so I can start graphical windows from wine - just that they do not work as they should.

When I try to run winecfg as root I get this error instead:

jenss:~ # winecfg
No protocol specified
No protocol specified
No protocol specified
No protocol specified
Application tried to create a window, but no driver could be loaded.
Make sure that your X server is running and that $DISPLAY is set correctly.
Application tried to create a window, but no driver could be loaded.
Make sure that your X server is running and that $DISPLAY is set correctly.
errle:apartment_createwindowifneeded CreateWindow failed with error 1114
[/b]

For the first errors it could be that there is a cripple wine configuration in your home directory.

If there is a .wine directory in your home folder delete or rename it and retry running winecfg and post the output again if you like.

Getting the error when running as root in a console is normal as far as I know seeing root does not have a X session open so the winecfg dialog can't be opened.

Cheers,
wj

YES!

That worked...although wine is still not integrated as a component accessible from the K/Suse menu or from the konqueror...but now I can start winefile and actually install the programs I need

Great! Thanks!
...although I feel a bit stupid that it was such a simple error....