From: tornaria <tornaria@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: maxima: fix build with -o ~sbcl
Date: Mon, 16 Oct 2023 21:38:17 +0200 [thread overview]
Message-ID: <20231016193817.VsfROJmInP2yLsSdKo0EsGiphGc4_aGOR1rFZwRWzK4@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-46709@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1192 bytes --]
New comment by tornaria on void-packages repository
https://github.com/void-linux/void-packages/pull/46709#issuecomment-1765153271
Comment:
> if I also remove the patch, then it builds fine
>
> ```
> => maxima-ecl-5.47.0_3: running pkg_install ...
> => ERROR: maxima-ecl-5.47.0_3: vinstall: cannot find 'src/binary-ecl/libmaxima-ecl.so'...
> => ERROR: maxima-ecl-5.47.0_3: pkg_install: 'return 1' exited with 1
> => ERROR: in _noglob_helper() at common/environment/setup/install.sh:12
> => ERROR: in pkg_install() at srcpkgs/maxima-ecl/template:134
> ```
>
> I'll try again later.
I'm not sure ecl will cross build. It's no good if the binary that you build is x86_64 instead of aarch64. The strip hook just happens to barf at `libmaxima-ecl.so` and not at `maxima`; that doesn't mean the `maxima` binary will work.
Just use `file` to see whether the binaries have been built for aarch64 or not. You can try that with `maxima`, `maxima.fas` and `libmaxima-ecl.so` after running `do_build()`, it doesn't matter if the `do_install()` step succeeds or not, the files are there. If they are good, we can figure out a way to fix the install, if they are not good, then no.
next prev parent reply other threads:[~2023-10-16 19:38 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-16 2:56 [PR PATCH] " tornaria
2023-10-16 14:32 ` [PR PATCH] [Updated] " tornaria
2023-10-16 14:33 ` tornaria
2023-10-16 18:01 ` dkwo
2023-10-16 18:01 ` dkwo
2023-10-16 18:05 ` tornaria
2023-10-16 18:29 ` dkwo
2023-10-16 18:57 ` dkwo
2023-10-16 19:38 ` tornaria [this message]
2023-10-16 22:01 ` dkwo
2023-10-16 22:17 ` tornaria
2023-10-17 15:16 ` dkwo
2023-10-17 15:17 ` dkwo
2023-10-17 15:18 ` dkwo
2023-10-17 15:59 ` [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=20231016193817.VsfROJmInP2yLsSdKo0EsGiphGc4_aGOR1rFZwRWzK4@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).