From: "Ludovic Courtès" <ludovic.courtes@inria.fr>
To: Andreas Enge <andreas@enge.fr>
Cc: Romain GARBAGE <romain.garbage@inria.fr>,
Sharlatan Hellseher <sharlatanus@gmail.com>,
68682@debbugs.gnu.org, Efraim Flashner <efraim@flashner.co.il>,
Eric Bavier <bavier@posteo.net>
Subject: [bug#68682] [PATCH] gnu: maths: arpack-ng: Modify build settings.
Date: Wed, 24 Jan 2024 15:51:52 +0100 [thread overview]
Message-ID: <878r4evl6f.fsf@gnu.org> (raw)
In-Reply-To: <ZbEY9eCjz3yOfJd6@jurong> (Andreas Enge's message of "Wed, 24 Jan 2024 15:04:37 +0100")
Hi! :-)
Andreas Enge <andreas@enge.fr> skribis:
> 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?
The goal should be to build shared libraries only. If that’s already
happening without passing ‘-DBUILD_SHARED_LIBS=ON’, I agree we can drop
it, in an effort to keep the package definition minimal.
Romain, could you confirm that ‘-DBUILD_SHARED_LIBS=ON’ is indeed
unnecessary and send a new version without it if it is?
Thanks,
Ludo’.
next prev parent reply other threads:[~2024-01-24 14:53 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
2024-01-24 14:07 ` Andreas Enge
2024-01-24 14:51 ` Ludovic Courtès [this message]
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
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=878r4evl6f.fsf@gnu.org \
--to=ludovic.courtes@inria.fr \
--cc=68682@debbugs.gnu.org \
--cc=andreas@enge.fr \
--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 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).