Jump to content


Photo

How do I completely remove Wine?


  • Please log in to reply
34 replies to this topic

#1 Bakshara

Bakshara

    Linux-Noob Member

  • Members
  • PipPip
  • 91 posts

Posted 30 September 2009 - 04:11 AM

I updated to Wine 1.1.30 from 1.1.24. Then when I tried to run files I had ran previously, like APPLEWIN.EXE, I got a tiny dialogue that said, "Wine File" "Error" and an "OK" button. So I uninstalled Wine 1.1.30 and installed Wine 1.1.29. Same error. I uninstalled that and reinstalled Wine 1.1.24. Same error. I uninstalled that and downloaded Wine 1.0.1, because it was labelled "Stable:" Same error.

How do I get rid of Wine entirely so I can go back to Wine 1.1.24 and not have that "Wine File" "Error" mess and operate all the programs I was able to operate previously?

Thanks in advance!
To protect their little egos, they put burritos in their Speedos!

Bakshara the Linux Noob!

#2 hybrid

hybrid

    Linux-Noob Frequent Member

  • Admin
  • PipPipPipPipPipPipPipPip
  • 1,005 posts

Posted 30 September 2009 - 09:56 AM

Which distro is this on and what method did you use to update to Wine 1.1.30 (RPM file, source etc.)?
My website | Portfolio

FOSSwire -- all about free and open source software, featuring tips, tricks, tutorials, reviews, articles and all the latest news from the free software universe.

#3 Bakshara

Bakshara

    Linux-Noob Member

  • Members
  • PipPip
  • 91 posts

Posted 01 October 2009 - 03:02 AM

Which distro is this on and what method did you use to update to Wine 1.1.30 (RPM file, source etc.)?


Umm... by "distro" do you mean Linux Fedora 11?
The files I used to install were:
wine-1.1.30.tar.bz2
wine-1.1.29.tar.bz2
wine-1.1.24.tar.bz2
wine-1.0.1.tar.bz2
For the uninstall of each I did:
sudo yum remove wine*
And when extracting each of those I chose, "Extract here." Then I did:
yum install wine
about half way through it asks,
Total download size: 29 M
Is this ok [y/N]: 
and I answer "Y" every time.

Every time I do an uninstall and a reinstall and I pull up the
Wine Configuration
it always has the same settings I had it set to before I uninstalled it.
To protect their little egos, they put burritos in their Speedos!

Bakshara the Linux Noob!

#4 hybrid

hybrid

    Linux-Noob Frequent Member

  • Admin
  • PipPipPipPipPipPipPipPip
  • 1,005 posts

Posted 01 October 2009 - 09:09 AM

OK, the problem here is that you've mixed up two different ways of installing this bit of software.

You downloaded what appears to be the source packages for Wine, extracted them, but then instructed yum to download a separate copy from the Fedora repositories and install that instead. So you never actually installed the .tar.bz2 files that you downloaded.

If you want to install one of the newer source packages, extract it, cd into the folder and then follow the instructions here.
My website | Portfolio

FOSSwire -- all about free and open source software, featuring tips, tricks, tutorials, reviews, articles and all the latest news from the free software universe.

#5 Bakshara

Bakshara

    Linux-Noob Member

  • Members
  • PipPip
  • 91 posts

Posted 02 October 2009 - 04:11 AM

OK, the problem here is that youve mixed up two different ways of installing this bit of software.

You downloaded what appears to be the source packages for Wine, extracted them, but then instructed yum to download a separate copy from the Fedora repositories and install that instead. So you never actually installed the .tar.bz2 files that you downloaded.

If you want to install one of the newer source packages, extract it, cd into the folder and then follow the instructions here.


Ok, I went to that link and attempted to do that, to no avail.

I did:
[root@Bakshara ~]# ./configure
-bash: ./configure: No such file or directory

I did "Extract Here" of wine-1.1.24 and then I did
yum install wine

Next I did a Filesystem search for wine.

I found wine locked these locations:
/usr/lib
/usr/lib64
/usr/share

In that "Wine" search:
wine-core-1.1.29 <- locked
wine-pulseaudio-1.1.29 <- locked
What are wine 1.1.29 elements still doing there?

Also I am still getting the "Wine File" "Error" mess.
To protect their little egos, they put burritos in their Speedos!

Bakshara the Linux Noob!

#6 Dungeon-Dave

Dungeon-Dave

    Linux-Noob Frequent Member

  • Moderator
  • PipPipPipPipPipPipPip
  • 972 posts

Posted 02 October 2009 - 07:14 PM

As hybrid has mentioned, you're mixing together two separate methods of installing software.

Downloading .tar.bz files, extracting them, running ./configure = manually compiling the packages
"yum install ..." = getting YUM to download pre-compiled packages, then install them using RPM.

This is essentially bringing home a film on DVD, then turning on the TV and watching the same film being broadcast over the airwaves.

It is probably easier to turn on the TV and select the channel you want (yum-install) rather than bring home the DVD then spend some time trying to set up your DVD player, speakers, etc (the ./configure stuff)

#7 Bakshara

Bakshara

    Linux-Noob Member

  • Members
  • PipPip
  • 91 posts

Posted 14 October 2009 - 03:49 AM

OK I am going to attempt to explain this in a much clearer fashion.



I first log in to root

[Bakshara@Bakshara ~]$ su -
Password: 
[root@Bakshara ~]# 
Then I do
[root@Bakshara ~]# sudo yum remove wine*
and it goes through a lot.

Loaded plugins: dellsysidplugin2, refresh-packagekit

...

about 12 pages of uninstall data

...

Transaction Summary

================================================================================

Remove 16 Package(s)
Re-install 0 Package(s)
Downgrade 0 Package(s)

Is this ok [y/N]:

I respond "Y" to remove everything.

Downloading Packages:
Running rpm_check_debug
Running Transaction Test
Finished Transaction Test
Transaction Test Succeeded
Running Transaction


There are 16 line of this type:
Erasing        : wine-???-?.?.??-?.????                                  ?/??
and then:

Removed:
wine.x86_64 0:1.1.29-1.fc11 wine-capi.i586 0:1.1.29-1.fc11
wine-capi.x86_64 0:1.1.29-1.fc11 wine-cms.i586 0:1.1.29-1.fc11
wine-cms.x86_64 0:1.1.29-1.fc11 wine-common.noarch 0:1.1.29-1.fc11
wine-core.i586 0:1.1.29-1.fc11 wine-core.x86_64 0:1.1.29-1.fc11
wine-desktop.noarch 0:1.1.29-1.fc11 wine-fonts.noarch 0:1.1.29-1.fc11
wine-ldap.i586 0:1.1.29-1.fc11 wine-ldap.x86_64 0:1.1.29-1.fc11
wine-pulseaudio.i586 0:1.1.29-1.fc11 wine-pulseaudio.x86_64 0:1.1.29-1.fc11
wine-twain.i586 0:1.1.29-1.fc11 wine-twain.x86_64 0:1.1.29-1.fc11

Complete!


I do that per http://wiki.winehq.org/HowTo where it says,

Before you install Wine, make sure that there is no previous Wine installation on your system, either from a package or from source. If you haven't yet installed Wine, you should be fine. See the Removing old Wine versions chapter in the User Guide for details. Many Linux distributions come with an included Wine package, but due to Wine's rapid development rate these are usually old and often broken versions. It is best to uninstall your distribution's included package versions and update to the latest Wine version available here.


Now I have downloaded
wine-1.1.30.tar.bz2
wine-1.1.29.tar.bz2
wine-1.1.28.tar.bz2
wine-1.1.27.tar.bz2
wine-1.1.26.tar.bz2
wine-1.1.25.tar.bz2
wine-1.1.24.tar.bz2
wine-1.1.23.tar.bz2
wine-1.0.1.tar.bz2

I had wine-1.1.24 installed. I uninstalled it and installed wine-1.1.30.

Every time I have done an install; I first uninstalled as above. Then I click on the wine-1.?.??.tar.bz2 version I wish to install and tell it to extract here.
Then I wind up with the following folders:
tools, server, programs, loader, libs, include, fonts, documentation, dlls
and the following files:
.gitignore, VERSION, README, Makefile.in, Make.rules.in, LICENSE.OLD, LICENSE, COPYING.LIB, configure.ac, configure, config.log, AUTHORS, ANNOUNCE, aclocal.m4

At the
[root@Bakshara ~]#
prompt I enter
yum install wine
to install the version I extracted.

