I typically build all plugins internal, so there's no *.so file to check.
Further, I looked in the directory containing my running instance of
squeak (also as a vm), in /usr/local/lib/squeak/3.2-6, and my build
directory and could no such *.so.

Oddly, I also noticed that although my build directory does have an
UnixProcessPlugin.c, it does not have the usual subdirectory just for this
plugin.  Is that correct?  Further, when I check the VMMaker configuration
I've used to build this VM, I notice that the plugin that appears is
UnixProcessPluginNoInThisSession--what's that?

I don't think things are entirely broken, as I am able to safely clone my
running squeak instance, as well as fork headless images.  Further, on a
prior build of this VM I know I have (de)capitated images without issue.

Hope the info helps! :)


On Sat, 21 Dec 2002, David T. Lewis wrote:

>
> Hmm, this sounds totally broken. My guess is that you are accidentally
> running a different OSPP than the one you actually compiled, possibly because
> of some search path problem. For example, your VM might be finding a copy of
> UnixOSProcessPlugin.so in the /usr/local/lib/squeak/3.2-6/ directory when you
> intended to use the one you built in your ./build//UnixOSProcessPlugin/.libs/
> directory. If that's what's happening, just copy the UnixOSProcessPlugin.so
> file which you built into your squeak working directory, and you should be
> fine again.
>
> Dave
>
>
>