> On 16.02.2018, at 19:23, tim Rowledge <tim at rowledge.org> wrote:
> 
> 
> 
>> On 16-02-2018, at 7:37 AM, Louis LaBrunda <Lou at Keystone-Software.com> wrote:
>> I don't seem to have a folder /lib/i386-linux-gnu, so
>> I'm going to see if I can figure out how to load/install it.
> 
> You shouldn’t have any i386 directory on a Pi! On my Pi's the libcrypto is in /usr/lib/arm-linux-gnueabihf as is libssl. 
> The working setup has libcrypto.so.1.0.0 & libssl.so.1.0.0, the non-working has libcrypto.so.1.0.2 & ibssl.so.1.0.2 
> 
> Now it’s true that I’ve never been able to make sense of the way unix chooses to connect libraries nor indeed the way our makefiles persuade things to link up, but is it possible that the vm on my non-working setup simply isn’t willing to connect to a version 1.0.2 library?
> 

Folks, can you try a VM or at least a SqueakSSL plugin from this fortnight? :)

I mean, eg squeak.cog.spur_linux32ARMv6_itimer_201802072244.tar.gz

It does no longer link directly to libssl/libcrypto but dynamically loads it. This should actually help…
But then again… it _should_ …


Best regards
	-Tobias


> tim
> --
> tim Rowledge; tim at rowledge.org; http://www.rowledge.org/tim
> User: A harmless drudge.
> 
> 
>