[Vm-dev] RE: Linux vm default plugins directory

Schwab,Wilhelm K bschwab at anest.ufl.edu
Wed Sep 1 19:49:22 UTC 2010

Bert, Eliot,

FWIW, I have had terrible results with LD_LIBRARY_PATH on Ubuntu - maybe I'm just missing something.  I probably should let the squeak script handle it, but it seems silly to use a script to call a script, so I've typically gone straight to the vm; that appears to be getting harder to do with time.

About plugins not loading, my big point is that we should not have to guess about what is or is not happening.  The vm does not provide enough information to reliably fix problems.


On 01.09.2010, at 21:12, Eliot Miranda wrote:

> Hi Wilhelm,
> On Wed, Sep 1, 2010 at 12:01 PM, Schwab,Wilhelm K <bschwab at anest.ufl.edu> wrote:
>> 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.
> Set LD_LIBRARY_PATH to include the relevant directory.  Here's the script I use at Teleplace

The current "squeak" script fills in the plugins path, so there is no need to fiddle with LD_LIBRARY_PATH.

However, I occasionally too see a plugin that inexplicably does not want to load.

- Bert -

More information about the Vm-dev mailing list