Thanks for the info.
If you think that the module is not being built at all, take a look at the config.h file in your build directory. That is the output of the cmake configure process, and if there is some issue related to locating the build libraries, you will probably see evidence of it in config.h. Look for definitions that are commented out, but maybe should not be.
Note, the "so.xxxx" naming convention is part of the installation process, so don't worry about that. If you can build the VM and install it, the naming will take care of itself.
I'm not sure which source package you are starting with, but here is a simple recipe for building the latest from Subversion.
I was using the compressed file on:
http://squeakvm.org/unix/index.html
- Start with an empty directory, then get the latest versions of all the
platforms sources and the VMMaker generated sources:
$ svn co http://squeakvm.org/svn/squeak/trunk/platforms $ svn co http://squeakvm.org/svn/squeak/trunk/src
- In that same directory, make a subdirectory in which to build the VM:
$ mkdir build $ cd build
Copy the attached Makefile into your build directory.
build the VM, and install it if you get plausible results.
$ make $ sudo make install
This makefile is what I use on Linux, so you may need to fiddle around with the CFLAGS, or add additional "--without xxxx" options to exclude modules that give you problems, but otherwise I think it should work.
I think this might help. I'll see what happens with this.
<snip>