[Vm-dev] correct 32bit libssl library for CentOS 7.2?

[Tobias Pape]

On 17.04.2016, at 12:54, Bernhard Pieber <bernhard at pieber.com> wrote:

> 
> Thanks for the clarification, Tobias. Sounds a tad complicated, though. ;-)

Just history and pragmatism ;)

> 
> Cheers,
> Bernhard
> 
>> Am 17.04.2016 um 12:33 schrieb Tobias Pape <Das.Linux at gmx.de>:
>> 
>> On 17.04.2016, at 11:54, Bernhard Pieber <bernhard at pieber.com> wrote:
>>> Thank you for your help, Fabio!
>>> 
>>> I just copied the SqueakSSL file to the pharo-vm directory and it worked. :-) Great!
>>> 
>>> What is the other file (so.SqueakSSL) for?
>>> 
>>> I find it a bit surprising that I didn’t even have to remove libSqueakSSL.so.
>> 
>> This has to do with the different ways the different VMs handle plugin names.
>> 
>> Cog uses the way it was when it branched, that is a plugin is names
>> 
>> 	PLUGINNAME.so		(On Unix)	or
>> 	PLUGINNAME.dll		(On Windows)	or
>> 	PLUGINNAME.dylib	(On OS X)
>> 
>> After that, Ian Piumarta, maintaining the unix part of the platform tree, 
>> found that PLUGINNAME.so is not always compatible on all Unicies out there.
>> I do not recall correctly, but presumably, some Solaris couldn't find plugins 
>> then or something. So he changed it for _Unix_ to
>> 
>> 	so.PLUGINNAME
>> 
>> During Pharo development, people decided to make plugins look more like libraries
>> (please correct me here, I'm just speculating) and so we have for Unix Pharos:
>> 
>> 	libPLUGINNAME.so
>> 
>> 
>> Most VMs try also find plugins of other naming conventions. That's why you see
>> Pharo also loading SqueakSSL.so. It apparently tries the first variant before the
>> thrid.