Github messages for voidlinux
 help / color / mirror / Atom feed
From: tornaria <tornaria@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: New math packages: cddlib, singular
Date: Mon, 06 Sep 2021 13:50:25 +0200	[thread overview]
Message-ID: <20210906115025.7wPm72H_6SdaYSsizMMhsnLYDDdY1C9jopX9VP3jIjE@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-32822@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 747 bytes --]

New comment by tornaria on void-packages repository

https://github.com/void-linux/void-packages/pull/32822#issuecomment-913585978

Comment:
> Btw, the packages `ntl-devel` and `flintlib-devel` are not even found on the Void homepage - packages for `arm` and `aarch`, what am I missing here? does it have to do with `nocross=yes` in ntl?

There is no native builder for arm, so `nocross` packages won't be available on arm.

Since `ntl` is optional to `flintlib` and singular, one option would be to disable ntl on cross builds. I was pointed to `vips` for an example: add a build_option `ntl` and have it enabled by default only if not cross-compiling. I'm not in a hurry to do that, let's get x86 working and later we can worry about cross.

  parent reply	other threads:[~2021-09-06 11:50 UTC|newest]

Thread overview: 54+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-03 16:05 [PR PATCH] " dkwo
2021-09-03 16:12 ` dkwo
2021-09-03 20:45 ` [PR REVIEW] " paper42
2021-09-03 21:34 ` tornaria
2021-09-03 21:38 ` tornaria
2021-09-03 21:38 ` tornaria
2021-09-03 22:12 ` tornaria
2021-09-03 22:21 ` tornaria
2021-09-06  9:01 ` [PR REVIEW] " dkwo
2021-09-06  9:43 ` dkwo
2021-09-06  9:44 ` dkwo
2021-09-06  9:45 ` [PR PATCH] [Updated] " dkwo
2021-09-06  9:50 ` dkwo
2021-09-06  9:52 ` [PR PATCH] [Updated] " dkwo
2021-09-06  9:53 ` dkwo
2021-09-06  9:55 ` [PR PATCH] [Updated] " dkwo
2021-09-06  9:55 ` dkwo
2021-09-06 11:09 ` dkwo
2021-09-06 11:20 ` dkwo
2021-09-06 11:50 ` tornaria [this message]
2021-09-06 11:59 ` tornaria
2021-09-06 12:31 ` dkwo
2021-09-06 12:44 ` dkwo
2021-09-11 15:20 ` dkwo
2021-09-11 15:20 ` dkwo
2021-09-11 16:08 ` [PR PATCH] [Updated] " dkwo
2021-09-12 13:50 ` tornaria
2021-09-13  7:35 ` dkwo
2021-09-20 15:57 ` [PR PATCH] [Updated] " dkwo
2021-09-20 16:13 ` dkwo
2021-09-20 16:33 ` tornaria
2021-09-20 16:47 ` [PR PATCH] [Updated] " dkwo
2021-09-20 17:02 ` dkwo
2021-09-21  8:21 ` dkwo
2021-09-23  9:28 ` [PR PATCH] [Updated] " dkwo
2021-09-23  9:38 ` dkwo
2021-10-07  8:38 ` dkwo
2021-10-13 17:11 ` [PR PATCH] [Updated] " dkwo
2021-10-13 17:15 ` dkwo
2021-10-22 12:45 ` dkwo
2021-11-08 23:04 ` leahneukirchen
2021-11-09 10:43 ` [PR PATCH] [Updated] " dkwo
2021-11-09 10:47 ` dkwo
2021-11-09 10:59 ` dkwo
2021-11-09 11:27 ` tornaria
2021-11-09 11:38 ` tornaria
2021-11-09 12:15 ` [PR PATCH] [Updated] " dkwo
2021-11-09 12:27 ` dkwo
2021-11-09 12:45 ` tornaria
2021-11-09 15:44 ` leahneukirchen
2021-11-09 15:44 ` leahneukirchen
2021-11-09 15:46 ` [PR PATCH] [Updated] " dkwo
2021-11-09 15:48 ` dkwo
2021-11-09 16:02 ` [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=20210906115025.7wPm72H_6SdaYSsizMMhsnLYDDdY1C9jopX9VP3jIjE@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).