David Thompson <dthomps...@worcester.edu> skribis:
> From 873dffc9dc892ad252a33b2b27f28d41573d6bf7 Mon Sep 17 00:00:00 2001
> From: David Thompson <dthomps...@worcester.edu>
> Date: Wed, 25 Jun 2014 20:32:23 -0400
> Subject: [PATCH] gnu: Add libsodium.
>
> * gnu-system.am (GNU_SYSTEM_MODULES): Add crypto.scm.
> * gnu/packages/crypto.scm: New file.
Looks good to me.
However, the web page reads:
In order to pick the fastest working implementation of each primitive,
NaCl performs tests and benchmarks at compile-time. Unfortunately,
the resulting library is not guaranteed to work on different hardware.
Which means that Hydra would end up building a version that uses the
specific ISA extensions that happened to be available on the build
machine, which in turn might be unavailable on the user’s machine.
Is there a way to disable the compile-time magic, and instead let
libsodium make the choice at run time? GMP has --enable-fat for that
purpose.
Thanks,
Ludo’.
PS: Apparently this NaCl is unrelated to Google’s NaCl sandboxing
thing; terrible!
