Winex (Cedega) CVS installation problems

[ahemp]

I downloaded the CVS of winex and ran the ./tools/wineinstall script that comes with it. It configures, compiles, and does make install alright, I answer the questions asking me where to install it, then it fails to install the registry with "wine: chdir to /home/ahemp/.wine/wineserver-localhost.localdomain : No such file or directory
Registry install failed." If I make the directory manually then it says "wine: '/home/ahemp/.wine/wineserver-localhost.localdomain' must not be accessible by other users." I try to fix this by running "chmod -orwx /home/ahemp/.wine/wineserver-localhost.localdomain/." Then it says permission is denied to the directory! Why does it say that? I just removed the rights for other users to use the directory. I didn't change my rights to it. And why do I even need to make the directory in the first place? Shouldn't the script take care of that?

[vesselinpeev]

Originally Posted by ahemp

I downloaded the CVS of winex and ran the ./tools/wineinstall script that comes with it. It configures, compiles, and does make install alright, I answer the questions asking me where to install it, then it fails to install the registry with "wine: chdir to /home/ahemp/.wine/wineserver-localhost.localdomain : No such file or directory
Registry install failed." If I make the directory manually then it says "wine: '/home/ahemp/.wine/wineserver-localhost.localdomain' must not be accessible by other users." I try to fix this by running "chmod -orwx /home/ahemp/.wine/wineserver-localhost.localdomain/." Then it says permission is denied to the directory! Why does it say that? I just removed the rights for other users to use the directory. I didn't change my rights to it. And why do I even need to make the directory in the first place? Shouldn't the script take care of that?

I went throught he same steps and got the same error. To fix it, I ran "wineserver" (run it only once, or otherwise you'll get another error when running "wine" later), then I ran "wineinstall" again. Once finished with "wineinstall", I ran "wine" and the registry stage seemed to proceed. However, the final result was "Segmentation fault".

However, this seems to be due to Fedora's stack protection technology. It has to be disabled -- I'll have to read up on that and will report here.

I'd be glad if that helps you.

I'm on Fedora Core 3.

[vesselinpeev]

I found the best information here, after searching in other places.
http://www.fedoraforum.org/forum/arc...p/t-26182.html
I followed all steps to disable exec-shield and prelinking, and re-link applications, but couldn't get past the SegFault (and I relinked winex, too, first did "make clean" in the "winex/tools" directory). But the error it's definitely related to protections in Fedora -- newer versions of Wine have workarounds for that, but it seems that the WineX CVS still doesn't have those.

[vesselinpeev]

Everything seems right and I tried some more, but still couldn't get it to work. Disabling the above stuff in Fedora as I found out is the official way according to TransGaming, makers of WineX.
I guess that if you try it on a distro without exec-shield, it would work.

[ahemp]

Okay, I've done your suggestions, but now it hangs during the installation when "Installing Wine Default Registry Entries ... " Thanks for all your help so far. At least there seems to be hope now.

[vesselinpeev]

Ahemp, above I wrote "wineserver" (run it only once, or otherwise you'll get another error when running "wine" later). It's actually "wine" that must not be run more than once, and since "wineinstall" invokes it, after each failed attempt to compile it you need to restart Fedora, type "wineserver" and then "wineinstall".

Now, some more help:

The updated Fedora 3 FAQ does things a bit differently to disable exec-shield.
This is from the current recently updated (after my last post) FAQ at http://www.fedorafaq.org:

13. Q: How do I get Wine to work?

Become root:
su -

Run prelink:
prelink -ua

Edit /etc/sysconfig/prelink. You'll need to change:
PRELINK_OPTS=-mR

to:

PRELINK_OPTS="-m --no-exec-shield"

Then do this to disable exec-shield:
prelink -am --no-exec-shield


You might want to try it this way, to see if it stops to segfault.
I currently don't have the opportunity to try it, but will do it later.

Good luck