From: Patrick Bennett Date: 2004-10-08T23:44:55+09:00 Subject: Re: compiling/installing ruby in a nonstandard directory Mark, do a search for the thread 'can $LOAD_PATH be relative'. I believe I posted a patch I made to Ruby that enables it to be run from any path and treat its lib directories as paths relative to where it was launched (just like it works in Windows). It was a really easy patch (as I too despise the 'fixed' path). Mark Hubbart wrote: >On Fri, 8 Oct 2004 03:04:45 +0900, ara.t.howard@noaa.gov > wrote: > > >>On Fri, 8 Oct 2004, Mark Hubbart wrote: >> >> >> >>>However, my main problem is that I want to be able to compile up some >>>packages without fubaring my system. I guess I'll have to figure out >>>some better way of setting this up; since It appears that there is no >>>way to do this while avoiding installing the binaries in their end >>>location. :/ >>> >>> >>perhaps >> >> configure --prefix=/somewhere >> make >> make prefix=/somewhere/else/ install >> >> > >Well, I didn't know I could do that... I'm guessing that will make the >binaries relocatable? I want to end up installing them in /usr/local, >but I want 'make install' to put them in ~/tmp/install. > > > >>or are you talking ruby extentions? if so something similar should work >> >> > >Yes. I need to be able to link the ruby readline extension against the >readline library, which I would like to make/install in the same >manner. In fact, thar's the main problem I'm having. If it wasn't for >the linking difficulties, I'd have just skipped the install step and >pulled the binaries/libs out of the source dir once they were >compiled. > >Thanks, >Mark > > > >>-a >>-- >>=============================================================================== >>| EMAIL :: Ara [dot] T [dot] Howard [at] noaa [dot] gov >>| PHONE :: 303.497.6469 >>| A flower falls, even though we love it; >>| and a weed grows, even though we do not love it. >>| --Dogen >>=============================================================================== >> >> >> >> > > > >