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
/lib64/libcurl-gnutls.so.4 And the last step is following the
instructions related with some security parameters: you must create a
file, /etc/security/limits.d/pharo.conf cat pharo.conf * hard rtprio 2 *
soft rtprio 2 Reboot, and pharo works fine.
/[/12:32 AM/]/arkaitzmugica/:/
If working with 'toolbox' command line tool, like me, because I'm using
Fedora 31 Silverblue, you should keep this in mind too when creating a
container with a custom Dockerfile.
/[/12:34 AM/]/arkaitzmugica/:/
I haven't tested, but I think it could work also for Centos and RHEL.
Pierre.
On 12/01/2020 19:52, Jan Blizničenko wrote:
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 makes Launcher unusable on both systems for both reasons (cannot
hotfix launcher itself and have to hotfix all VMs it downloads).
Jan
--
Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html
