unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Thompson, David" <dthompson2@worcester.edu>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: [PATCH] gnu: Add libsodium
Date: Thu, 26 Jun 2014 09:03:18 -0400	[thread overview]
Message-ID: <CAJ=RwfYjspwVQoH01+mawFALhcUFrSRKTOqRwX1mdiMLMwOJ6A@mail.gmail.com> (raw)
In-Reply-To: <87a98zu99f.fsf@gnu.org>

On Thu, Jun 26, 2014 at 8:48 AM, Ludovic Courtès <ludo@gnu.org> wrote:

> 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.

Well, Sodium is a fork on NaCL, and underneath that paragraph it reads:

  Sodium performs tests at run-time, so that the same binary package
can still run everywhere.

So, I think we are okay!  This is a good advantage of Sodium over NaCl.

With that concern out of the way, okay to push?

> PS: Apparently this NaCl is unrelated to Google’s NaCl sandboxing
>     thing; terrible!

Confused me as well.

Thanks.  I appreciate your thorough reviews.

- Dave

  reply	other threads:[~2014-06-26 13:03 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-26  0:39 [PATCH] gnu: Add libsodium David Thompson
2014-06-26  5:09 ` John Darrington
2014-06-26 11:43   ` David Thompson
2014-06-26 12:44     ` Ludovic Courtès
2014-06-26 12:48 ` Ludovic Courtès
2014-06-26 13:03   ` Thompson, David [this message]
2014-06-26 13:57     ` Ludovic Courtès

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAJ=RwfYjspwVQoH01+mawFALhcUFrSRKTOqRwX1mdiMLMwOJ6A@mail.gmail.com' \
    --to=dthompson2@worcester.edu \
    --cc=guix-devel@gnu.org \
    --cc=ludo@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).