-
-
Notifications
You must be signed in to change notification settings - Fork 487
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
update M4RI to newest upstream release #11574
Comments
This comment has been minimized.
This comment has been minimized.
Dependencies: #11261 |
comment:3
I'm a little confused. The spkgs here and at #9562 are both libm4ri, and seem to be numbered backwards (the "earlier" one in the dependency is from 2011). |
comment:4
Okay, I think I figured it out. Sorry for the noise. |
comment:5
I don't know what I did wrong, but I still get the problem with the |
This comment has been minimized.
This comment has been minimized.
Author: Martin Albrecht |
comment:7
For the record, I tried spkg + patch on t2 and doctests pass. |
This comment has been minimized.
This comment has been minimized.
comment:9
applies & passes doctests with 4.7.1.rc2. |
Reviewer: Simon King |
comment:10
Why is the documentation for matrices over GF(2) not part of the reference manual? I think you should use the upgrade to expose the documentation to the audience. |
comment:11
I am not sure this documentation is much use in the reference manual since most of the interesting functions won't show up. Also, these matrices are expected to behave just as other matrices. On the other hand, there are a few - not many - special functions which are only available for GF(2). I'll take a look. |
comment:12
It seems that you agreed in a different ticket (#9562) that this class doesn't need to be in the reference manual? Hence, returning to needs review. Feel free to change it back, though. |
comment:13
I think I can live with not including it into the references. However, currently I am getting segment faults when doctesting on mark (one of the skynet machines). I try to make sure that I properly install everything from scratch again, before reporting details. |
comment:14
I did a forced new installation of the polybori spkg, then of the M4RI spkg, and I also installed the patches. I get on mark:
Of course, it could be that the problem comes from the polybori spkg. That would be unfortunate, since it is already merged. |
comment:15
Now, I tried to force re-installation of the original polybori spkg. However, that failed as well. I hope that it will not be needed to rebuild all of sage, which takes ages on mark. |
comment:16
I think the issue is that one needs to install stuff in the right order:
|
comment:17
Meanwhile I managed to revert to the original state, and can confirm that, with vanilla sage-4.7.1.rc2 on 32-bit solaris, the segfault above does not occur. I will now try to do things in the order you suggested: In fact, originally I had installed polybori, then m4ri, then the m4ri patch, and then sage -b (without touching decl.pxd). But how can the new polybori spkg be merged if apparently it depends on the new m4ri? |
comment:18
The new installation order did the trick, the segfault has gone. I am now repeating the failing doctests. |
comment:19
Or actually I am repeating sage -testall. |
comment:67
The new M4RI SPKG is at #11757 |
comment:69
Replying to @malb:
Yes, the updated patch does allow Sage to build and there are no failing tests. |
comment:70
Replying to @simon-king-jena:
I guess one could look at it this way. I'd suggest: We deal with this ticket here first and if people then still have energy and are not sick of M4RI yet we can also include #11757. |
comment:72
So, anybody up for reviewing this? Or are people waiting for attachment: trac_11574_m4ri_sse2.patch being ported to #11757? |
comment:73
Replying to @malb:
I should probably defer review to Simon since I got in through the backdoor. However, |
comment:75
Replying to @strogdon:
Sorry, I will probably not be able to review it in the next couple of days. So, iI'd appreciate if someone was quicker than I. |
comment:76
anyone? |
This comment has been minimized.
This comment has been minimized.
comment:77
The spkg builds and and installs fine. Together with the patches So, I can cordially give a positive review! |
Changed reviewer from Simon King to Simon King, Alexander Dreyer |
comment:78
attachment: m4ri_20110601.patch has no ticket number in its commit message. |
rebased to 4.7.1.alpha4 |
comment:79
Attachment: m4ri_20110601.patch.gz fixed. |
Merged: sage-4.7.2.alpha3 |
M4RI 20110601 changed the API, so we need to apply a patch as well,
cf. https://bitbucket.org/malb/m4ri/wiki/M4RI-20110601
cf. https://bitbucket.org/malb/m4ri/wiki/M4RI-20110715
Depends on #11261
Depends on #11756
CC: @strogdon @nexttime @alexanderdreyer
Component: packages: standard
Keywords: sd32
Author: Martin Albrecht
Reviewer: Simon King, Alexander Dreyer
Merged: sage-4.7.2.alpha3
Issue created by migration from https://trac.sagemath.org/ticket/11574
The text was updated successfully, but these errors were encountered: