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: Fri, 13 Oct 2023 12:58:31 +0200	[thread overview]
Message-ID: <20231013105831.gGI87O56hZqw_7NBbA-By3qdnHEEMYRRSZJzR9goVCw@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: 1321 bytes --]

New comment by tornaria on void-packages repository

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

Comment:
The requirement for us is:
 - running `maxima` standalone binary works (of course)
 - in ecl, the following works: `(require :maxima)`

This is achieved by creating both a binary executable `maxima` and a binary module `maxima.fas`. They are both installed in `/usr/lib/maxima/5.47.0/binary-ecl/`.

This is supported by maxima just fine.
 However, the two files produced `maxima` and `maxima.fas` both contain the whole of maxima code.

Now let me explain the purpose of the `use-shared-library.patch` and the `libmaxima-ecl.so` dynamic library. By default, maxima will statically link everything so all the code is duplicated between `maxima` and `maxima.fas`. What my patch does is to place all the code in `libmaxima-ecl.so` and have `maxima` and `maxima.fas` dynamically load that one.

So now I think I have a clue of what is the trouble. It seems maxima needs to run maxima to finish building. When maxima is built for sbcl + ecl, everything is fine (maxima is run via sbcl). But when maxima is built for ecl, the dynamic library is not found. We may be able to fix that so the maxima executable actually works at build time (maybe using `LD_LIBRARY_PATH` ?).

  parent reply	other threads:[~2023-10-13 10:58 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 [this message]
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=20231013105831.gGI87O56hZqw_7NBbA-By3qdnHEEMYRRSZJzR9goVCw@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).