para_core_load gone for good

[Justin F. <vh...@us...>]

It looks like the library have been loaded twice by the console stub. 
The library was already loaded during the process start-up, because 
functions like para_mod_load() were used in a regular manner, without 
looking them up using dlsym().

For some reason under Darwin this resulted in loading the same library 
twice, even though there was only one copy of it installed and the path 
was obviously the same.

This resulted in a "fresh" copy of all static variables, effectively 
deinitializing the library.  I don't think that the ability to load the 
core dynamically worths everything that has to be done to get past this 
problem.  Link using -lparabellym.  Normally you don't notice the 
difference.

There also was a deadlock when a message was sent to a module that is 
actively waiting for it.  Introduced seml::waitex() with a parameter not 
to lock the mutex (this actually goes to libfaeutil).