From: tornaria <tornaria@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [RC] sagemath: update to 10.2, flintlib: update to 3.0.1
Date: Thu, 16 Nov 2023 02:16:32 +0100 [thread overview]
Message-ID: <20231116011632.GOhd4JIVcEg9CJvQP3YivMopbxfTjNib39X6mNcSqHY@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-46832@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 870 bytes --]
New comment by tornaria on void-packages repository
https://github.com/void-linux/void-packages/pull/46832#issuecomment-1813570151
Comment:
> Can flint (and possibly sage) be built without ntl after this update? i read somewhere that ntl might not be necessary anymore, and this would ease the burden of cross compiling.
I think flintlib is already cross-compiled.
As for eclib, it lists `ntl-devel` in makedepends. Have you tried building it cross without `ntl-devel`? If it works, we can just add a build option ntl that is disabled by default in cross builds. However, I think that `eclib` actually uses `ntl` for some things.
As for sagemath, I think it has a few more nocross makedepends. The comment in the template list some; including flintlib, but I'm not sure this is a mistake. It's possible that sagemath needs a flintlib that was built with ntl.
next prev parent reply other threads:[~2023-11-16 1:16 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-46832@inbox.vuxu.org>
2023-10-26 12:12 ` [PR PATCH] [Updated] [WIP] flintlib: update to 3.0.0 tornaria
2023-10-29 16:05 ` dkwo
2023-10-30 19:23 ` [PR PATCH] [Updated] " tornaria
2023-10-31 1:28 ` tornaria
2023-10-31 1:43 ` [PR PATCH] [Updated] [WIP] flintlib: update to 3.0.0 / track sagemath-10.2 prereleases tornaria
2023-11-07 2:21 ` tornaria
2023-11-10 23:49 ` [PR PATCH] [Updated] [RC] sagemath: update to 10.2, flintlib: update to 3.0.1 tornaria
2023-11-11 12:21 ` tornaria
2023-11-12 19:38 ` [PR PATCH] [Updated] " tornaria
2023-11-14 21:56 ` tornaria
2023-11-15 0:51 ` tornaria
2023-11-15 8:05 ` dkwo
2023-11-15 8:08 ` dkwo
2023-11-16 1:16 ` tornaria [this message]
2023-11-16 1:19 ` [PR PATCH] [Updated] " tornaria
2023-11-18 4:51 ` tornaria
2023-11-19 18:06 ` [PR REVIEW] " dkwo
2023-11-19 18:08 ` dkwo
2023-11-20 14:24 ` dkwo
2023-11-21 20:39 ` [PR REVIEW] " dkwo
2023-11-22 17:23 ` tornaria
2023-12-01 11:01 ` [PR PATCH] [Updated] " tornaria
2023-12-01 21:08 ` tornaria
2023-12-03 14:20 ` tornaria
2023-12-03 16:18 ` [PR PATCH] [Updated] " tornaria
2023-12-03 16:21 ` tornaria
2023-12-03 18:29 ` dkwo
2023-12-03 19:21 ` dkwo
2023-12-08 16:05 ` [PR PATCH] [Merged]: " leahneukirchen
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=20231116011632.GOhd4JIVcEg9CJvQP3YivMopbxfTjNib39X6mNcSqHY@z \
--to=tornaria@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/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.
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 NNTP newsgroup(s).