> On 5 Oct 2017, at 14:55, Hernán Morales Durand <hernan.mora...@gmail.com> > wrote: > > Forgot to comment that Nacl worked in Pharo 5.
yes but that was with NB and there are some minimum differences. I do not have the library and I lack the time to try more, but seems to me that here: apiCryptoHashSha512Output: outByteArray input: inByteArray inputLength: inByteArrayLength ^ self ffiCall: #(long crypto_hash_sha512_ref (byte * outByteArray, byte * inByteArray, ulonglong * inByteArrayLength)) module: 'libsodium’. instead "byte * outByteArray”, you want "byte **outByteArray” can you try? Esteban > > Cheers, > > Hernán > > 2017-10-05 3:23 GMT-03:00 Esteban Lorenzano <esteba...@gmail.com>: >> H Hernani, >> >> Most probably is a problem in the library and not UFFI, but I could not know >> without a crash report. >> >> Esteban >> >>> On 5 Oct 2017, at 06:00, Hernán Morales Durand <hernan.mora...@gmail.com> >>> wrote: >>> >>> Hi, >>> >>> I ported Nacl (a libsodium wrapper) from the old FFI apicall: format >>> to use the UFFI ffiCall:, but there should be something terribly wrong >>> because is crashing the VM, in both Windows 8.1 and Linux. >>> >>> How to reproduce in Pharo 6.1 >>> >>> Metacello new >>> smalltalkhubUser: 'tonyg' project: 'Crypto-Nacl'; >>> configuration: 'Nacl'; >>> version: #development; >>> load. >>> >>> (Nacl hashString: 'The quick brown fox jumps over the lazy dog') hex >>> >>> This one does deserve a bug entry? >>> >>> Cheers, >>> >>> Hernán >>> >> >> >