-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
maxima fails to (natively) build using ecl #46293
Comments
Downgrading to 5.46.0 fixes the issue. |
@tornaria is downgrading an option? will it interfere with sage? |
|
Not sure I understand what you mean. The default for 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:
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). |
Let me clarify: the error was in does this make sense? |
Hi, I'm a Maxima developer and I'm working on the upstream bug report. @tornaria you mentioned matrixexp.patch; where can I find that patch? I will take a look at merging it into Maxima. |
Thanks for helping. The patches are here: https://github.com/void-linux/void-packages/tree/master/srcpkgs/maxima/patches |
Might the problem be that we use the (potentially cross-built) Maxima during the build process, possibly not telling it where to find it's libraries? |
@dkwo Thanks for linking the patches, I will take a look at them. About libmaxima-ecl.so, I seem to recall now that it's part of the Maxima installation for Sage. Is the Maxima build machinery that you are working with somehow derived from the stuff for Sage? If so, I guess my advice is to start over with a vanilla installation. Is interoperability with Sage a requirement for a Maxima-only installation? I don't know what the requirements for Void Linux are, you can tell me. |
Are you cross-compiling for the arm platform? |
@gunterkoenigsmann I'm building @robert-dodier I'm building just maxima here, not as part of sage. it's downloaded from ${SOURCEFORGE_SITE}/maxima/maxima-${version}.tar.gz and built using the gnu-configure build-style in https://github.com/void-linux/void-packages/blob/master/srcpkgs/maxima/template (the only modification are the patches I linked before, as well as the
which I'm not sure is relevant here. Let me emphasize that the failure only happens with maxima 5.47 (while 5.46 builds fine) and only when building with ecl (if using sbcl, it builds fine). |
the gnu-configure build style runs standard
|
Removing all the patches and the post_configure phase still fails. |
let me attach the config.log |
Thanks for the info. Sorry for the trouble, but can you post the content of |
By the way, FWIW, I just built current Maxima from Git with ECL 23.9.9 on an Ubuntu 16.04 system.
I am more than a little puzzled by the presence of |
No worries. Here 's my src/autoconf-variables.lisp:
Do you think it makes sense to also upstream this patch? https://github.com/void-linux/void-packages/blob/master/srcpkgs/maxima/patches/handle-multiple-ldflags.patch Actually, could this patch be creating troubles? https://github.com/void-linux/void-packages/blob/master/srcpkgs/maxima/patches/use-shared-library.patch |
Yes, after removing the
@tornaria can you comment? |
removing that patch, as well as
passes checks with |
The requirement for us is:
This is achieved by creating both a binary executable This is supported by maxima just fine. Now let me explain the purpose of the 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 |
@robert-dodier Thanks for helping with this, and sorry for bothering you. |
@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 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:
Also a comment about documentation. The tarball includes all the documentation so it is not necessary to rebuild. However:
|
If you were willing to file them at https://sourceforge.net/p/maxima/patches/ it would make them more visible for the Maxima developers |
Is this a new report?
Yes
System Info
6.5 series kernel on apple silicon (aarch64), as well as
Void 6.5.5_2 x86_64 GenuineIntel uptodate rrFFFFFFFFFFFFFF
Package(s) Affected
maxima-5.47.0
Does a report exist for this bug with the project's home (upstream) and/or another distro?
https://sourceforge.net/p/maxima/bugs/4188/
but this is possibly due to our own https://github.com/void-linux/void-packages/blob/master/srcpkgs/maxima/patches/use-shared-library.patch
Expected behaviour
The prior version 5.46.0 builds fine.
Actual behaviour
In the
do_build
phase:Steps to reproduce
build natively on any of those archs using
./xbps-src pkg -o ecl,~sbcl maxima
The text was updated successfully, but these errors were encountered: