On Fri, 15 Feb 2002, Sylvain Petreolle wrote:
ldconfig -v produces :
/usr/local/lib: libopengl32.so -> libopengl32.so libglu32.so -> libglu32.so libmsvcrt20.so -> libmsvcrt20.so libsane.so.1 -> libsane.so.1.0.7 ldconfig: /usr/local/lib/libwine_unicode.so is not a symbolic link
libwine_unicode.so -> libwine_unicode.so.1.0 ldconfig: /usr/local/lib/libwine_tsx11.so is not a symbolic link
libwine_tsx11.so -> libwine_tsx11.so.1.0 ....
Not only that, but
make uninstall make install
is broken. I thought that would fix it, but I had to install the wine binary by hand, and the result is exactly the same. Where there were symbolic links before are now copies. Besides wasting file space, though, I don't see it does any harm. You get this mail by the latest Wine, ldconfig warnings and all.
Lawson
First shoot the arrow. Then draw the bulls-eye. - J. A. Soucy
On 2002.02.15 11:48 lawson_whitney@juno.com wrote: [SNIP]
Not only that, but
make uninstall make install
is broken. I thought that would fix it, but I had to install the wine binary by hand, and the result is exactly the same. Where there were symbolic links before are now copies. Besides wasting file space, though, I don't see it does any harm. You get this mail by the latest Wine, ldconfig warnings and all.
Hmm...
To make uninstall: rm -rf /opt/wine-cvs
To build and install: ./cofigure --prefix=/opt/wine-cvs make depend make make install
To run: Be sure /opt/wine-cvs/bin is on your PATH and that /opt/wine-cvs/lib is in your /etc/ld.so.conf.. that's IT.. why WOULDN'T you put Wine in it's own prefix under /opt or /usr or wherver you please.
Solves all of these problems.
Besides.. make uninstall is a broken concept anyway.. Who the hell would want to keep the sourcetree of a program around just so they could uninstall it properly? Not I.
-Dave
At the moment make install/uninstall is working as before. rm and others are not necessary... And the problem was only in /usr/local/lib... ...fixed now.
Hmm...
To make uninstall: rm -rf /opt/wine-cvs
To build and install: ./cofigure --prefix=/opt/wine-cvs make depend make make install
To run: Be sure /opt/wine-cvs/bin is on your PATH and that /opt/wine-cvs/lib is in your /etc/ld.so.conf.. that's IT.. why WOULDN'T you put Wine in it's own prefix under /opt or /usr or wherver you please.
Solves all of these problems.
Besides.. make uninstall is a broken concept anyway.. Who the hell would want to keep the sourcetree of a program around just so they could uninstall it properly? Not I.
-Dave
wine-users mailing list wine-users@winehq.com http://www.winehq.com/mailman/listinfo/wine-users
___________________________________________________________ Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français ! Yahoo! Mail : http://fr.mail.yahoo.com
On Fri, 15 Feb 2002, David Elliott wrote:
Solves all of these problems.
No it doesn't. It was nothing to do with --prefix.
Besides.. make uninstall is a broken concept anyway.. Who the hell would want to keep the sourcetree of a program around just so they could uninstall it properly? Not I.
-Dave
I keep the source in case I want to work on it, or test somebody's patch, also I just like having source around.
This fixed it:
ChangeSet ID: 1013786006777549421414733 CVSROOT: /opt/cvs-commit Module name: wine Changes by: julliard@wine2. 02/02/15 10:13:27
Modified files: . : Makefile.in configure configure.ac
Log message: Fixed installation issues caused by new configure script.
Patch: http://cvs.winehq.com/patch.py?id=1013786006777549421414733
Revision Changes Path 1.107 +3 -1 wine/Makefile.in 1.256 +362 -364 wine/configure 1.2 +0 -3 wine/configure.ac
Lawson
Probable user head space error. - Dennis A. Moore
"David Elliott" dfe@tgwbd.org wrote in message news:20020215231337.G4335@biscuit.chronic...
On 2002.02.15 11:48 lawson_whitney@juno.com wrote: [SNIP]
Not only that, but
make uninstall make install
is broken. I thought that would fix it, but I had to install the wine binary by hand, and the result is exactly the same. Where there were symbolic links before are now copies. Besides wasting file space, though, I don't see it does any harm. You get this mail by the latest Wine, ldconfig warnings and all.
Hmm...
Don't worry; it was a very temporary problem that Alexandre fixed as soon as he was aware of it.
If you are really interested: For a very short period of time the rule to "make install" included making install in all subdirectories and then copying the wine itself into the bin. Unfortunately making install in the debugger included copying the wine in bin, except it hadn't been put there yet (so it stopped).
Congratulations to Alexandre on fixing the whole thing so promptly.
Bill
On Sat, 16 Feb 2002, Bill Medland wrote:
Don't worry; it was a very temporary problem that Alexandre fixed as soon as he was aware of it.
I know that. I already said on wine-users that it's fixed... Oh, I see. I cross-posted the make install bit back to wine-devel to make sure he _was_ aware of it, and then said no more about it on wine-devel. I wondered why this was still echoing. No, I'm not worried, and I even found and installed autoconf 2.50.
If you are really interested: For a very short period of time the rule to "make install" included making install in all subdirectories and then copying the wine itself into the bin. Unfortunately making install in the debugger included copying the wine in bin, except it hadn't been put there yet (so it stopped).
I know, that's why I said I had to hand-install wine to start it back up.
Congratulations to Alexandre on fixing the whole thing so promptly.
Bill
Yes, he is amazing, isn't he? Great sense of humor, too.
Really, I am not one who has to have the last word, so if you answer this, please don't be offended if I let it drop, as I should have done already.
Lawson ---oof---
-
Bill Medland -
David Elliott -
lawson_whitney＠juno.com -
Sylvain Petreolle