I don't have it in my version of Pharo. I don't know if I can update it without going through a full pharo image which I don't want to do now.
Ok. Doesn't matter. Your current problem is not about FFI but you will have that problem then (when you get squeakDBX working). You only need to get the latests FFI version from MC to work in pharo with closure VM.
I am pretty sure the VM I used is not with the fixed closure. I am note sure about the image, I can tell you tomorrow the version number of the image when at the office.
Is the fixed closure mandatory to get SqueakDBX working?
Which Pharo # image and VM should be used?
SqueakDBX works with both. If you use a closure image you must use a VM with closure an latest FFI (from MC). But, you can also use Squeak in older version (non closure) with FFI from Universes. So, no problem for you.
�
I haven't my linux machine here, I will look tonight in my home, but:
> 1) what do you have /usr/lib in PATH ?
No it points only to binary as it should.
Does FFI looks at PATH for the libraries? If so it is a buggy behavior.
I am really currious to know how FFI find the libraries...
I am not sure about this. Perhaps someone (Andreas) can help us.
�
2) Just for testing, can you put the openDBX libraries in the same directory where the pharo
image is.
3) The same as 2) but where the VM is.
I will try tomorrow morning.
Which Linux are you using?� Perhaps there is a problem trying to resolve the library. The last test you can do (just to see if it works) is this:
Go t class OpenDBXUnix and change the methods
apiBind: handle database: databaseName name: userName password: password method: method
and
apiInitialize: handle backend: backend host: host port: port
In both, put module: 'libopendbx.so.1' or module: 'libopendbx.so' instead of module: 'opendbx'
I hope you get it working. Ask all what you want.
Greetings,
Mariano
