[Vm-dev] Linux vm default plugins directory

[Eliot Miranda]

On Wed, Sep 1, 2010 at 1:53 PM, Bert Freudenberg <bert at freudenbergs.de>wrote:

>
>
> On 01.09.2010, at 22:38, Eliot Miranda wrote:
>
>
>
> On Wed, Sep 1, 2010 at 12:22 PM, Bert Freudenberg <bert at freudenbergs.de>wrote:
>
>>
>>
>> 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.
>>
>
> If one has a plugin that depends on a secondary library then fiddling with
> LD_LIBRARY_PATH can be necessary.
>
>
> True, but that's not specific to squeak :)
>
>
>
>>
>> http://squeakvm.org/svn/squeak/trunk/platforms/unix/cmake/squeak.in
>>
>> However, I occasionally too see a plugin that inexplicably does not want
>> to load.
>>
>
> Inexplicably, or because some symbol is undefined?
>
>
> Inexplicably. I'm pretty certain that I've seen a plugin I just compiled
> fail, and when compiled again it worked.
>

Linux creeps me out like this.  Th way it does so currently is when using
gdb and one is not supposed to have to exit if one recompiles teh executable
one is debugging, except when one does because every one out of four times
it just doesn't work.  Not debugging the program one thinks one is debugging
is only slightly less well known than getting mired in a land war in Asia
and yet gdb on linux invades Afghanistan regularly...


>
> - Bert -
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.squeakfoundation.org/pipermail/vm-dev/attachments/20100901/f5b0aa61/attachment.htm