From: zimoun <zimon.toutoune@gmail.com>
To: "Nicolò Balzarotti" <anothersms@gmail.com>
Cc: 41167@debbugs.gnu.org
Subject: [bug#41167] Julia: fix current patches, upgrade to 1.4.1
Date: Wed, 13 May 2020 02:11:49 +0200 [thread overview]
Message-ID: <CAJ3okZ0mhtva5ePoYZLYKrUfQeYHvVaC3c5qTBs2WGjZucFT0w@mail.gmail.com> (raw)
In-Reply-To: <873688i57c.fsf@guixSD.i-did-not-set--mail-host-address--so-tickle-me>
Hi Nicolò,
On Sun, 10 May 2020 at 10:08, Nicolò Balzarotti <anothersms@gmail.com> wrote:
> - fixed the julia-SOURCE_DATE_EPOCH-mtime.patch: It's now a meta-patch,
> that creates the right patch file, so the current julia version is not
> patched, and precompile cache of packages installed with guix is
> broken. Still no julia-package is in guix, that's why it went
> unnoticed
Does this fix the unreproducible behaviour of Julia? As described in
this bug [1] and discussed at length for v1.3.
> - Update julia to latest release, v1.4.1. I was finally able to
> unbundle the last pieces of bundled software (libwhich). Now julia
> is based on llvm-8 (previously on llvm-6) and I measuread a speedup of
> ~17x on precompile times
Because my machine (of lockdown) is not enough powerful, I cannot
rebuild Julia v1.4.1 with the option '--check'.
Could you report the status on the reproducibility of Julia with this
new version?
BTW, thank you for this important update!
Hope to play with it soon.
Cheers,
simon
ps:
hope that your PhD defense was fine?
next prev parent reply other threads:[~2020-05-13 0:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-10 8:07 [bug#41167] Julia: fix current patches, upgrade to 1.4.1 Nicolò Balzarotti
2020-05-13 0:11 ` zimoun [this message]
2020-05-13 10:13 ` Nicolò Balzarotti
2020-05-13 18:38 ` zimoun
2020-05-13 11:04 ` Efraim Flashner
[not found] ` <CAJ3okZ3hjN6umT7bapg1CU4k+pChEio1rk78M0uz5j18oucbNA@mail.gmail.com>
2020-05-13 18:44 ` bug#22304: Julia v1.4.1 still not reproducible zimoun
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=CAJ3okZ0mhtva5ePoYZLYKrUfQeYHvVaC3c5qTBs2WGjZucFT0w@mail.gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=41167@debbugs.gnu.org \
--cc=anothersms@gmail.com \
/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.