all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludovic.courtes@inria.fr>
To: "Maurice Brémond" <Maurice.Bremond@inria.fr>
Cc: 37646-done@debbugs.gnu.org
Subject: bug#37646: [PATCH] gnu: mumps: Update to 5.2.1 and add shared libraries
Date: Mon, 14 Oct 2019 18:28:09 +0200	[thread overview]
Message-ID: <87r23fpa06.fsf@gnu.org> (raw)
In-Reply-To: <87sgo4k657.fsf@inria.fr> ("Maurice \=\?utf-8\?Q\?Br\=C3\=A9mond\=22\?\= \=\?utf-8\?Q\?'s\?\= message of "Mon, 07 Oct 2019 14:00:04 +0000")

Hi Maurice,

Maurice Brémond <Maurice.Bremond@inria.fr> skribis:

> ---
>  gnu/packages/maths.scm                   | 53 ++++++++++------
>  gnu/packages/patches/shared-libseq.patch | 42 +++++++++++++
>  gnu/packages/patches/shared-mumps.patch  | 63 +++++++++++++++++++
>  gnu/packages/patches/shared-pord.patch   | 77 ++++++++++++++++++++++++
>  4 files changed, 218 insertions(+), 17 deletions(-)
>  create mode 100644 gnu/packages/patches/shared-libseq.patch
>  create mode 100644 gnu/packages/patches/shared-mumps.patch
>  create mode 100644 gnu/packages/patches/shared-pord.patch

Thanks for the patch!  :-)

I took the liberty to split it: one patch for the update, and one patch
for shared library support.

I simplified shared library support by resorting to ‘$ORIGIN’ for the
RUNPATH instead of using PatchELF.  And that’s about it.

The result is these two commits:

  06e1239502 gnu: mumps: Build and install shared libraries.
  5dbc79eb60 gnu: mumps: Update to 5.2.1.

Let me know if anything is amiss!

Thank you,
Ludo’.

      reply	other threads:[~2019-10-14 16:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-07 14:00 [bug#37646] [PATCH] gnu: mumps: Update to 5.2.1 and add shared libraries Maurice Brémond
2019-10-14 16:28 ` Ludovic Courtès [this message]

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=87r23fpa06.fsf@gnu.org \
    --to=ludovic.courtes@inria.fr \
    --cc=37646-done@debbugs.gnu.org \
    --cc=Maurice.Bremond@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.