hi, this is not a bug, UFFI cannot know where a library is (because it can be anywhere). but, not being a bug, this remains a problem :) One solution is to search on LD_LIBRARY_PATH but this is not generalised (it should) for the moment. And of course, this is a solution that works for linux and not other platforms, so not perfect. Also we need to consider architecture, etc. etc. etc.
Esteban > On 23 Sep 2017, at 09:16, Stephane Ducasse <stepharo.s...@gmail.com> wrote: > > Can you open a bug entry and propose your solution? > > Stef > > On Fri, Sep 22, 2017 at 9:56 PM, Dan Wilczak <dan.g.wilc...@gmail.com> wrote: >> That pointed me in the right direction, thanks. I've got it working now. >> >> I think there's a bug there which may bite other people --- >> >> If you have both 32-bit and 64-bit versions of the library installed, >> Unix64ModuleName can find the >> 32-bit version first (depending on your LD_LIBRARY_PATH) and set that as the >> lib to use. Then when >> UFFI loads it, it recognizes it as 32-bit and gives up rather than looking >> in any more directories. >> >> Dan >> >> >> >> -- >> Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html >> >
