Github messages for voidlinux
 help / color / mirror / Atom feed
From: tornaria <tornaria@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: maxima fails to build natively on aarch64
Date: Tue, 03 Oct 2023 02:12:12 +0200	[thread overview]
Message-ID: <20231003001212.0W2dUxr0CppijX6n6E3f0NjUcRukFsQQimzX0B3PeGs@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-46293@inbox.vuxu.org>

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

New comment by tornaria on void-packages repository

https://github.com/void-linux/void-packages/issues/46293#issuecomment-1743952946

Comment:
> `./xbps-src pkg -o ecl maxima` builds fine on `x86_64`.

Not sure I understand what you mean. The default for `x86_64` is ecl + sbcl. For `aarch64` the default is only ecl. The sbcl binary is faster, so when building ecl + sbcl the installer will set sbcl as the default. I.e., when you run just `maxima` you are running sbcl; if you run `maxima -l ecl` you are running ecl. The ecl binary we move to the `maxima-ecl` package, so if building only ecl maybe `maxima` won't work without the `maxima-ecl` package installed (can you check that? if so we can try to do something about it).

OTOH, when you say "downgrading to 5.46.0 fixes the issue", does that mean that you rebuilt using 5.46.0, or that you used an old xbps file? If the latter, maybe the issue is not with maxima itself, but with some change in ecl which was recently updated. Maybe there is something wrong with ecl on aarch64? Can you try different combinations:
 - does the maxima 5.47.0 that is cross built (i.e. the one in the repos) work?
 - what if you rebuild ecl natively, then build maxima natively, does that change something?

> on a side note, we carry matrixexp.patch (which sagemath does not, but they carry infodir.patch which we don't).

I don't think the infodir.patch does anything outside windows. I believe we carry matrixexp.patch because its still a actual bug worth fixing. IIRC the sagemath crowd decided to workaround the bug in sage itself and thus dropped the patch (since most maxima available in distros have the bug).

  parent reply	other threads:[~2023-10-03  0:12 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-27 15:28 [ISSUE] " dkwo
2023-09-29 13:44 ` dkwo
2023-09-29 13:45 ` dkwo
2023-10-02 21:51 ` dkwo
2023-10-03  0:12 ` tornaria [this message]
2023-10-03 14:22 ` dkwo
2023-10-11 22:13 ` maxima fails to build using ecl robert-dodier
2023-10-11 22:39 ` dkwo
2023-10-12  7:11 ` gunterkoenigsmann
2023-10-12 17:19 ` gunterkoenigsmann
2023-10-12 18:14 ` dkwo
2023-10-12 18:16 ` dkwo
2023-10-12 18:17 ` dkwo
2023-10-12 19:07 ` maxima fails to (natively) " dkwo
2023-10-12 19:24 ` dkwo
2023-10-12 19:48 ` robert-dodier
2023-10-12 19:51 ` robert-dodier
2023-10-12 20:13 ` dkwo
2023-10-12 20:27 ` dkwo
2023-10-12 21:03 ` dkwo
2023-10-13 10:58 ` tornaria
2023-10-14 19:48 ` dkwo
2023-10-16  3:00 ` robert-dodier
2023-10-16 18:01 ` [ISSUE] [CLOSED] " dkwo
2023-10-16 18:02 ` tornaria
2023-10-16 21:23 ` gunterkoenigsmann

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=20231003001212.0W2dUxr0CppijX6n6E3f0NjUcRukFsQQimzX0B3PeGs@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).