wrc doesn't seem to accept -r option,even though it is automatically generated by make file

[Gregory M. Turner]

On Tuesday 11 November 2003 01:22 pm, Parzival Herzog wrote:
> 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>

There, there, no need to <whine />, it's going to be OK!  Try following the 
instructions on this page: 

http://www.winehq.com/site/cvs

Just do what it says, step-by-step.  You don't need ssh for this, just cvs.  
That page even tells you how to keep your wine up-to-date via cvs once you 
get it.

And, wine just happens to support "make uninstall".

Sounds to me like you are letting yourself get overwhelmed by the scope of 
what you do not know.  For example, very few people here (although there are 
probably one or two) would actually know the full answer to "how does the 
loader find a shared library".  You don't need to know that for your 
experiment.  Instead, just read the "ld.so" manpage and the pages it 
references.  Think of it like your television: you don't care how the "ion 
gun" works... just how to change the channel, volume, etc.

(As for the make uninstall thing, you hit the nail on the head: where did all 
those binaries go?  Many unixy programs support a "--prefix=[path]" argument 
at the "configure" stage of the build; so all your binaries go under that 
directory; for example, to install my wine, I use --prefix=/opt/wine, which 
puts wine in /opt/wine/bin, /opt/wine/lib, etc.  But it certainly can get 
tricky keeping track of this if you are building tons of stuff from source 
and putting it all in "/usr" or "/usr/local", as is common practice. The best 
solution I know of, if you are building lots of stuff from source, is to use 
gentoo, which really does rigorously keep track of what 'make install' did.  
But I should warn you that gentoo is not always so easy to get up and running 
as other distributions.)

Good luck!  You are now in the nasty horizontal part of the learning curve for 
unix programming and wine.  It does get better, just be patient and 
persistent, and you will prevail.

-- 
gmt

"It is to be the assent and ratification of the several States,
derived from the supreme authority in each State, the authority
of the people themselves.  The act, therefore, establishing the
Constitution, will not be a NATIONAL, but a FEDERAL act." --James
Madison, Federalist No. 39