Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!sdd.hp.com!think.com!ames!xn.ll.mit.edu!xn!olson From: olson@juliet.ll.mit.edu ( Steve Olson) Newsgroups: comp.windows.x Subject: Re: Sun shared libs - openwin vs MIT R4 Message-ID: Date: 9 May 91 18:50:27 GMT References: <9105090143.AA02124@lightning.McRCIM.McGill.EDU> Sender: usenet@xn.ll.mit.edu Organization: M.I.T. Lincoln Lab - Group 43 Lines: 46 In-Reply-To: mouse@lightning.mcrcim.mcgill.EDU's message of 9 May 91 01:43:17 GMT In article <9105090143.AA02124@lightning.McRCIM.McGill.EDU> mouse@lightning.mcrcim.mcgill.EDU (der Mouse) writes: A couple of suggestions: 1) Replace all the OW programs with shell script wrappers that bash $LD_LIBRARY_PATH and then exec the real binary. This is a good solution if there are a few slected OW binaries that one is interested in. Example: %more ~/bin/OWperf #! /bin/csh setenv LD_LIBRARY_PATH $OPENWINHOME/lib exec $OPENWINHOME/bin/xview/perfmeter exit 2) Use your favorite binary editor to bash the LD_LIBRARY_PATH string in the OW binaries to OW_LIBRARY_PATH or some such. (Could be automated easily; I can toss together a program to do it if you want.) First reaction: "neat idea!". Second reaction: "Er, I can't find it". I suppose that one could 1) trick up ld.so in the manner suggested and 2) edit the OW binaries to use the new ld.so. Somehow it dosen't seem worth it. der Mouse old: mcgill-vision!mouse new: mouse@larry.mcrcim.mcgill.edu The "obvious" solution, which I forgot to mention in my first post (somebody reminded me via private Email) because I don't like it too much and don't use it myself is .. setenv LD_LIBRARY_PATH : I think this helps the specific problem of the orginal poster, but I don't like it that much because it dosen't generalize too well. Perhaps for some executable you want the OW libs to have priority - you'll be forever juggling that stupid enviroment variable. -- -- Steve Olson -- MIT Lincoln Laboratory -- olson@juliet.ll.mit.edu --