|
View:
New views
11 Messages
—
Rating Filter:
Alert me
|
|
|
upgrade wineHi
yesterday I compiled 1.1.32 on openSuse. How could I now upgrade to 1.1.33? Thanks Michael |
|
|
Re: upgrade wineTry this
Code: cd /path/to/your/wine/source git pull and then compile again Code: ./configure <with_Options_If_You_Need> && make depends && make |
|
|
Re: upgrade wineAre u trying to fool with me? :D
Anyway I'll remove all and install 1.33 michael@53-194-pool:/usr/local/lib/wine> whereis wine wine: /usr/local/bin/wine /usr/local/lib/wine |
|
|
Re: upgrade wineI didn't understand you wanted to do a system wide installation.
In my case, I compiled 1.1.32 from source and yesterday (some hours ago in fact), I wanted to try the latest release. "git pull" made my local source up to date and I compiled it but I didn't install (because I didn't want to conflict with my .deb package) So now, I'm waiting for the 1.1.33 .deb package which will properly install the latest wine. Opening the Makefile gives me: Code: # This Makefile understands the following targets: # # all (default): build wine # clean: remove all intermediate files # distclean: also remove all files created by configure # test: run tests # testclean: clean test results to force running all tests again # crosstest: build tests as native windows applications (requires MinGW) # install-lib: install libraries needed to run applications # install-dev: install development environment # install: install everything # uninstall: uninstall everything # depend: create the dependencies # ctags: create a tags file for vim and others. # etags: create a TAGS file for Emacs. # manpages: compile manpages for Wine API # htmlpages: compile html pages for Wine API # sgmlpages: compile sgml source for the Wine API Guide # xmlpages: compile xml source for the Wine API Guide so if you need to widely install wine, you should do "make uninstall" before. |
|
|
Re: upgrade winemickthebike wrote: > Are u trying to fool with me? :D > Anyway I'll remove all and install 1.33 > > michael@53-194-pool:/usr/local/lib/wine> whereis wine > wine: /usr/local/bin/wine /usr/local/lib/wine Um... su -c "make uninstall" before all steps given and su -c "make install" after all steps given by Alex? Seriously, this is basic compiling stuff, you asked how to update, the answer is recompile, and he gave instructions on how to do so even though you probably already know the instructions because you compiled before. :? |
|
|
Re: upgrade wineit still looks strange to me...make uninstall from /home/michael/downloads/wine/? I simply removed all...worked.
|
|
|
Re: upgrade wineSorry but you're wrong.
When you do "make", binaries, man pages, libraries ... are built and stay in the source directory (probably /home/michael/dowloads/wine/). When you do "make install", those files are copied in several specific (system wide) directories. So removing /home/michael/downloads/wine didn't uninstall wine. In fact, wine is still in /usr/local/bin, libraries in /usr/local/lib/wine ... As many linux users, you're coming from MS Windows. Did you used to remove a program by deleting its directory in "Program Files" ? Let me search some doc about make... |
|
|
Re: upgrade wineI found this (http://www.control-escape.com/linux/lx-swinstall-tar.html) to help you understanding compilation on linux.
You may read the last paragraph and go to Where did the files go ? (http://www.control-escape.com/linux/lx-swinstall-where.html) for more details. Hope it can help you |
|
|
Re: upgrade wineI get the feeling you didn't actually compile 1.1.32, but just retreived the already compiled version from your distro's package repository... I'm guessing "removed all" in this case removing that package.
If you really compiled before, "make uninstall" is a special command for Wine's make file that removes everything of a globally installed ("make install") Wine (except for maybe ~/.wine since that's user configuration). Removing files by hand is a LOT less convenient than doing a make uninstall. |
|
|
Re: upgrade wineThanks. Yes I simply did:
whereis wine and removed the files in bin and usr. So I should have been right. Anyway make uninstall...oh if that's wine specific that's why it looked weird to me. But i must admit i didn't really uninstall many compilations so far on Linux :P |
|
|
Re: upgrade wine> and removed the files in bin and usr. Wine installs many more files than just those in several locations, so if you actually compiled Wine from source you'll have to use make uninstall to get rid of them (and "remove package" from the package manager if it was an RPM or something like that). |
| Free embeddable forum powered by Nabble | Forum Help |