I guess you could try a symbolic link.
sudo ln -s /lib/i386-linux-gnu/libcrypto.so.1.0.0 '/home/chris/Desktop/sqsistaspurlinuxht/lib/squeak/5.0-201802061430/libcrypto.so'
Chris
Hi Chris,
When I run apt install libssl1.0.2 it says the latest version is already installed. From your suggestion I'm guessing that Squeak expects the file(s) to be named differently. But I can't find libssl* or libcrypto* or anything. 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.
Lou
On Fri, 16 Feb 2018 09:59:29 -0500, Chris Cunnington brasspen@gmail.com wrote:
I guess you could try a symbolic link.
sudo ln -s /lib/i386-linux-gnu/libcrypto.so.1.0.0 '/home/chris/Desktop/sqsistaspurlinuxht/lib/squeak/5.0-201802061430/libcrypto.so'
Chris
On 16-02-2018, at 7:37 AM, Louis LaBrunda Lou@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?
tim -- tim Rowledge; tim@rowledge.org; http://www.rowledge.org/tim User: A harmless drudge.
On 16.02.2018, at 19:23, tim Rowledge tim@rowledge.org wrote:
On 16-02-2018, at 7:37 AM, Louis LaBrunda Lou@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@rowledge.org; http://www.rowledge.org/tim User: A harmless drudge.
squeak-dev@lists.squeakfoundation.org
-
Chris Cunnington -
Louis LaBrunda -
tim Rowledge -
Tobias Pape