-
-
Notifications
You must be signed in to change notification settings - Fork 517
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
experimental package macaulay2-1.1-r7221.p0.spkg fails to install #11710
Comments
comment:1
Attaching But as you mentioned, the package is fairly old anyway, which doesn't necessarily mean a newer version will install seamlessly. Did you already try that? |
comment:2
Yes, I tried installing a newer version. It did not go well, and |
This comment has been minimized.
This comment has been minimized.
Changed keywords from none to sd32 |
comment:5
For the record: Macaulay2 1.5 is about to be released. |
comment:6
To review #12335 I need to install the spkg
It's mentioned in the error message that one can try:
but going to a sage shell and into the spkg src and running this command fails:
|
comment:7
Replying to @benjaminfjones:
Is autoconf installed on your system? If not, does Sage include its own autoconf? These may be dumb questions, but I can get past the autoconf, maybe because it's on my system. It breaks for me elsewhere. |
comment:8
I am trying to build M2 1.4 from source - it would be way better to upgrade spkg. My diary:
|
comment:9
I am not sure where fat source is, but I have downloaded files one by one until there were no complaints from here:
As I understand some of these should be substituted by Sage versions. From a license point of view, would it be OK to make an optional spkg with the rest included? |
comment:10
The end of make's output:
|
comment:11
I made a new spkg based on Macaulay2-1.4, so far it fails to build because of 4ti2 and gfan. Both are installed in Sage (4ti2 as optional), but not detected by M2 - I've asked M2 developers what can be done. Including these into M2 package breaks during gfan installation, so I have no idea yet how close I am to a working package. |
Changed keywords from sd32 to sd32, sd40.5 |
comment:12
Here is an spkg that tries to build (building 4ti2 and gfan is prohibited): http://sage.math.washington.edu/home/novoselt/macaulay2-1.4-r12617.spkg It crashes with implicit-function-declaration after several minutes into the build. I am also experimenting with the trunk version of version 1.5, but so far I had to enable downloading extra files, these extra files are huge (27Mb for normaliz), and the build is taking forever (although it is likely to succeed - it seems to process documentation now). |
comment:13
The trunk version has succeeded, although my system now has autoconf, lib(n)curses and libxml2. |
comment:14
Replying to @novoselt:
Is it possible and/or advisable to test? I'm interested in trying this out. |
comment:15
Sure, here is a link: http://sage.math.washington.edu/home/novoselt/macaulay2-1.5.spkg Let me know if it complains about bison and flex during build - the install script does not check for them yet. |
comment:16
Replying to @novoselt:
I had complaints about libxml2 and yacc. I installed bison for yacc. Right now it's still building, but I'm guessing (fingers crossed) that I have everything I need. I may leave before it quits, and it may be Thursday before I'm back in the office, but I will let you know how it turns out. |
comment:17
I think there is an option to build without xml, but I didn't try it yet. In any case since I was not able to build 1.4 due to errors during compilation of M2 itself, I'd like to wait till 1.5 is officially released, hopefully with proper packages for Normaliz etc. Then we can see how to cut down on dependencies. |
comment:18
I encountered a complaint about flex, too. Trying another rebuild... |
comment:19
Interesting - so this complain was late in the build process, M2 didn't detect its absence? I've updated 1.5 spkg to have checks for gdbm, 4ti2, bison, and flex spkgs. The rest of dependencies has to be dropped somehow. |
Author: Andrey Novoseltsev |
comment:20
As far as I know, M2 didn't detect its absence, no. It does detect some other things. Apparently, the build finished, but I don't see any variant of "Macaulay2" in the list of optional_packages, either in the installed section, or the uninstalled section. (i.e., when I call If I knew how to test it out, I'd give you some more useful information. (For example, whether it crashes while using it.) I'm turning back to #12802 for a little bit, and I have some other things to do, so I'll look at it later. BTW, what would constitute grounds for a positive review? Not just the installation, presumably, but a fairly careful amount of checking that it works, right? |
Reviewer: John Perry |
comment:21
You can try to run "sage -M2" to get M2 prompt and see if it works (worked for me showing version 1.4.0.1). Also I see it in "sage -i" - the list of installed packages. Maybe to see it in optional ones it has to be registered somehow. For a positive review you need to check that it follows guidelines here: Note also that if you just want to use M2 with Sage, you can install M2 on its own and if it is in your PATH, Sage interface should work. At least I made it work reliably with version 1.3.1 a couple years ago: #7897. |
comment:22
Replying to @novoselt:
Okay, yes, I see it there.
Good point about not being ready for review. :-) For future reference, it's nice to have the link. But, I would also like to try it out with more than the M2 command line; I have seen from my work in
I might like to use M2 with sage, and I have a version installed, as I had thought of looking into this myself at one point. Thanks for the tip. |
comment:23
One automatic thing to try is (in Sage root)
Which shows that things still work quite well - only the last test is not quite clear without looking at the code (and there are 144 failures without M2 available, so there are quite a few tests in that module). If you have a separate M2 installed, be careful during review tests - if you don't have a working installation inside of Sage the system-wide will be used silently and without any difference. So it may seem that spkg is working when it does not. On an unrelated note, it is peculiar how 1 was not in |
Dependencies: #13234 |
comment:25
Replying to @novoselt: |
comment:31
(Not sure what Authors and Reviewers means here, as there doesn't seem to be any code / patch / branch.) "The current stable version is 1.9.2, released August, 2016." https://github.com/Macaulay2/M2/releases/tag/version-1.9.2 |
comment:33
I think this can be closed as won't fix. M2 needs many patched, for Boehm GC compatibility, packages (e.g. Flint, NTL) , and it's very bulky this way. |
comment:35
I agree, and furthermore it is not even listed under the experimental packages anymore. |
sage-4.7.1 on the Skynet machine eno (x86_64-Linux-core2-fc) fails to install the experimental package macaulay2-1.1-r7221.p0.spkg.
(Note that installing optional package gdbm-1.8.3.spkg is a prerequiste for installing
macaulay2-1.1-r7221.p0.spkg
.)Rather than fix this problem, it may be better to upgrade to
a more recent version of Macaulay2, such as macaulay2-1.4-r12617.
...stuff deleted...
Depends on #13234
Component: packages: experimental
Keywords: sd32, sd40.5
Author: Andrey Novoseltsev
Reviewer: John Perry
Issue created by migration from https://trac.sagemath.org/ticket/11710
The text was updated successfully, but these errors were encountered: