From: zimoun <zimon.toutoune@gmail.com>
To: "Ludovic Courtès" <ludovic.courtes@inria.fr>
Cc: Guix Devel <guix-devel@gnu.org>
Subject: Re: Proposal for a blog contribution on reproducible computations
Date: Fri, 10 Jan 2020 18:19:20 +0100 [thread overview]
Message-ID: <CAJ3okZ3O=bTOqbqckUzmA5HkZ+ty8Ny4D=FoM8iD3+m_k6-gxQ@mail.gmail.com> (raw)
In-Reply-To: <87h813uu1v.fsf@gnu.org>
Hi Ludo,
On Fri, 10 Jan 2020 at 17:59, Ludovic Courtès <ludovic.courtes@inria.fr> wrote:
> • In the ‘guix pack’ example, you could perhaps omit all the -S flags
> except for /bin, and mention ‘--save-provenance’.
I am the culprit.
The invocation of "guix pack -f docker" is not clear to me. So
basically, I copied/pasted the lines here [1] :-) because it works all
the time.
[1] http://bioinformatics.mdc-berlin.de/pigx/supplementary-materials.html
That said, I also find interesting the command-line and hashes comparisons:
--8<---------------cut here---------------start------------->8---
/usr/bin/gcc pi.c -o pi-debian-gcc8
docker run -v `pwd`:`pwd` -w `pwd` -ti gcc-toolchain gcc pi.c -o pi-docker
guix environment --container --ad-hoc gcc-toolchain -- gcc pi.c -o pi-guix
md5sum pi-*
b268af34d62763a2a707944403bf7b0b pi-debian-gcc8
1be3c1b5d1e065017e4c56f725b1a692 pi-docker
1be3c1b5d1e065017e4c56f725b1a692 pi-guix
--8<---------------cut here---------------end--------------->8---
Anyway! :-)
> • Would it make sense to mention MPFR in the paragraph about IEEE 754?
And MPFI? ;-)
All the best,
simon
next prev parent reply other threads:[~2020-01-10 17:19 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-05 14:16 Feedback from JRES in Dijon Julien Lepiller
2019-12-05 14:34 ` Pierre Neidhardt
2019-12-05 14:42 ` Julien Lepiller
2019-12-05 15:44 ` Konrad Hinsen
2019-12-05 15:52 ` zimoun
2019-12-06 7:07 ` Bengt Richter
2019-12-06 12:24 ` Konrad Hinsen
2019-12-07 16:35 ` Timothy Sample
2019-12-08 2:48 ` Bengt Richter
2019-12-08 4:11 ` Timothy Sample
2019-12-08 23:09 ` Bengt Richter
2019-12-09 5:23 ` Konrad Hinsen
2019-12-06 12:57 ` Konrad Hinsen
2019-12-10 16:57 ` Ludovic Courtès
2019-12-11 20:48 ` Konrad Hinsen
2020-01-07 16:05 ` Proposal for a blog contribution on reproducible computations Konrad Hinsen
2020-01-09 20:40 ` zimoun
2020-01-10 16:59 ` Ludovic Courtès
2020-01-10 17:19 ` zimoun [this message]
2020-01-10 18:53 ` Giovanni Biscuolo
2020-01-11 9:31 ` Konrad Hinsen
2020-01-11 14:05 ` Giovanni Biscuolo
2020-01-13 8:37 ` Ludovic Courtès
2020-01-14 9:06 ` Konrad Hinsen
2020-01-14 15:38 ` Ludovic Courtès
2020-01-14 16:18 ` Konrad Hinsen
2020-01-14 16:40 ` Ludovic Courtès
2020-01-10 17:03 ` Ludovic Courtès
2020-01-11 9:39 ` Konrad Hinsen
2020-01-15 22:20 ` Ludovic Courtès
2019-12-05 15:47 ` Feedback from JRES in Dijon zimoun
2019-12-05 14:39 ` Julien Lepiller
2019-12-05 15:42 ` zimoun
2019-12-10 17:06 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAJ3okZ3O=bTOqbqckUzmA5HkZ+ty8Ny4D=FoM8iD3+m_k6-gxQ@mail.gmail.com' \
--to=zimon.toutoune@gmail.com \
--cc=guix-devel@gnu.org \
--cc=ludovic.courtes@inria.fr \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.