Github messages for voidlinux
 help / color / mirror / Atom feed
From: tornaria <tornaria@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: giac does not support arbitrary precision floating point
Date: Tue, 23 Feb 2021 16:20:47 +0100	[thread overview]
Message-ID: <20210223152047.bKKWI0xVuSxGyXj5MVILgd4wW2eNFgeF9SEHDvVbHA8@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-28989@inbox.vuxu.org>

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

New comment by tornaria on void-packages repository

https://github.com/void-linux/void-packages/issues/28989#issuecomment-784277765

Comment:
While doing that I run `xbps-src check` and found that several tests fail, revealing that other dependencies are missing:
- in the current version: 12 tests fail
- adding `mpfr-devel` to `makedepends`: 9 tests fail
- adding also `pari-devel`: 2 tests fail
- adding a patch found in [`sagemath`](https://trac.sagemath.org/ticket/25567#comment:41): 1 tests fail
I wasn't able to get rid of the last fail (a segmentation fault).

Should I do all of that in a single PR, or split?

Comments:
- For the remaining test failure, I will open another issue. I should point out that `sagemath` compiles giac (I think the same version as in void) and that one does NOT have the segfault so this might be worth looking into.
- There are more (optional?) dependencies for giac, some of them are available in void, namely: `libao-devel libsamplerate-devel libcurl-devel libICE-devel glpk-devel gmpxx-devel ecm-devel`. If adding them to `makedepends`, they are found by configure, but they don't affect tests. I'm not sure if I should also add those dependencies or not. In case of doubt, I'll stick to the changes described above (mpfr and pari)
- For the record, other (optional?) dependencies not available in void are `mpfi ntl CoCoA nauty`
- I'm not a direct user of `giac`, but I would like to package `sagemath` or at least make it easy to compile with as many system packages as possible. The original issue was caught by running sage tests.

  parent reply	other threads:[~2021-02-23 15:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-23  3:45 [ISSUE] " tornaria
2021-02-23  4:02 ` ericonr
2021-02-23 15:20 ` tornaria [this message]
2021-02-24 10:07 ` dkwo
2021-03-08 20:08 ` ericonr
2021-03-08 20:08 ` [ISSUE] [CLOSED] " ericonr

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=20210223152047.bKKWI0xVuSxGyXj5MVILgd4wW2eNFgeF9SEHDvVbHA8@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).