<br><br><div class="gmail_quote">On Wed, Sep 1, 2010 at 1:53 PM, Bert Freudenberg <span dir="ltr"><<a href="mailto:bert@freudenbergs.de">bert@freudenbergs.de</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<br><div style="word-wrap:break-word"><br><div><div>On 01.09.2010, at 22:38, Eliot Miranda wrote:</div><br><blockquote type="cite"><br><br><div class="gmail_quote">On Wed, Sep 1, 2010 at 12:22 PM, Bert Freudenberg <span dir="ltr"><<a href="mailto:bert@freudenbergs.de" target="_blank">bert@freudenbergs.de</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div><br>
<br>
On 01.09.2010, at 21:12, Eliot Miranda wrote:<br>
<br>
> Hi Wilhelm,<br>
><br>
> On Wed, Sep 1, 2010 at 12:01 PM, Schwab,Wilhelm K <<a href="mailto:bschwab@anest.ufl.edu" target="_blank">bschwab@anest.ufl.edu</a>> wrote:<br>
><br>
>> A recurring theme is that I encounter a problem for which there is no explanation from the system, hack the vm sources to add some tracing, and correct the problem. As a result, I end up building the vm from source and so tend to use a shell script that runs it.<br>
>><br>
> Set LD_LIBRARY_PATH to include the relevant directory. Here's the script I use at Teleplace<br>
<br>
</div>The current "squeak" script fills in the plugins path, so there is no need to fiddle with LD_LIBRARY_PATH.<br></blockquote><div><br></div><div>If one has a plugin that depends on a secondary library then fiddling with LD_LIBRARY_PATH can be necessary.</div>
</div></blockquote><div><br></div><div>True, but that's not specific to squeak :)</div></div></div></blockquote><div><br></div><div>Right. But -plugins only solves the issue one level deep whereas fiddling with LD_LIBRARY_PATH, as horribly ugly as that is, solves it for any depth, hence in my book its the only way to go.</div>
<div><br></div><div>cheers</div><div>Eliot</div></div>