From: Andreas Enge <andreas@enge.fr>
To: Romain GARBAGE <romain.garbage@inria.fr>
Cc: Eric Bavier <bavier@posteo.net>,
Sharlatan Hellseher <sharlatanus@gmail.com>,
68682@debbugs.gnu.org, Efraim Flashner <efraim@flashner.co.il>
Subject: [bug#68682] [PATCH] gnu: maths: arpack-ng: Modify build settings.
Date: Wed, 24 Jan 2024 15:04:37 +0100 [thread overview]
Message-ID: <ZbEY9eCjz3yOfJd6@jurong> (raw)
In-Reply-To: <4284df7d0499bb5b6a46d29d6e7f858fd3baa896.1706085982.git.romain.garbage@inria.fr>
Hello Romain,
Am Wed, Jan 24, 2024 at 09:46:22AM +0100 schrieb Romain GARBAGE:
> * gnu/packages/maths.scm (arpack-ng): Add configure flags for building
> the shared library and the iso C bindings.
thanks for sending the patch!
I see that the ISO C binding flag installs additional headers, but I do not
see why the flag for building shared libraries would be needed. In the current
arpack-ng, there is already a shared library in the lib/ subdirectory.
Could you explain how adding the flag makes a difference?
Andreas
PS: Concerning the commit message, we usually do not mention the module
and just start by "gnu: arpack-ng:" without "maths:".
next prev parent reply other threads:[~2024-01-24 14:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-24 8:46 [bug#68682] [PATCH] gnu: maths: arpack-ng: Modify build settings Romain GARBAGE
2024-01-24 14:04 ` Andreas Enge [this message]
2024-01-24 14:07 ` Andreas Enge
2024-01-24 14:51 ` Ludovic Courtès
2024-01-24 16:04 ` Romain Garbage
2024-01-24 16:21 ` Andreas Enge
2024-01-24 16:28 ` [bug#68682] [PATCH v2 1/2] gnu: arpack-ng: Add preprocessor flag Andreas Enge
2024-01-24 16:28 ` [bug#68682] [PATCH v2 2/2] gnu: arpack-ng: Update to 3.9.1 Andreas Enge
2024-02-10 21:58 ` [bug#68682] [PATCH v2 1/2] gnu: arpack-ng: Add preprocessor flag Ludovic Courtès
2024-02-11 7:55 ` Andreas Enge
2024-02-14 13:54 ` bug#68682: Close Andreas Enge
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=ZbEY9eCjz3yOfJd6@jurong \
--to=andreas@enge.fr \
--cc=68682@debbugs.gnu.org \
--cc=bavier@posteo.net \
--cc=efraim@flashner.co.il \
--cc=romain.garbage@inria.fr \
--cc=sharlatanus@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.