unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Simon Tournier <zimon.toutoune@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>, 62183@debbugs.gnu.org
Cc: "Ludovic Courtès" <ludovic.courtes@inria.fr>
Subject: [bug#62183] [PATCH v2 2/2] gnu: vtk: Remove reference to GCC.
Date: Fri, 07 Apr 2023 17:38:25 +0200	[thread overview]
Message-ID: <874jprln2m.fsf@gmail.com> (raw)
In-Reply-To: <20230320220956.13920-2-ludo@gnu.org>

Hi,

On lun., 20 mars 2023 at 23:09, Ludovic Courtès <ludo@gnu.org> wrote:

> This removes GCC from the closure of VTK, reducing its size by 200 MiB
> (17%).

Awesome!  Well done! :-)

Cheers,
simon

PS: Following the meeting with Kitware folks, you did not tweak
Paraview, right?

 + PARAVIEW_ENABLE_CATALYST because catalyst is not packages yet
 + No dependencies to OSPRay, OpenVDB, OpenXR, ADIOS2, Fides, OpenTURNS,
   TTK, etc.

And ’paraview’ is only packages in Guix proper and not in some guix-hpc
channels, right?  Well, the only versions [1] I found are from Guix
proper.

1: https://hpc.guix.info/browse 




  parent reply	other threads:[~2023-04-07 16:55 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-14 11:04 [bug#62183] [PATCH 0/2] VTK packaging improvements for HPC Ludovic Courtès
2023-03-14 11:06 ` [bug#62183] [PATCH 1/2] gnu: vtk: Enable OpenMP, TBB, and Open MPI support Ludovic Courtès
2023-03-14 11:06   ` [bug#62183] [PATCH 2/2] gnu: vtk: Remove reference to GCC Ludovic Courtès
2023-03-20 22:09 ` [bug#62183] [PATCH v2 1/2] gnu: vtk: Enable OpenMP, TBB, and Open MPI support Ludovic Courtès
2023-03-20 22:09   ` [bug#62183] [PATCH v2 2/2] gnu: vtk: Remove reference to GCC Ludovic Courtès
2023-03-21 18:12     ` bug#62183: [PATCH 0/2] VTK packaging improvements for HPC Ludovic Courtès
2023-04-07 15:38     ` Simon Tournier [this message]
2023-04-17  8:17       ` [bug#62183] [PATCH v2 2/2] gnu: vtk: Remove reference to GCC 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=874jprln2m.fsf@gmail.com \
    --to=zimon.toutoune@gmail.com \
    --cc=62183@debbugs.gnu.org \
    --cc=ludo@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 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).