[gobolinux-users] Source repositories and other suggestions
martinobal at gmail.com
Sun Dec 3 17:30:05 UTC 2006
Well, if the information about which libraries will be actually used can be
extracted, so that you eventually get an R-R name look up in the
compatibility table, then I see no problem with that. But I'm probably
overlooking something. Isn't there any potential problems with your
proposal? Has it not ever been proposed or adopted?
Interesting idea, this per-process view of library locations. I'd say it
sounds a bit like Plan9 :D
On 12/3/06, Jonatan Liljedahl <lijon at kymatica.com> wrote:
> Martin Baldan wrote:
> > On 12/3/06, Jonatan Liljedahl <lijon at kymatica.com> wrote:
> >> Just an idea.. I'm not sure what you want, but if you want to control
> >> exactly what libraries are linked (runtime) with a program, wouldn't it
> >> be possible to have a separate set of links to libs under each program?
> >> Like /Programs/Foo/Current/Links/lib and then set LD_LIBRARY_PATH to
> >> this before running a binary?
> >> --
> > Wouldn't this affect the behavior of other programs? How does this
> > recursive dependencies? Isn't LD_LIBRARY_PATH a global variable?
> You can set it locally for each running process, like this:
> ] LD_LIBRARY_PATH=/Programs/MyApp/lib myapp
> One could make a wrapper script for this:
> LD_LIBRARY_PATH=$(which $1 | cut -d/ -f1-3)/lib $1
> If this script is saved as /bin/linkrun, then one just runs:
> ] linkrun name-of-binary
> It wouldn't affect other programs. Recursive dependencies would not be
> handled in any special way, all libraries would be searched for in the
> current LD_LIBRARY_PATH...
> /Jonatan -=( http://kymatica.com )=-
> gobolinux-users mailing list
> gobolinux-users at lists.gobolinux.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the gobolinux-users