On November 11, 2003 11:39, Ivan Leo Murray-Smith wrote:
I don't know how to solve your problem, but it would be a good idea if you just installed the latest CVS version.
<whine>
I' just too inexperienced and too isolated to use CVS right now: an 800 page manual, configuring, using SSH, it threatens to take up the rest of the year just to get started, and I'm off to another mailing list when the inevitable "why doesn't it work" problems occur.
I've also discovered that with non-rpm source distributions, there is a "make install", but so far, nothing I have seen has a "make uninstall" that does anything, and that concerns me, when I see 70 MB of stuff flying off to 400 different places. (Maybe wine is not like that, but I just built the "insight" gdb, and I thought it would use my existing gdb, but it built and installed a new one, installed its own tk, (gee, what about the tk that is a part of Python) and has no way to uninstall.
I'm at a place where I'm wrestling with "how does the PATH get set", "how do you build a static library", "how do you build a shared library", "how does the loader find a shared library". Wrestling with ten thousand-line makefiles is sheer insanity from my perspective. I just hope that I can get my little program to compile and run with winelib, because if it that works, I won't have to use Windows in my day-to-day work.
</whine>
If you really want the latest RPM, you can get it here http://prdownloads.sourceforge.net/wine/wine-20031016-mdk.i586.rpm?download but the CVS would be a better solution, as the binary is stripped of all debug symbols, so it's harder to debug with a rpm version.
OK, great, that link works today, but what about the wine libraries - wine-devel? What version, which rpm is compatible? There are only Suse and Red Hat rpms on sourceforge, and likely my original problem is a version mismatch (i.e. the winebuilder tools seem to generate makefile commands that other tools (wrc) don't understand)