From: Efraim Flashner <efraim@flashner.co.il>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 73197@debbugs.gnu.org,
"Ludovic Courtès" <ludovic.courtes@inria.fr>,
"Philippe Virouleau" <philippe.virouleau@inria.fr>,
"Simon Tournier" <zimon.toutoune@gmail.com>
Subject: [bug#73197] [PATCH] gnu: julia: Update to 1.9.3.
Date: Mon, 16 Sep 2024 10:50:22 +0300 [thread overview]
Message-ID: <ZufjPjnj4aZbjxiV@3900XT> (raw)
In-Reply-To: <d9e54f64579b184f4715713101f13f01c809873a.1726147051.git.ludo@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 2116 bytes --]
On Thu, Sep 12, 2024 at 03:22:50PM +0200, Ludovic Courtès wrote:
> From: Ludovic Courtès <ludovic.courtes@inria.fr>
>
> * gnu/packages/julia.scm (julia): Update to 1.9.3.
> [arguments]: Use gexps.
> [inputs, native-inputs]: Remove labels.
> * gnu/packages/llvm.scm (llvm-julia): Rename to…
> (llvm-14-julia): … this. Upgrade to 14.0.6-3.
> * gnu/packages/patches/julia-1.9-build-tweaks.patch: New file.
> * gnu/packages/patches/julia-Use-MPFR-4.2.patch: Remove.
> * gnu/local.mk (dist_patch_DATA): Adjust accordingly.
>
> Co-authored-by: Philippe Virouleau <philippe.virouleau@inria.fr>
> Change-Id: I6ef35c6cd31741a7725b50364dd0f8fa6a0c6424
> ---
> gnu/local.mk | 2 +-
> gnu/packages/julia.scm | 862 ++++++++++--------
> gnu/packages/llvm.scm | 38 +-
> .../patches/julia-1.9-build-tweaks.patch | 152 +++
> gnu/packages/patches/julia-Use-MPFR-4.2.patch | 228 -----
> 5 files changed, 651 insertions(+), 631 deletions(-)
> create mode 100644 gnu/packages/patches/julia-1.9-build-tweaks.patch
> delete mode 100644 gnu/packages/patches/julia-Use-MPFR-4.2.patch
>
> Hello comrades!
>
> Here is an update of Julia adapted from:
>
> https://gitlab.inria.fr/guix-hpc/guix-hpc/-/commit/eb83e466fe0b9492216abc46da26ec3a89b0a946
>
> Version 1.9.3 has been in the guix-hpc channel for a while. It’s not
> the latest version, not even the latest series, but it’s an improvement
> over what we have.
>
> Thoughts?
>
> Ludo’.
I tested it out on my machines and it built without problems on x86_64
and aarch64. However, I was unable to compile the julia packages we have
when there were some julia inputs.
Do we want to add it in as julia-next, and then we can continue pushing
the version forward and working on the package build failures separately?
--
Efraim Flashner <efraim@flashner.co.il> רנשלפ םירפא
GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2024-09-16 7:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-12 13:22 [bug#73197] [PATCH] gnu: julia: Update to 1.9.3 Ludovic Courtès
2024-09-16 7:50 ` Efraim Flashner [this message]
2024-09-16 9:47 ` Ludovic Courtès
2024-09-20 15:29 ` Simon Tournier
2024-09-22 7:24 ` Efraim Flashner
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=ZufjPjnj4aZbjxiV@3900XT \
--to=efraim@flashner.co.il \
--cc=73197@debbugs.gnu.org \
--cc=ludo@gnu.org \
--cc=ludovic.courtes@inria.fr \
--cc=philippe.virouleau@inria.fr \
--cc=zimon.toutoune@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 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).