The VM crash for Launcher is not caused by having different VM, but by using
specific usage of SSL lib that does not work with this workaround. I added
more details into new issue I created for vm:
https://github.com/pharo-project/opensmalltalk-vm/issues/62
Jan
--
Sent from:
Thank you for forwarding this. At first, I though "well, that is the same
solution I posted in previous mail/post, you just have libs in different
directory", but it is not. It creates link just once in lib64, not in each
VM, which is way better (but has be done by root). Unfortunately, it does
Arkaitzmugica posted this on discord, which worked for him. Since
the problems were similar, that may be relevant for you (or other
people)
12:28 AM/]/arkaitzmugica/:/
I've made Pharo work on Fedora 31. First libgit2-devel must be
installed. Then sudo ln -s /lib64/libcurl.so.4
So it seems the good old
ln -s /usr/lib64/libcurl.so.4 (path to
pharo)/pharo-vm/lib/pharo/(version)/libcurl-gnutls.so.4
still works after all, just not with Pharo Launcher VM (where it causes
segfault). With regular VMs downloaded either manually or via the Launcher
itself it works.
Too bad it
Hello
Thank you for this script. Unfortunately it does not seem to work for me.
After downloading that VM you linked and downloaded image with sources,
image opens and immediately crashes:
ioLoadModule(//home/honza/Downloads/pharo64-linux-stable/lib/pharo/5.0-201902062351/libgit2.so):
It's exclusively due curl-gnutls (libcurl linked against GNUtls instead of
OpenSSL for license preference). A version of OpenSSL1.0.0 seems to be in the
bundle.
This was tested against
http://files.pharo.org/get-files/80/pharo64-linux-stable.zip
1.) Download that file
2.) unzip that file
Hi,
I just ran into the very same problem and into further problems when building
from source. I will try to see which help I can provide to come to a solution:
libgit2 requires libssh2 which requires OpenSSL 1.0.x which is not
installed/installable.
Building fails as OpenSUSE puts amd64
