I just configured wine with a setup script from a site called sidenet, as this was suggested by a user in another thread. When I attempt to run the installer for photoshop 7 the terminal says:

/usr/bin/wineserver: relocation error: /usr/bin/wineserver: symbol epoll_create, version GLIBC_2.3.2 not defined in file libc.so.6 with link time reference

Part of the problem may be that I pointed the setup script to /usr/bin. What I really wanted was /usr/lib, which is where the wine package installed.

I attempted to run the photoshop installer with the command:
wine /mnt/cdrom/Photo shop 7/Photoshop/setup.exe.
This is definately the right path.

You're not the only one getting this version problem; see:

http://www.linuxquestions.org/questi...hreadid=276532
http://www.linuxquestions.org/questi...hreadid=257639
http://www.linuxquestions.org/questi...hreadid=252670
http://www.linuxquestions.org/questi...hreadid=254035
http://www.linuxquestions.org/questi...hreadid=250503
http://www.linuxquestions.org/questi...hreadid=246622
http://www.linuxquestions.org/questi...hreadid=250147

It looks like there's a problem with the RH9 binary for wine; I suggest downloading the source RPM and recompiling.

I just followed that first link. The thread starter was describing a problem after he installed from an RPM and it was suggested that he try installing from source

Update your glibc to 2.3.2-27.9.7 (last errata one RedHat provided before discontinuing support for RH9).
Actually, update your complete distribution and keep it up to date, else you're just begging to be rooted (and RH9's support is terminated, so please install Fedora Core 3 for new installations instead of RH9).

The 20050111 Wine rpm for RH9 include an explicit dependancy on glibc >= 2.3.2-27.9.7, so it should be more explicit in the future what's the problem.

Sorry but I'm unfamiliar with glibc. What is it and where do I get it from?

Also, I downloaded my wine 20041201 from winehq about 5 days ago and there was not a 2005 wine designed for my system

I had the same problem too with that RPM (20041201-1rh9winehq.i386.rpm) on my RH9. I wouldn't update your glibc as that may pose some other problems with other programs. My suggestion would be to install a previous version. I have just installed 20041019-1rh9winehq.i386.rpm and it worked fine with no problems. You can download is from here:

ftp://rpmfind.net/linux/sourceforge/...inehq.i386.rpm

thanks dave. I tried for an hour or two to uninstall wine, but i couldn't figure it out.
Some sites said "wine -r make uninstall" or something similar.

Are you trying to uninstall a wine RPM?

I'm a little hazy on that. The link I followed to download from winehq.com said "binary and source .rpms for RedHat...". The package installed itself automatically when I clicked on it.

Well, I'm currently not at home in front of my linux box... but I believe if you typed this command:

rpm -qa | grep wine*

It will list the wine package that you have installed, then you can type this command to uninstall it:

rpm -e <wine package name>

Then you should be able to install the version I mentioned to you in the earlier post.

thanks fro your help. I'll try that a little later when I reboot my pc into LInux. Right now I need my windows apps. One more newbie question: how do I get the vertical line? |

The "|" is called the "pipe" and on my computer it is just above the "\"on the same key. Unfortunately, not all keyboards put the "|" in the same place. On my keyboard it looks like two short little vertical pipes one above the other. The "|" is used to redirect the output of one command into another command. In the example that hywaydave gave he is sending the output of the rpm command into the grep command. The grep command will then search for any lines in the output from the rpm command that have the word "wine" in them and only display those lines.

The rpm command is what is Red Hat and Fedora Core and some other versions of Linux usually use to install software which orignally came in the form of an rpm package . The "-qa" parameter after the rpm command tells the rpm command to "query" "all" of the package names which have been installed on the computer. Presumably, wine was one of the rpm packages that had been been installed. Hywaydave is having you use grep so that you will not have to look at too much output about every package ever installed, it will only display the lines that mention "wine." That output should give you the exact name of the original rpm installation file. You you will need to know its name to remove wine. I use Slackware which normally does not use rpm files but I believe the "-e" parameter stands for "erase" to remove an rpm package.

Wine or any other program can be installed either from a precompiled binary RPM package or it can be compiled from source code which can come in the form of an RPM source file or some other format such as a tar file or as a compressed tar file. Both forms have been mentioned in this discussion, so I wanted to make sure that you knew that there is a difference.

wow, you learn something every day. My "pipe" is in the same place. With all this information I should be able to get going as soon as I'm back home on my linux pc.
Once again thanks to all who helped me

Nice. Those commands that hywaydave mentioned worked great. I'm now ready to install a new wine RPM.

Rick485- thanks fro clearing that up. I was uncertain about rpm/source.

hywaydave- When I downloaded my 20041201 RPM the downloads were arranged by architecture. Options werer:
i686
i386
athlon
development package
source

I'm a little hazy on the difference between those top 3 (i686,i386,athlon) but since my PC rund on AMD athlon XP I went for the athlon version. Is that the right thing to do?

I used a downloaded setup script to configure my wine. It created the fake C:/ drive, the config file, etc.. in my home directory. Should I need to do anything with those dettings. I don't recall having to enter whet RPM I was using.

For those experiencing these problems you need to run the up2date program (or use Fedora Core 3 instead of the quite old RH9)