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 (natively) build using ecl
Date: Mon, 16 Oct 2023 20:02:15 +0200	[thread overview]
Message-ID: <20231016180215.E7pkyYwB_zccyQHNieH5kNeuJfeY58KRT__UHrzjGqo@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: 1898 bytes --]

New comment by tornaria on void-packages repository

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

Comment:
> @dkwo No problem, I'm glad to help. Looks like you have figured out what the basic problem is, good luck from here on out.

@robert-dodier sorry for the confusion with my bad `use-shared-library.patch`. I've since improved it so the binary that is built works without having to fiddle with `patchelf`.

Please let me know if I can help to upstream some of the patches we have in https://github.com/tornaria/void-packages/tree/maxima/srcpkgs/maxima/patches. I think at least the following would be quite reasonable to upstream:
 - [handle-multiple-ldflags.patch](https://github.com/tornaria/void-packages/blob/maxima/srcpkgs/maxima/patches/handle-multiple-ldflags.patch) Handle multiple LDFLAGS.
 - [matrixexp.patch](https://github.com/tornaria/void-packages/blob/maxima/srcpkgs/maxima/patches/matrixexp.patch) Fix error in matrix exponentiation.
 - [maxima-sbcl-with-gmp.patch](https://github.com/tornaria/void-packages/blob/maxima/srcpkgs/maxima/patches/maxima-sbcl-with-gmp.patch) Patch maxima initialization for sbcl so it uses gmp for arithmetic.
 - [musl-round.patch](https://github.com/tornaria/void-packages/blob/maxima/srcpkgs/maxima/patches/musl-round.patch) Add a bit more room for rounding errors which cause two tests to fail on x86_64-musl.

Also a comment about documentation. The tarball includes all the documentation so it is not necessary to rebuild. However:
 - Configure will write makefiles and maybe a version file, and building documentation depends on the makefiles so they are rebuild nonetheless. I workaround that by `touch`ing the target files after configure.
 - There's an option to configure to skip building documentation. Unfortunately, it also disables installing the documentation, so it doesn't help us.

  parent reply	other threads:[~2023-10-16 18:02 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-27 15:28 [ISSUE] maxima fails to build natively on aarch64 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
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 [this message]
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=20231016180215.E7pkyYwB_zccyQHNieH5kNeuJfeY58KRT__UHrzjGqo@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).