The
./configure
is from austin987 saying, "Did you install from source? Try './configure' first." See http://forum.winehq....p?p=29191#29191 That did not work.

After uninstalling wine-1.1.24 and installing wine-1.1.30 I was getting a tiny error dialog box "Wine File" "Error" on every single EXE file I told wine to run. Even on files the worked perfectly fine under wine-1.1.24.

So, I uninstalled wine-1.1.30 and wine-1.1.29. I had the same problem. I jumped back to wine-1.1.24. That "Wine File" "Error" problem remained. At that time WinHQ said:

Stable: Wine 1.0.1 (shortlog)
Development: Wine 1.1.30 (shortlog)

See http://www.winehq.org/
Therefore I downloaded wine-1.0.1.tar.bz2, uninstalled wine-1.1.24 and installed wine-1.0.1. I was still getting the "Wine File" "Error" problems.

That is when I did the file search and found
wine-core-1.1.29
wine-pulseaudio-1.1.29
both of which are locked. Since I uninstalled every time; why are those two still there and why are they locked?

I hope this helps to explain everything better.

Bakshara
To protect their little egos, they put burritos in their Speedos!

Bakshara the Linux Noob!

#8 Dungeon-Dave

Dungeon-Dave

    Linux-Noob Frequent Member

  • Moderator
  • PipPipPipPipPipPipPip
  • 972 posts

Posted 15 October 2009 - 02:01 PM

Every time I have done an install; I first uninstalled as above. Then I click on the wine-1.?.??.tar.bz2 version I wish to install and tell it to extract here.
Then I wind up with the following folders:
tools, server, programs, loader, libs, include, fonts, documentation, dlls
and the following files:
.gitignore, VERSION, README, Makefile.in, Make.rules.in, LICENSE.OLD, LICENSE, COPYING.LIB, configure.ac, configure, config.log, AUTHORS, ANNOUNCE, aclocal.m4

At the

[root@Bakshara ~]#
prompt I enter
yum install wine
to install the version I extracted.

No - THIS is where you are going wrong. YUM installs packages from HTTP or FTP sources - it does NOT install the version you extracted.

To give you an idea: you have rented a film from the DVD store, then come home and taken the DVD out of its case, then turned your TV over to a film station where the same film is playing. And now you are complaining that the DVD remote control is now rewinding or pausing the film.

Either watch the film on the film station, or watch the DVD in your hand. Either use YUM to install/uninstall from repos, or download the .tar.gz files and COMPILE FROM SOURCE.

If you have extracted the files, you now need to read the README file that was extracted, and follow the instructions within that.

#9 Bakshara

Bakshara

    Linux-Noob Member

  • Members
  • PipPip
  • 91 posts

Posted 16 October 2009 - 03:29 AM

No - THIS is where you are going wrong. YUM installs packages from HTTP or FTP sources - it does NOT install the version you extracted.

To give you an idea: you have rented a film from the DVD store, then come home and taken the DVD out of its case, then turned your TV over to a film station where the same film is playing. And now you are complaining that the DVD remote control is now rewinding or pausing the film.

Either watch the film on the film station, or watch the DVD in your hand. Either use YUM to install/uninstall from repos, or download the .tar.gz files and COMPILE FROM SOURCE.

If you have extracted the files, you now need to read the README file that was extracted, and follow the instructions within that.


No, step back. I have successfully installed whatever version I chose. I am not having any problems installing any version. The problem I am having is removing Wine completely.

As I stated before:
After uninstalling wine I did a search for wine and got
wine-core-1.1.29
wine-pulseaudio-1.1.29
which are both locked.
That shows me that wine was not completely uninstalled. Thus my main question, “How do I completely remove Wine?”

Respectfully,

Bakshara
To protect their little egos, they put burritos in their Speedos!

Bakshara the Linux Noob!

#10 Dungeon-Dave

Dungeon-Dave

    Linux-Noob Frequent Member

  • Moderator
  • PipPipPipPipPipPipPip
  • 972 posts

Posted 16 October 2009 - 09:47 AM

No, step back. I have successfully installed whatever version I chose.

Not according to your previous post(s).

In This post you performed the following steps:

1. downloaded and extracted Wine-1.1.24 locally
2. used YUM to install Wine-1.1.29 from online repos.

In this post you did the following:

1. used YUM to uninstall Wine-1.1.29 (all 16 packages) - but you seemed to think you had 1.1.24 installed
2. downloaded Wine 1.1.23 - 1.1.30 source packages locally
3. extracted one of the local packages (you didn't say which one)
4. used YUM to reinstall from online repos

Now, if you have installed a package WITH YUM from online repos then you can use YUM to uninstall it:
yum erase wine-core
yum erase wine-pulseaudio
If you have extracted and compiled it manually, you will need to remove the files you have compiled to delete it.

As a tip: if you do "rpm -ql | grep -i wine" and it shows any wine packages, use "rpm -e" or "yum erase" to delete them. If the Wine packages don't show up in that list, then you have manually compiled them from source - but from the information in your posts, it looks like you're downloading and extracting the source files, running though the configure... then using yum to ignore the locally-stored extracted packages and install from online repos instead.

Hope that helps. I honestly feel the uninstall issues you are encountering are from your confusion over how something is installed... which means you could be looking in the wrong place to remove it.

#11 Bakshara

Bakshara

    Linux-Noob Member

  • Members
  • PipPip
  • 91 posts

Posted 17 October 2009 - 12:26 AM

Dungeon-Dave,

Now, if you have installed a package WITH YUM from online repos then you can use YUM to uninstall it:

yum erase wine-core
yum erase wine-pulseaudio
If you have extracted and compiled it manually, you will need to remove the files you have compiled to delete it.

As a tip: if you do "rpm -ql | grep -i wine" and it shows any wine packages, use "rpm -e" or "yum erase" to delete them. If the Wine packages don't show up in that list, then you have manually compiled them from source - but from the information in your posts, it looks like you're downloading and extracting the source files, running though the configure... then using yum to ignore the locally-stored extracted packages and install from online repos instead.

Hope that helps. I honestly feel the uninstall issues you are encountering are from your confusion over how something is installed... which means you could be looking in the wrong place to remove it.


Thank you. That seems to be more helpful.

I did the
yum erase wine-core
[root@Bakshara ~]# yum erase wine-core
Loaded plugins: dellsysidplugin2, refresh-packagekit
Setting up Remove Process
No Match for argument: wine-core
Package(s) wine-core available, but not installed.
No Packages marked for removal
yum erase wine-pulseaudio
[root@Bakshara ~]# yum erase wine-pulseaudio
Loaded plugins: dellsysidplugin2, refresh-packagekit
Setting up Remove Process
No Match for argument: wine-pulseaudio
Package(s) wine-pulseaudio available, but not installed.
No Packages marked for removal

rpm -ql | grep -i wine
[root@Bakshara ~]# rpm -ql | grep -i wine
rpm: no arguments given for query
You have new mail in /var/spool/mail/root

So, hopefully this information will be more helpful.

Gratefully,

Bakshara
To protect their little egos, they put burritos in their Speedos!

Bakshara the Linux Noob!

#12 Dungeon-Dave

Dungeon-Dave

    Linux-Noob Frequent Member

  • Moderator
  • PipPipPipPipPipPipPip
  • 972 posts

Posted 19 October 2009 - 09:23 PM

rpm -ql | grep -i wine
So, hopefully this information will be more helpful.

Gratefully,

Bakshara

Doh! Sorry - "rpm -qa | grep -i wine"
the "-l" = list contents of this package. "-qa" = query all, list ALL packages.

#13 Bakshara

Bakshara

    Linux-Noob Member

  • Members
  • PipPip
  • 91 posts

Posted 04 November 2009 - 04:33 AM

Ok,

The latest news. I have successfully removed Wine completely.
I tried to install wine-1.1.24, but it installed wine-1.1.23 instead. I was fine with that. What I really wanted was to document the entire install.

I'm documenting every thing I did to completely uninstall wine at the bottom of this message.*

Now these are the wine bz2 files I had downloaded:
wine-1.1.30
wine-1.1.29
wine-1.1.28
wine-1.1.27
wine-1.1.26
wine-1.1.25
wine-1.1.24
wine-1.1.23
wine-1.1.1

when I did
yum install wine
it installed wine-1.1.29. I uninstalled it. I compressed all but wine-1.1.24 and did
yum install wine
and it installed wine-1.1.29 again. So, I uninstalled it again. I deleted that compressed file and did
yum install wine
again. Once again it installed wine-1.1.29. You can see that the latest distribution on WineHQ is wine-1.1.32.

Dungeon-Dave you said,

No - THIS is where you are going wrong. YUM installs packages from HTTP or FTP sources - it does NOT install the version you extracted.

This is where I am really confused. My latest attempt was to install wine-1.1.24. It is the only version I have download and extracted. wine-1.1.32 is the latest version. Why did it install wine-1.1.29?

My complete uninstall* (I'm not going to put every single one of these in a code bracket.)
rm -f wine-capi-1.1.23-1.fc10.i386.rpm

rm -f wine-cms-1.1.23-1.fc10.i386.rpm
rm -f wine-core-1.1.23-1.fc10.i386.rpm
rm -f wine-desktop-1.1.23-1.fc10.i386.rpm
rm -f wine-esd-1.1.23-1.fc10.i386.rpm
rm -f wine-jack-1.1.23-1.fc10.i386.rpm
rm -f wine-ldap-1.1.23-1.fc10.i386.rpm
rm -f wine-nas-1.1.23-1.fc10.i386.rpm
rm -f wine-pulseaudio-1.1.23-1.fc10.i386.rpm
rm -f wine-tools-1.1.23-1.fc10.i386.rpm
rm -f wine-twain-1.1.23-1.fc10.i386.rpm
rm -f wine-1.1.23-1.fc10.i386.rpm
rm -f /usr/share/selinux/targeted/wine.pp.bz2
rm -f /usr/share/selinux/devel/include/apps/wine.if
rm -f /usr/lib64/openoffice.org3/basis-link/share/template/en-US/layout/lyt-wine.otp
rm -f /usr/lib/wine <- no work
rmdir wine
rm -f /usr/bin/winedump
rm -f /media/LinuxSwitch/Misc/Download/Need2Scan/Linux/WineInstallLog.txt
rm -f /media/LinuxSwitch/Misc/Download/Need2Scan/Linux/WineInstallLog.txt~
rm -f /usr/bin/wineserver
rm -f /media/WINDOZE/windows/$hf_mig$/KB974455-IE8/sp2qfe/wow/winetcpl.cpl
rm -f /media/WINDOZE/windows/system32/dllcache/winetcpl.cpl
rm -f /media/WINDOZE/windows/$hf_mig$/KB974455-IE8/sp2qfe/wow/winetcpl.cpl

[root@Bakshara ~]# cd /var/cache/yum/updates/packages
You have new mail in /var/spool/mail/root
[root@Bakshara packages]# rm -f $HOME/
rm: cannot remove `/root/': Is a directory
[root@Bakshara packages]# rm -f wine-capi-1.1.23-1.fc10.i386.rpm
[root@Bakshara packages]# rm -f wine-cms-1.1.23-1.fc10.i386.rpm
[root@Bakshara packages]# rm -f wine-core-1.1.23-1.fc10.i386.rpm
[root@Bakshara packages]# rm -f wine-desktop-1.1.23-1.fc10.i386.rpm
[root@Bakshara packages]# rm -f wine-esd-1.1.23-1.fc10.i386.rpm
[root@Bakshara packages]# rm -f wine-jack-1.1.23-1.fc10.i386.rpm
[root@Bakshara packages]# rm -f wine-ldap-1.1.23-1.fc10.i386.rpm
[root@Bakshara packages]# rm -f wine-nas-1.1.23-1.fc10.i386.rpm
[root@Bakshara packages]# rm -f wine-pulseaudio-1.1.23-1.fc10.i386.rpm
[root@Bakshara packages]# rm -f wine-tools-1.1.23-1.fc10.i386.rpm
[root@Bakshara packages]# rm -f wine-twain-1.1.23-1.fc10.i386.rpm
[root@Bakshara packages]# rm -f wine-1.1.23-1.fc10.i386.rpm
[root@Bakshara packages]# wineserver -k
wineserver: error while loading shared libraries: libwine.so.1: cannot open shared object file: No such file or directory
[root@Bakshara packages]# cd /usr/share/selinux/targeted
You have new mail in /var/spool/mail/root
[root@Bakshara targeted]# rm -f wine.pp.bz2
[root@Bakshara targeted]# cd /usr/share/selinux/devel/include/apps
[root@Bakshara apps]# rm -f /usr/share/selinux/devel/include/apps/wine.if
[root@Bakshara apps]# rm -f /usr/lib64/openoffice.org3/basis-link/share/template/en-US/layout/lyt-wine.otp
[root@Bakshara apps]# cd /usr/lib
[root@Bakshara lib]# rm -f /usr/lib/wine
rm: cannot remove `/usr/lib/wine': Is a directory
[root@Bakshara lib]# rm -f wine
rm: cannot remove `wine': Is a directory
[root@Bakshara lib]# rmdir wine
[root@Bakshara lib]# rm -f /usr/bin/winedump
[root@Bakshara lib]# rm -f /media/LinuxSwitch/Misc/Download/Need2Scan/Linux/WineInstallLog.txt
[root@Bakshara lib]# rm -f /media/LinuxSwitch/Misc/Download/Need2Scan/Linux/WineInstallLog.txt~
[root@Bakshara lib]# rm -f /usr/bin/wineserver
[root@Bakshara lib]# rm -f /media/WINDOZE/windows/$hf_mig$/KB974455-IE8/sp2qfe/wow/winetcpl.cpl
[root@Bakshara lib]# rm -f /media/WINDOZE/windows/system32/dllcache/winetcpl.cpl
[root@Bakshara lib]# rm -f /media/WINDOZE/windows/$hf_mig$/KB974455-IE8/sp2qfe/wow/winetcpl.cpl
[root@Bakshara lib]#

I did a search Applications
Under Applications I saw:
Main Menu
I opened that an inside it I saw several instances of Wine Application and a few winebrowser. It would not let me perform a group delete. I had to delete those each one by one.
Under /home/Bakshara was .wine and .winetrickscache I deleted those.
After all of this I believe Wine was completely GONE.
To protect their little egos, they put burritos in their Speedos!

Bakshara the Linux Noob!

#14 Dungeon-Dave

Dungeon-Dave

    Linux-Noob Frequent Member

  • Moderator
  • PipPipPipPipPipPipPip
  • 972 posts

Posted 04 November 2009 - 02:25 PM

This is where I am really confused. My latest attempt was to install wine-1.1.24. It is the only version I have download and extracted. wine-1.1.32 is the latest version. Why did it install wine-1.1.29?

The answer has been specified several times in previous posts. You even quoted it above this question:

No - THIS is where you are going wrong. YUM installs packages from HTTP or FTP sources - it does NOT install the version you extracted.

To install the version you extracted, you will need to compile it manually.

The way you are using YUM means it is ignoring your downloaded packages and fetching wine-1.1.29 from fedora's repos.

#15 Bakshara

Bakshara

    Linux-Noob Member

  • Members
  • PipPip
  • 91 posts

Posted 04 November 2009 - 03:59 PM


This is where I am really confused. My latest attempt was to install wine-1.1.24. It is the only version I have download and extracted. wine-1.1.32 is the latest version. Why did it install wine-1.1.29?

The answer has been specified several times in previous posts. You even quoted it above this question:

No - THIS is where you are going wrong. YUM installs packages from HTTP or FTP sources - it does NOT install the version you extracted.

To install the version you extracted, you will need to compile it manually.

The way you are using YUM means it is ignoring your downloaded packages and fetching wine-1.1.29 from fedora's repos.


Thank you!
Two questions:
1) How do I do that? How do I compile it manually?
2) Why does it fetch wine-1.1.29 and not the latest wine-1.1.32?
To protect their little egos, they put burritos in their Speedos!

Bakshara the Linux Noob!

#16 Dungeon-Dave

Dungeon-Dave

    Linux-Noob Frequent Member

  • Moderator
  • PipPipPipPipPipPipPip
  • 972 posts

Posted 04 November 2009 - 04:05 PM

Thank you!
Two questions:
1) How do I do that? How do I compile it manually?

I refer you back to my previous post:

If you have extracted the files, you now need to read the README file that was extracted, and follow the instructions within that.

2) Why does it fetch wine-1.1.29 and not the latest wine-1.1.32?

Because that is what will have been compiled and placed on the repos:
Dependencies Resolved

=============================================================================
 Package                 Arch       Version          Repository        Size
=============================================================================
Installing:
 wine                    i386       1.0-0.3.rc3.fc7  updates            21 k
Installing for dependencies:
 wine-capi               i386       1.0-0.3.rc3.fc7  updates            26 k
 wine-cms                i386       1.0-0.3.rc3.fc7  updates            41 k
 wine-core               i386       1.0-0.3.rc3.fc7  updates            11 M
 wine-esd                i386       1.0-0.3.rc3.fc7  updates            35 k
 wine-jack               i386       1.0-0.3.rc3.fc7  updates            37 k
 wine-ldap               i386       1.0-0.3.rc3.fc7  updates            89 k
 wine-nas                i386       1.0-0.3.rc3.fc7  updates            24 k
 wine-tools              i386       1.0-0.3.rc3.fc7  updates           601 k
 wine-twain              i386       1.0-0.3.rc3.fc7  updates            47 k

Transaction Summary
=============================================================================
Install     10 Package(s)
Update       0 Package(s)
Remove       0 Package(s)

Total download size: 12 M
Is this ok [y/N]:
So for my Fedora7 repo, the version available to me is 1.0-0.3. For your release of Fedora, the repos have a later version (but not the very latest).

#17 Bakshara

Bakshara

    Linux-Noob Member

  • Members
  • PipPip
  • 91 posts

Posted 27 November 2009 - 09:22 PM

Ok I did this:

If you have extracted the files, you now need to read the README file that was extracted, and follow the instructions within that.

...per WineOn64bit (Building Wine on Fedora 11 x86_64)

It did a whole bunch of stuff. Then I did:
./configure

This is the response I got:

[root@Bakshara ~]# ./configure
-bash: ./configure: No such file or directory
[root@Bakshara ~]#

I have no Wine menu. What else do I need to do?

Thanks in advance
To protect their little egos, they put burritos in their Speedos!

Bakshara the Linux Noob!

#18 hybrid

hybrid

    Linux-Noob Frequent Member

  • Admin
  • PipPipPipPipPipPipPipPip
  • 1,005 posts

Posted 28 November 2009 - 10:09 AM


[root@Bakshara ~]# ./configure
-bash: ./configure: No such file or directory
[root@Bakshara ~]#

I have no Wine menu. What else do I need to do?

Thanks in advance


I think you ran ./configure from the wrong directory. If you notice in the prompt, it says: root@Bakshara ~]. That '~' indicates you were in the home directory (for root, since that's who you were logged in as). You will first need to use cd to move into the directory where the extracted wine files are, before ./configure will work.

For example, if the extracted files are on the desktop of a user named bakshara:

cd /home/bakshara/Desktop/wine-1.1.32/
./configure

and then continue to follow the README instructions from after the ./configure stage.
My website | Portfolio

FOSSwire -- all about free and open source software, featuring tips, tricks, tutorials, reviews, articles and all the latest news from the free software universe.

#19 Bakshara

Bakshara

    Linux-Noob Member

  • Members
  • PipPip
  • 91 posts

Posted 23 February 2010 - 03:45 AM

Ok, it's been a while, but I am back and have given it a serious go.

I found this site that is VERY helpful. The one adjustment, you may have to make, is where it says, "2) The source code for Wine will be stored in a folder named "wine". Type cd wine press Enter." go to the directory where ever you download whatever version of Wine.
http://wiki.oldos.org/Linux/WineHowTo

Then I followed all of the instructions step-by-step. The following is the response I got:

[Bakshara@Bakshara wine-1.1.24]$ ./tools/wineinstall
Wine Installer v1.0

Running configure...

checking build system type... x86_64-unknown-linux-gnu
checking host system type... x86_64-unknown-linux-gnu
checking whether make sets $(MAKE)... yes
checking for gcc... no
checking for cc... no
checking for cl.exe... no
configure: error: in `/media/LinuxSwitch/Misc/Download/Need2Scan/Linux/wine-1.1.24':
configure: error: no acceptable C compiler found in $PATH
See `config.log' for more details.

Configure failed, aborting install.


What do I need to do to address the "error: no acceptable C compiler found in $PATH" issue?

Thanks for all your help!
P.S. Is it possible to to install and operate two versions of Wine?
To protect their little egos, they put burritos in their Speedos!

Bakshara the Linux Noob!

#20 hybrid

hybrid

    Linux-Noob Frequent Member

  • Admin
  • PipPipPipPipPipPipPipPip
  • 1,005 posts

Posted 23 February 2010 - 09:02 AM

Presuming you're still using Fedora as you were in the first post in this thread, you need to use this command to install the software development tools:

su -
[[enter your root password when prompted]]
yum groupinstall "Development Tools" "Legacy Software Development"

My website | Portfolio

FOSSwire -- all about free and open source software, featuring tips, tricks, tutorials, reviews, articles and all the latest news from the free software universe.

#21 Bakshara

Bakshara

    Linux-Noob Member

  • Members
  • PipPip
  • 91 posts

Posted 28 February 2010 - 04:36 AM

Presuming you're still using Fedora as you were in the first post in this thread, you need to use this command to install the software development tools:

su -
[[enter your root password when prompted]]
yum groupinstall "Development Tools" "Legacy Software Development"


Ok, I did that. There was a huge long process of installing the "C compiler." I then did:

[Bakshara@Bakshara ~]$ cd /media/LinuxSwitch/Misc/Download/Need2Scan/Linux/wine-1.1.24
[Bakshara@Bakshara wine-1.1.24]$ ./tools/wineinstall
Wine Installer v1.0

Running configure...

checking build system type... x86_64-unknown-linux-gnu
checking host system type... x86_64-unknown-linux-gnu
checking whether make sets $(MAKE)... yes
checking for gcc... gcc
checking for C compiler default output file name...
configure: error: in `/media/LinuxSwitch/Misc/Download/Need2Scan/Linux/wine-1.1.24':
configure: error: C compiler cannot create executables
See `config.log' for more details.

Configure failed, aborting install.
[Bakshara@Bakshara wine-1.1.24]$


I checked "config.log" and this is the info I gave me:

This file contains any messages produced by compilers while
running configure, to aid debugging if configure makes a mistake.

It was created by Wine configure 1.1.24, which was
generated by GNU Autoconf 2.63. Invocation command line was

$ ./configure

## --------- ##
## Platform. ##
## --------- ##

hostname = Bakshara
uname -m = x86_64
uname -r = 2.6.30.10-105.2.23.fc11.x86_64
uname -s = Linux
uname -v = #1 SMP Thu Feb 11 07:06:34 UTC 2010

/usr/bin/uname -p = unknown
/bin/uname -X = unknown

/bin/arch = x86_64
/usr/bin/arch -k = unknown
/usr/convex/getsysinfo = unknown
/usr/bin/hostinfo = unknown
/bin/machine = unknown
/usr/bin/oslevel = unknown
/bin/universe = unknown

PATH: /usr/lib64/qt-3.3/bin
PATH: /usr/kerberos/sbin
PATH: /usr/kerberos/bin
PATH: /usr/lib64/ccache
PATH: /usr/local/bin
PATH: /usr/bin
PATH: /bin
PATH: /usr/local/sbin
PATH: /usr/sbin
PATH: /sbin
PATH: /home/Bakshara/bin


## ----------- ##
## Core tests. ##
## ----------- ##

configure:2289: checking build system type
configure:2307: result: x86_64-unknown-linux-gnu
configure:2329: checking host system type
configure:2344: result: x86_64-unknown-linux-gnu
configure:2379: checking whether make sets $(MAKE)
configure:2401: result: yes
configure:2458: checking for gcc
configure:2474: found /usr/lib64/ccache/gcc
configure:2485: result: gcc
configure:2717: checking for C compiler version
configure:2725: gcc --version >&5
gcc (GCC) 4.4.1 20090725 (Red Hat 4.4.1-2)
Copyright © 2009 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

configure:2729: $? = 0
configure:2736: gcc -v >&5
Using built-in specs.
Target: x86_64-redhat-linux
Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --with-bugurl=http://bugzilla.redhat.com/bugzilla --enable-bootstrap --enable-shared --enable-threads=posix --enable-checking=release --with-system-zlib --enable-__cxa_atexit --disable-libunwind-exceptions --enable-languages=c,c++,objc,obj-c++,java,fortran,ada --enable-java-awt=gtk --disable-dssi --enable-plugin --with-java-home=/usr/lib/jvm/java-1.5.0-gcj-1.5.0.0/jre --enable-libgcj-multifile --enable-java-maintainer-mode --with-ecj-jar=/usr/share/java/eclipse-ecj.jar --disable-libjava-multilib --with-ppl --with-cloog --with-tune=generic --with-arch_32=i586 --build=x86_64-redhat-linux
Thread model: posix
gcc version 4.4.1 20090725 (Red Hat 4.4.1-2) (GCC)
configure:2740: $? = 0
configure:2747: gcc -V >&5
gcc: '-V' option must have argument
configure:2751: $? = 1
configure:2774: checking for C compiler default output file name
configure:2796: gcc conftest.c >&5
/usr/bin/ld: skipping incompatible /usr/lib/gcc/x86_64-redhat-linux/4.4.1/../../../libc.so when searching for -lc
/usr/bin/ld: skipping incompatible /usr/lib/libc.so when searching for -lc
/usr/bin/ld: cannot find -lc
collect2: ld returned 1 exit status
configure:2800: $? = 1
configure:2838: result:
configure: failed program was:
| /* confdefs.h. */
| #define PACKAGE_NAME "Wine"
| #define PACKAGE_TARNAME "wine"
| #define PACKAGE_VERSION "1.1.24"
| #define PACKAGE_STRING "Wine 1.1.24"
| #define PACKAGE_BUGREPORT "wine-devel@winehq.org"
| /* end confdefs.h. */
|
| int
| main ()
| {
|
| ;
| return 0;
| }
configure:2844: error: in `/media/LinuxSwitch/Misc/Download/Need2Scan/Linux/wine-1.1.24':
configure:2847: error: C compiler cannot create executables
See `config.log' for more details.

## ---------------- ##
## Cache variables. ##
## ---------------- ##

ac_cv_build=x86_64-unknown-linux-gnu
ac_cv_env_CCC_set=
ac_cv_env_CCC_value=
ac_cv_env_CC_set=
ac_cv_env_CC_value=
ac_cv_env_CFLAGS_set=
ac_cv_env_CFLAGS_value=
ac_cv_env_CPPFLAGS_set=
ac_cv_env_CPPFLAGS_value=
ac_cv_env_CPP_set=
ac_cv_env_CPP_value=
ac_cv_env_CXXFLAGS_set=
ac_cv_env_CXXFLAGS_value=
ac_cv_env_CXX_set=
ac_cv_env_CXX_value=
ac_cv_env_LDFLAGS_set=
ac_cv_env_LDFLAGS_value=
ac_cv_env_LIBS_set=
ac_cv_env_LIBS_value=
ac_cv_env_XMKMF_set=
ac_cv_env_XMKMF_value=
ac_cv_env_build_alias_set=
ac_cv_env_build_alias_value=
ac_cv_env_host_alias_set=
ac_cv_env_host_alias_value=
ac_cv_env_target_alias_set=
ac_cv_env_target_alias_value=
ac_cv_host=x86_64-unknown-linux-gnu
ac_cv_prog_ac_ct_CC=gcc
ac_cv_prog_make_make_set=yes

## ----------------- ##
## Output variables. ##
## ----------------- ##

ALL_DLL_DIRS=''
ALL_IMPLIB_DIRS=''
ALL_MAKEFILES=''
ALL_MAKEFILE_DEPENDS=''
ALL_MAKERULES=''
ALL_PROGRAM_BIN_INSTALL_DIRS=''
ALL_PROGRAM_DIRS=''
ALL_PROGRAM_INSTALL_DIRS=''
ALL_TEST_DIRS=''
ALL_TOP_DIRS=''
ALL_WINETEST_DEPENDS=''
ALSALIBS=''
AR=''
ARFLAGS=''
AUDIOIOLIBS=''
BISON=''
BUILTINFLAG=''
CARBONLIB=''
CC='gcc'
CFLAGS=''
COREAUDIO=''
COREFOUNDATIONLIB=''
CPP=''
CPPBIN=''
CPPFLAGS=''
CROSSCC=''
CROSSTARGETFLAGS=''
CROSSTEST=''
CRTLIBS=''
CUPSINCL=''
CXX=''
CXXFLAGS=''
DEFS=''
DEPENDENCIES=''
DISKARBITRATIONLIB=''
DLLEXT=''
DLLFLAGS=''
DLLTOOL=''
DLLWRAP=''
ECHO_C=''
ECHO_N='-n'
ECHO_T=''
EGREP=''
ESDCONFIG=''
ESDINCL=''
ESDLIBS=''
EXEEXT=''
EXTRACFLAGS=''
EXTRA_BINARIES=''
FLEX=''
FONTCONFIGINCL=''
FONTFORGE=''
FREETYPEINCL=''
FREETYPELIBS=''
GNUTLSINCL=''
GPHOTO2INCL=''
GPHOTO2LIBS=''
GREP=''
HALINCL=''
ICOTOOL=''
IMPLIBEXT=''
INSTALL_DATA=''
INSTALL_PROGRAM=''
INSTALL_SCRIPT=''
IOKITLIB=''
LCMSLIBS=''
LDAPLIBS=''
LDCONFIG=''
LDD=''
LDDLLFLAGS=''
LDEXECFLAGS=''
LDFLAGS=''
LDPATH=''
LDRPATH_INSTALL=''
LDRPATH_LOCAL=''
LDSHARED=''
LIBDL=''
LIBEXT=''
LIBKSTAT=''
LIBOBJS=''
LIBPOLL=''
LIBPTHREAD=''
LIBS=''
LINT=''
LINTFLAGS=''
LN=''
LN_S=''
LTLIBOBJS=''
MAINTAINER_MODE='#'
MINGWAR=''
NASLIBS=''
OBJEXT=''
OPENGL_LIBS=''
PACKAGE_BUGREPORT='wine-devel@winehq.org'
PACKAGE_NAME='Wine'
PACKAGE_STRING='Wine 1.1.24'
PACKAGE_TARNAME='wine'
PACKAGE_VERSION='1.1.24'
PATH_SEPARATOR=':'
PKG_CONFIG=''
PNGINCL=''
PRELINK=''
RANLIB=''
RESOLVLIBS=''
RSVG=''
SANEINCL=''
SECURITYLIB=''
SET_MAKE=''
SHELL='/bin/sh'
SOCKETLIBS=''
STRIP=''
TARGETFLAGS=''
TOOLSDIR=''
WIN16_FILES=''
WIN16_INSTALL=''
XLIB=''
XMKMF=''
XML2INCL=''
XML2LIBS=''
XSLTINCL=''
X_CFLAGS=''
X_EXTRA_LIBS=''
X_LIBS=''
X_PRE_LIBS=''
ZLIB=''
ac_ct_AR=''
ac_ct_CC='gcc'
ac_ct_CXX=''
bindir='${exec_prefix}/bin'
build='x86_64-unknown-linux-gnu'
build_alias=''
build_cpu='x86_64'
build_os='linux-gnu'
build_vendor='unknown'
datadir='${datarootdir}'
datarootdir='${prefix}/share'
docdir='${datarootdir}/doc/${PACKAGE_TARNAME}'
dvidir='${docdir}'
exec_prefix='NONE'
ft_devel=''
gphoto2_devel=''
gphoto2port_devel=''
host='x86_64-unknown-linux-gnu'
host_alias=''
host_cpu='x86_64'
host_os='linux-gnu'
host_vendor='unknown'
htmldir='${docdir}'
includedir='${prefix}/include'
infodir='${datarootdir}/info'
libdir='${exec_prefix}/lib'
libexecdir='${exec_prefix}/libexec'
localedir='${datarootdir}/locale'
localstatedir='${prefix}/var'
mandir='${datarootdir}/man'
oldincludedir='/usr/include'
pdfdir='${docdir}'
prefix='NONE'
program_transform_name='s,x,x,'
psdir='${docdir}'
sane_devel=''
sbindir='${exec_prefix}/sbin'
sharedstatedir='${prefix}/com'
sysconfdir='${prefix}/etc'
target_alias=''

## ------------------- ##
## File substitutions. ##
## ------------------- ##

MAKE_DLL_RULES=''
MAKE_IMPLIB_RULES=''
MAKE_PROG_RULES=''
MAKE_RULES=''
MAKE_TEST_RULES=''

## ----------- ##
## confdefs.h. ##
## ----------- ##

#define PACKAGE_NAME "Wine"
#define PACKAGE_TARNAME "wine"
#define PACKAGE_VERSION "1.1.24"
#define PACKAGE_STRING "Wine 1.1.24"
#define PACKAGE_BUGREPORT "wine-devel@winehq.org"

configure: exit 77


Now what do I need to do?

Again, Thanks in advance!
To protect their little egos, they put burritos in their Speedos!

Bakshara the Linux Noob!

#22 hybrid

hybrid

    Linux-Noob Frequent Member

  • Admin
  • PipPipPipPipPipPipPipPip
  • 1,005 posts

Posted 28 February 2010 - 11:17 AM

I have done some research and I came across the same error from someone doing roughly the same thing on Ubuntu (this post from the Ubuntu forums).

Unfortunately, I don't think you can actually compile wine from source, for a number of reasons (some of which are wine's fault, others are Ubuntu's):

1. WINE must be compiled to a 32bit executable. This is no-one's fault - all of the windows programs you want to run will be 32bit, so must WINE.
2. The WINE source-code does not compile under gcc-4. It just errors out. It does compile under gcc-3.4, but...
3. I can't get gcc-3.4 to produce 32bit binaries under Ubuntu!


From the information you posted, you are using an x86-64 distribution of Fedora and it looks like you will also run into this problem that you (for some reason as explained in the quote) can't compile Wine as 32-bit on a 64-bit host.

If you can install from a pre-built RPM package of the version of wine you would like, this should work. Alternatively, if you are determined to compile from source, you may need to reinstall Fedora x86 so that your whole system is 32-bit and you sidestep this issue.

I don't think you have told us which version of Fedora you are now using, but I did find this RPM of the Wine version you were after for Fedora 10 -- http://www.rpmfind.n....fc10.i386.html. You may want to search online yourself for wine-1.1.25-1 fedora version rpm.

If at all possible, though, you should use the wine version you get from 'yum install wine'. This will be much easier to maintain when updates are issued and using yum you will always know it comes from a reliable, trusted source.
My website | Portfolio

FOSSwire -- all about free and open source software, featuring tips, tricks, tutorials, reviews, articles and all the latest news from the free software universe.

#23 Bakshara

Bakshara

    Linux-Noob Member

  • Members
  • PipPip
  • 91 posts

Posted 03 March 2010 - 04:44 AM

...
I don't think you have told us which version of Fedora you are now using, but I did find this RPM of the Wine version you were after for Fedora 10 -- http://www.rpmfind.n....fc10.i386.html. You may want to search online yourself for wine-1.1.25-1 fedora version rpm.
...

I have an AMD 64 AM2 that handles both 32 bit & 64 bit. I am Running Dual boot windoze HexP64 and Linux Fedora 11.
I was running wine-1.1.24 just fine until I upgraded it to wine-1.1.30. That is when all my problems began. I completely removed wine-1.1.30. Hope that helps.

Thanks,

Bakshara
To protect their little egos, they put burritos in their Speedos!

Bakshara the Linux Noob!

#24 hybrid

hybrid

    Linux-Noob Frequent Member

  • Admin
  • PipPipPipPipPipPipPipPip
  • 1,005 posts

Posted 03 March 2010 - 05:19 PM

So, what is it that you want to do now with Wine? Roll back to 1.1.24?
My website | Portfolio

FOSSwire -- all about free and open source software, featuring tips, tricks, tutorials, reviews, articles and all the latest news from the free software universe.

#25 Dungeon-Dave

Dungeon-Dave

    Linux-Noob Frequent Member

  • Moderator
  • PipPipPipPipPipPipPip
  • 972 posts

Posted 03 March 2010 - 09:10 PM

I don't think you have told us which version of Fedora you are now using

It was displayed in the log higher up:

hostname = Bakshara
uname -m = x86_64
uname -r = 2.6.30.10-105.2.23.fc11.x86_64

FC11, on 64-bit Intel architecture.

I was running wine-1.1.24 just fine until I upgraded it to wine-1.1.30. That is when all my problems began. I completely removed wine-1.1.30. Hope that helps.

Not according to your posts higher up.

From those, I read that you downloaded source code for 1.1.30 but haven't managed to successfully compile it. You *have*, however, managed to install Wine 1.1.29 from YUM repos several times. Did that version work at all?

#26 Bakshara

Bakshara

    Linux-Noob Member

  • Members
  • PipPip
  • 91 posts

Posted 09 March 2010 - 02:49 AM


I don't think you have told us which version of Fedora you are now using

It was displayed in the log higher up:

hostname = Bakshara
uname -m = x86_64
uname -r = 2.6.30.10-105.2.23.fc11.x86_64

FC11, on 64-bit Intel architecture.

Linux Fedora 11 on an AMD 64.


I was running wine-1.1.24 just fine until I upgraded it to wine-1.1.30. That is when all my problems began. I completely removed wine-1.1.30. Hope that helps.

Not according to your posts higher up.

(see http://www.linux-noo...dpost__p__13787)
In the "03 November 2009 - 09:33 PM" post I said, "The latest news. I have successfully removed Wine completely.
I tried to install wine-1.1.24, but it installed wine-1.1.23 instead. I was fine with that. What I really wanted was to document the entire install."

From those, I read that you downloaded source code for 1.1.30 but haven't managed to successfully compile it. You *have*, however, managed to install Wine 1.1.29 from YUM repos several times. Did that version work at all?

(see http://www.linux-noo...dpost__p__13710)
No. In the very first post I said, "I updated to Wine 1.1.30 from 1.1.24. Then when I tried to run files I had ran previously, like APPLEWIN.EXE, I got a tiny dialogue that said, "Wine File" "Error" and an "OK" button. So I uninstalled Wine 1.1.30 and installed Wine 1.1.29. Same error..."

Please help,

Bakshara
To protect their little egos, they put burritos in their Speedos!

Bakshara the Linux Noob!

#27 hybrid

hybrid

    Linux-Noob Frequent Member

  • Admin
  • PipPipPipPipPipPipPipPip
  • 1,005 posts

Posted 09 March 2010 - 03:15 PM

I'm sorry, I still don't understand what it is you want to now do. What is the desired outcome of this? What do you want to do with Wine?
My website | Portfolio

FOSSwire -- all about free and open source software, featuring tips, tricks, tutorials, reviews, articles and all the latest news from the free software universe.

#28 Dungeon-Dave

Dungeon-Dave

    Linux-Noob Frequent Member

  • Moderator
  • PipPipPipPipPipPipPip
  • 972 posts

Posted 13 March 2010 - 10:38 AM

Linux Fedora 11 on an AMD 64.

Aha, didn't realise it was AMD, sorry.

No. In the very first post I said, "I updated to Wine 1.1.30 from 1.1.24.

I know that's what you SAID, and you probably believed that you were upgrading 1.1.24->30... but for the rest of this thread I (and Pete) have been trying to clear up your confusion over installation methods: you never actually upgraded, which accounts for part of your confusion.

If you re-read from the post you linked - in which you describe your actions - which can be summarised thus:
- you were downoading source code in .bz2 archives
- you then used YUM to install from RPM files held on online repos (which ignored the archives)
- you were confused as to why the version you had installed (RPMs) differed to the ones you downloaded (bz2s)

The clue should have been in your statement:
"about half way through it asks,
Total download size: 29 M"

- why is YUM downloading 29M when you have already downloaded the .bz2 files? Because yum is ignoring those archives and downloading PRM files into /var/yum/cache.

If you *had* successfully installed 1.1.30 from the .bz archives, then you would have extracted and compiled manually, which you didn't know how to do (your later post asked for instructions on how to do this). All of your posts suggest to me that you have never actually installed from your downloaded archives but used YUM all this time, which has continuously installed 1.1.29. You even asked later on in the thread why that same version keeps cropping up - and even after that evidence you still believe you installed 1.1.30.

I honestly think a lot of your confusion is down to you convincing yourself of incorrect facts, which means any view of reality after that will be skewed. We're willing (and trying) to help you here, Bakshara - but only if you listen and understand what had been written beforehand.

Asking where that ship has disappeared from the horizon - after telling everyone the world is flat - will never get you the right answer.

How about we draw a line under that with a simple question of: "what IS it you want to do with wine?"

#29 Bakshara

Bakshara

    Linux-Noob Member

  • Members
  • PipPip
  • 91 posts

Posted 06 June 2010 - 10:39 PM

I know it has been a while, but this is now more of "How to manually install Wine" than "How do I completely remove Wine."

I did a whole lot research on-line. The following is what I did, the results I got. Then I would like to know what I am missing and what I need to do next.

Gratefully,

Bakshara

[Bakshara@Bakshara ~]$ cd /media/LinuxSwitch/Misc/Download/Need2Scan/Linux/wine-1.1.24
[Bakshara@Bakshara wine-1.1.24]$ ./tools/wineinstall
Wine Installer v1.0

Running configure...

checking build system type... x86_64-unknown-linux-gnu
checking host system type... x86_64-unknown-linux-gnu
checking whether make sets $(MAKE)... yes
checking for gcc... gcc
checking for C compiler default output file name...
configure: error: in `/media/LinuxSwitch/Misc/Download/Need2Scan/Linux/wine-1.1.24':
configure: error: C compiler cannot create executables
See `config.log' for more details.

Configure failed, aborting install.
[Bakshara@Bakshara wine-1.1.24]$


This file contains any messages produced by compilers while
running configure, to aid debugging if configure makes a mistake.

It was created by Wine configure 1.1.24, which was
generated by GNU Autoconf 2.63. Invocation command line was

$ ./configure

## --------- ##
## Platform. ##
## --------- ##

hostname = Bakshara
uname -m = x86_64
uname -r = 2.6.30.10-105.2.23.fc11.x86_64
uname -s = Linux
uname -v = #1 SMP Thu Feb 11 07:06:34 UTC 2010

/usr/bin/uname -p = unknown
/bin/uname -X = unknown

/bin/arch = x86_64
/usr/bin/arch -k = unknown
/usr/convex/getsysinfo = unknown
/usr/bin/hostinfo = unknown
/bin/machine = unknown
/usr/bin/oslevel = unknown
/bin/universe = unknown

PATH: /usr/lib64/qt-3.3/bin
PATH: /usr/kerberos/sbin
PATH: /usr/kerberos/bin
PATH: /usr/lib64/ccache
PATH: /usr/local/bin
PATH: /usr/bin
PATH: /bin
PATH: /usr/local/sbin
PATH: /usr/sbin
PATH: /sbin
PATH: /home/Bakshara/bin


## ----------- ##
## Core tests. ##
## ----------- ##

configure:2289: checking build system type
configure:2307: result: x86_64-unknown-linux-gnu
configure:2329: checking host system type
configure:2344: result: x86_64-unknown-linux-gnu
configure:2379: checking whether make sets $(MAKE)
configure:2401: result: yes
configure:2458: checking for gcc
configure:2474: found /usr/lib64/ccache/gcc
configure:2485: result: gcc
configure:2717: checking for C compiler version
configure:2725: gcc --version >&5
gcc (GCC) 4.4.1 20090725 (Red Hat 4.4.1-2)
Copyright © 2009 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

configure:2729: $? = 0
configure:2736: gcc -v >&5
Using built-in specs.
Target: x86_64-redhat-linux
Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --with-bugurl=http://bugzilla.redhat.com/bugzilla --enable-bootstrap --enable-shared --enable-threads=posix --enable-checking=release --with-system-zlib --enable-__cxa_atexit --disable-libunwind-exceptions --enable-languages=c,c++,objc,obj-c++,java,fortran,ada --enable-java-awt=gtk --disable-dssi --enable-plugin --with-java-home=/usr/lib/jvm/java-1.5.0-gcj-1.5.0.0/jre --enable-libgcj-multifile --enable-java-maintainer-mode --with-ecj-jar=/usr/share/java/eclipse-ecj.jar --disable-libjava-multilib --with-ppl --with-cloog --with-tune=generic --with-arch_32=i586 --build=x86_64-redhat-linux
Thread model: posix
gcc version 4.4.1 20090725 (Red Hat 4.4.1-2) (GCC)
configure:2740: $? = 0
configure:2747: gcc -V >&5
gcc: '-V' option must have argument
configure:2751: $? = 1
configure:2774: checking for C compiler default output file name
configure:2796: gcc conftest.c >&5
/usr/bin/ld: skipping incompatible /usr/lib/gcc/x86_64-redhat-linux/4.4.1/../../../libc.so when searching for -lc
/usr/bin/ld: skipping incompatible /usr/lib/libc.so when searching for -lc
/usr/bin/ld: cannot find -lc
collect2: ld returned 1 exit status
configure:2800: $? = 1
configure:2838: result:
configure: failed program was:
| /* confdefs.h. */
| #define PACKAGE_NAME "Wine"
| #define PACKAGE_TARNAME "wine"
| #define PACKAGE_VERSION "1.1.24"
| #define PACKAGE_STRING "Wine 1.1.24"
| #define PACKAGE_BUGREPORT "wine-devel@winehq.org"
| /* end confdefs.h. */
|
| int
| main ()
| {
|
| ;
| return 0;
| }
configure:2844: error: in `/media/LinuxSwitch/Misc/Download/Need2Scan/Linux/wine-1.1.24':
configure:2847: error: C compiler cannot create executables
See `config.log' for more details.

## ---------------- ##
## Cache variables. ##
## ---------------- ##

ac_cv_build=x86_64-unknown-linux-gnu
ac_cv_env_CCC_set=
ac_cv_env_CCC_value=
ac_cv_env_CC_set=
ac_cv_env_CC_value=
ac_cv_env_CFLAGS_set=
ac_cv_env_CFLAGS_value=
ac_cv_env_CPPFLAGS_set=
ac_cv_env_CPPFLAGS_value=
ac_cv_env_CPP_set=
ac_cv_env_CPP_value=
ac_cv_env_CXXFLAGS_set=
ac_cv_env_CXXFLAGS_value=
ac_cv_env_CXX_set=
ac_cv_env_CXX_value=
ac_cv_env_LDFLAGS_set=
ac_cv_env_LDFLAGS_value=
ac_cv_env_LIBS_set=
ac_cv_env_LIBS_value=
ac_cv_env_XMKMF_set=
ac_cv_env_XMKMF_value=
ac_cv_env_build_alias_set=
ac_cv_env_build_alias_value=
ac_cv_env_host_alias_set=
ac_cv_env_host_alias_value=
ac_cv_env_target_alias_set=
ac_cv_env_target_alias_value=
ac_cv_host=x86_64-unknown-linux-gnu
ac_cv_prog_ac_ct_CC=gcc
ac_cv_prog_make_make_set=yes

## ----------------- ##
## Output variables. ##
## ----------------- ##

ALL_DLL_DIRS=''
ALL_IMPLIB_DIRS=''
ALL_MAKEFILES=''
ALL_MAKEFILE_DEPENDS=''
ALL_MAKERULES=''
ALL_PROGRAM_BIN_INSTALL_DIRS=''
ALL_PROGRAM_DIRS=''
ALL_PROGRAM_INSTALL_DIRS=''
ALL_TEST_DIRS=''
ALL_TOP_DIRS=''
ALL_WINETEST_DEPENDS=''
ALSALIBS=''
AR=''
ARFLAGS=''
AUDIOIOLIBS=''
BISON=''
BUILTINFLAG=''
CARBONLIB=''
CC='gcc'
CFLAGS=''
COREAUDIO=''
COREFOUNDATIONLIB=''
CPP=''
CPPBIN=''
CPPFLAGS=''
CROSSCC=''
CROSSTARGETFLAGS=''
CROSSTEST=''
CRTLIBS=''
CUPSINCL=''
CXX=''
CXXFLAGS=''
DEFS=''
DEPENDENCIES=''
DISKARBITRATIONLIB=''
DLLEXT=''
DLLFLAGS=''
DLLTOOL=''
DLLWRAP=''
ECHO_C=''
ECHO_N='-n'
ECHO_T=''
EGREP=''
ESDCONFIG=''
ESDINCL=''
ESDLIBS=''
EXEEXT=''
EXTRACFLAGS=''
EXTRA_BINARIES=''
FLEX=''
FONTCONFIGINCL=''
FONTFORGE=''
FREETYPEINCL=''
FREETYPELIBS=''
GNUTLSINCL=''
GPHOTO2INCL=''
GPHOTO2LIBS=''
GREP=''
HALINCL=''
ICOTOOL=''
IMPLIBEXT=''
INSTALL_DATA=''
INSTALL_PROGRAM=''
INSTALL_SCRIPT=''
IOKITLIB=''
LCMSLIBS=''
LDAPLIBS=''
LDCONFIG=''
LDD=''
LDDLLFLAGS=''
LDEXECFLAGS=''
LDFLAGS=''
LDPATH=''
LDRPATH_INSTALL=''
LDRPATH_LOCAL=''
LDSHARED=''
LIBDL=''
LIBEXT=''
LIBKSTAT=''
LIBOBJS=''
LIBPOLL=''
LIBPTHREAD=''
LIBS=''
LINT=''
LINTFLAGS=''
LN=''
LN_S=''
LTLIBOBJS=''
MAINTAINER_MODE='#'
MINGWAR=''
NASLIBS=''
OBJEXT=''
OPENGL_LIBS=''
PACKAGE_BUGREPORT='wine-devel@winehq.org'
PACKAGE_NAME='Wine'
PACKAGE_STRING='Wine 1.1.24'
PACKAGE_TARNAME='wine'
PACKAGE_VERSION='1.1.24'
PATH_SEPARATOR=':'
PKG_CONFIG=''
PNGINCL=''
PRELINK=''
RANLIB=''
RESOLVLIBS=''
RSVG=''
SANEINCL=''
SECURITYLIB=''
SET_MAKE=''
SHELL='/bin/sh'
SOCKETLIBS=''
STRIP=''
TARGETFLAGS=''
TOOLSDIR=''
WIN16_FILES=''
WIN16_INSTALL=''
XLIB=''
XMKMF=''
XML2INCL=''
XML2LIBS=''
XSLTINCL=''
X_CFLAGS=''
X_EXTRA_LIBS=''
X_LIBS=''
X_PRE_LIBS=''
ZLIB=''
ac_ct_AR=''
ac_ct_CC='gcc'
ac_ct_CXX=''
bindir='${exec_prefix}/bin'
build='x86_64-unknown-linux-gnu'
build_alias=''
build_cpu='x86_64'
build_os='linux-gnu'
build_vendor='unknown'
datadir='${datarootdir}'
datarootdir='${prefix}/share'
docdir='${datarootdir}/doc/${PACKAGE_TARNAME}'
dvidir='${docdir}'
exec_prefix='NONE'
ft_devel=''
gphoto2_devel=''
gphoto2port_devel=''
host='x86_64-unknown-linux-gnu'
host_alias=''
host_cpu='x86_64'
host_os='linux-gnu'
host_vendor='unknown'
htmldir='${docdir}'
includedir='${prefix}/include'
infodir='${datarootdir}/info'
libdir='${exec_prefix}/lib'
libexecdir='${exec_prefix}/libexec'
localedir='${datarootdir}/locale'
localstatedir='${prefix}/var'
mandir='${datarootdir}/man'
oldincludedir='/usr/include'
pdfdir='${docdir}'
prefix='NONE'
program_transform_name='s,x,x,'
psdir='${docdir}'
sane_devel=''
sbindir='${exec_prefix}/sbin'
sharedstatedir='${prefix}/com'
sysconfdir='${prefix}/etc'
target_alias=''

## ------------------- ##
## File substitutions. ##
## ------------------- ##

MAKE_DLL_RULES=''
MAKE_IMPLIB_RULES=''
MAKE_PROG_RULES=''
MAKE_RULES=''
MAKE_TEST_RULES=''

## ----------- ##
## confdefs.h. ##
## ----------- ##

#define PACKAGE_NAME "Wine"
#define PACKAGE_TARNAME "wine"
#define PACKAGE_VERSION "1.1.24"
#define PACKAGE_STRING "Wine 1.1.24"
#define PACKAGE_BUGREPORT "wine-devel@winehq.org"

configure: exit 77


To protect their little egos, they put burritos in their Speedos!

Bakshara the Linux Noob!

#30 hybrid

hybrid

    Linux-Noob Frequent Member

  • Admin
  • PipPipPipPipPipPipPipPip
  • 1,005 posts

Posted 07 June 2010 - 09:58 AM

You still don't have all the programs you need in order to compile wine. Assuming you're still running Fedora 11, try:

su -
yum groupinstall "Development Tools" "Development Libraries"

And then retry the install.

UPDATE: if you do in fact have all of that already installed, this might be the 64-bit/32-bit issue we discussed at some point earlier in the thread. I'm not sure how you would resolve that.
My website | Portfolio

FOSSwire -- all about free and open source software, featuring tips, tricks, tutorials, reviews, articles and all the latest news from the free software universe.

#31 Dungeon-Dave

Dungeon-Dave

    Linux-Noob Frequent Member

  • Moderator
  • PipPipPipPipPipPipPip
  • 972 posts

Posted 07 June 2010 - 04:06 PM

I know it has been a while, but this is now more of "How to manually install Wine"

Then I would like to know what I am missing and what I need to do next.

So far you have been asked "So, what is it that you want to do now with Wine? Roll back to 1.1.24?" but haven't really answered - you seem to be intent with asking how to do things, rather than fully stating what your intended goal is. Not saying that this is incorrect (many people want to experiment just to gain experience) but it isn't helping you much if we don't fully understand the reasoning behind your objectives.

Alternatively, if you are determined to compile from source, you may need to reinstall Fedora x86 so that your whole system is 32-bit and you sidestep this issue.

It sounds like you cannot manually compile WINE under 64-bit.

You may use YUM to install the 64-bit version from repos, but this is not the same as manually compiling.

#32 Bakshara

Bakshara

    Linux-Noob Member

  • Members
  • PipPip
  • 91 posts

Posted 14 June 2010 - 02:11 AM

So far you have been asked "So, what is it that you want to do now with Wine? Roll back to 1.1.24?" but haven't really answered - you seem to be intent with asking how to do things, rather than fully stating what your intended goal is. Not saying that this is incorrect (many people want to experiment just to gain experience) but it isn't helping you much if we don't fully understand the reasoning behind your objectives.


I want to manually compile Wine 1.1.24. That is what I had before. That is what worked.

Alternatively, if you are determined to compile from source, you may need to reinstall Fedora x86 so that your whole system is 32-bit and you sidestep this issue.
It sounds like you cannot manually compile WINE under 64-bit.

You may use YUM to install the 64-bit version from repos, but this is not the same as manually compiling.


I do want to compile from source. There should be no problem for two reasons:
1) As I just mentioned I had Wine 1.1.24 before and it worked.
2) I have an AMD 64 CPU that handles both 32bit and 64bit.

Part of the research was under http://www.murga-lin...pic.php?t=44007 but, I was not sure that would work with Fedora.

I hope this clears up your questions. Please let me know exactly what you need to know so I can do this.

Thanks in advance,

Bakshara
To protect their little egos, they put burritos in their Speedos!

Bakshara the Linux Noob!

#33 Dungeon-Dave

Dungeon-Dave

    Linux-Noob Frequent Member

  • Moderator
  • PipPipPipPipPipPipPip
  • 972 posts

Posted 14 June 2010 - 01:14 PM

I want to manually compile Wine 1.1.24. That is what I had before. That is what worked.

I do want to compile from source. There should be no problem for two reasons:
1) As I just mentioned I had Wine 1.1.24 before and it worked.
2) I have an AMD 64 CPU that handles both 32bit and 64bit.

Please let me know exactly what you need to know so I can do this.


Alternatively, if you are determined to compile from source, you may need to reinstall Fedora x86 so that your whole system is 32-bit and you sidestep this issue.

Remember that your AMD64 CPU handles both 32-bit and 64-bit OPERATING SYSTEMS. It seems like you will need to compile Wine on a 32-bit OS (it won't compile on 64-bit) - but I'm not certain if the 32-bit binary will work seamlessly on 64-bit platforms.

Do you definitely know if the yum-installed version (1.1.29) wasn't any good? Or are you going for the manual compile as a challenge?

#34 Bakshara

Bakshara

    Linux-Noob Member

  • Members
  • PipPip
  • 91 posts

Posted 17 June 2010 - 02:59 AM

Remember that your AMD64 CPU handles both 32-bit and 64-bit OPERATING SYSTEMS. It seems like you will need to compile Wine on a 32-bit OS (it won't compile on 64-bit) - but I'm not certain if the 32-bit binary will work seamlessly on 64-bit platforms.

Do you definitely know if the yum-installed version (1.1.29) wasn't any good? Or are you going for the manual compile as a challenge?


I started with Linux Fedora 9 and Wine 1.1.24. I upgraded Linux directly to Fedora 11. I left Wine at version 1.1.24. At some point I thought it would be a good idea to upgrade wine. Then the latest version was 1.1.30. It just had all kinds of problems. That is when I did all I could to completely remove it. See complete details

Now I want to go back to 1.1.24. Then I can have the fun I was having before. As for the, "compile as a challenge," if it works it's worth it.

Please let me know what else you need to know so I can get this done.

Thanks,

Bakshara
To protect their little egos, they put burritos in their Speedos!

Bakshara the Linux Noob!

#35 Dungeon-Dave

Dungeon-Dave

    Linux-Noob Frequent Member

  • Moderator
  • PipPipPipPipPipPipPip
  • 972 posts

Posted 17 June 2010 - 06:24 PM

If you want to install from an RPM, you'll need to search for the right package: wine-1.1.24.x86_64.fc11.rpm or so.

If you download that package, use "yum localinstall wine-1.1.24.x86_64.fc11.rpm" then it'll resolve dependencies for you.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users