-
-
Notifications
You must be signed in to change notification settings - Fork 482
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 PolyBoRi to release 0.8.0 #11575
Comments
This comment has been minimized.
This comment has been minimized.
comment:2
For the record I have a gentoo ebuild that pulls the trunk of hg on bitbucket. That's how I tested things in the issues I have filled for polybori recently. |
This comment has been minimized.
This comment has been minimized.
comment:3
I prepared a first at http://boxen.math.washington.edu/home/dreyer/spkg/polybori-0.8-alpha.p0.spkg It builds, but of course |
comment:4
Build using my ebuild (you didn't commit anything since you tagged 0.8-alpha so that's what I should have pulled). Used boost-1.42 and m4ri-20100817. Builds and install fine without warnings. Is there a working test suite that can be run? Also I didn't build any docs. |
comment:5
Hi Francois! I gave to access to polybori-testsuite. If you do use it via the cython interface from Sage's Library (not the original PyPolyBoRi,so). I need to update this, but it's not that easy, because I have to c++-ify some classes without defautl constructor. |
comment:6
Hi Alexander, thanks for giving me access. I think it is best to test it separate from sage at first, especially when you consider that installing it will break sage. I hope that it can work that way. |
comment:7
I just had a thought. I should really try this against m4ri-20110715 (#11574). I suppose this version of polybori is ready for it. |
comment:9
Replying to @alexanderdreyer:
I'll have to wait until the sage server are fully back on, m4ri tarball seem to be stored there. That or I clone m4ri tip from bitbucket, which may be an idea since I already to that for polybori. |
comment:10
Pulled m4ri tip. Polybori-0.7.1 compiles against it, no problem. I'll check 0.8.alpha a bit later and then I'll see about that test suite. |
Attachment: polybori-0.8.0alpha.p1.patch.gz First working patch for supporting PolyBoRi 0.8 by the Sage-lib |
This comment has been minimized.
This comment has been minimized.
comment:11
Here's now the first patch for making the Sage-lib supporting PolyBoRi 0.8: I needs to workaround missing default generators of PolyBoRi-functions by reintroducing then (just for now: It should be using the cppclass construct) . Therefore, we do need another patched spkg: http://boxen.math.washington.edu/home/dreyer/spkg/polybori-0.8-alpha.p1.spkg |
This comment has been minimized.
This comment has been minimized.
comment:13
I have done a build of your latest tip from a couple of days ago and it was fine. I still have to get organized to do the testing. Nice to have a patch for sage but I am afraid it will need to be rebased now that #11377 is in. Please do not use SAGE_ROOT in module_list.py. In your case SAGE_INC will be enough. |
comment:14
Replying to @kiwifb:
No problem, it's still work to do anyway, since the c++-ification not really done yet. (I just mis-clicked, it should read "NEEDS_WORKS".) PS: So that crash-issue on gentoo-prefix got away with 0.8-alpha? |
comment:15
Replying to @alexanderdreyer:
Don't know yet. I have to build this on OS X and apply the patch. It may very well not happen until Monday local time (it's Saturday morning here) since this is one of my work machine. |
comment:16
Here, too (1:00). In case this still fails: Can you give the plain PolyBoRi source from bitbucket a try? I had to patch the recent spkg to work around some cython vs. c++ issue. |
comment:18
Replying to @alexanderdreyer:
Not quite lunch time here. I'll make a note to try both. The nature of sage-on-gentoo is that the plain sources will be used over spkg unless the spkg is the only thing that exists or works. We still patch stuff if it is not too big (OK sometimes even when it is big). |
comment:19
Pulled the latest mercurial tip. Installed fine on linux. OS X (10.5.8 on x86) didn't like it one bit. I compiled with -ggdb which may have an impact.
That's the critical bit where it fails. I'll compare with what happens on linux shortly. Francois who is a bit snowed in today (some more falling). |
comment:20
@kiwifb Please pull again. There was indeed an outdated directory name given, which was ignored on Linux. |
comment:138
Something seems to have gone wrong with the rebased patch: I
This gave me a few hunks and one conflict in PolynomialConstruct which I fixed. While it now compiles I get these failures:
So something went wrong and Alexander's element_constructor fixes didn't make it into this patch? |
Changed work issues from cython-0.15.1 to none |
comment:139
Replying to @malb:
Did you apply the dependency #9138? |
comment:140
Ha, no! Sorry for the noise then. |
comment:141
Works as advertised, but I didn't try it with the new Cython yet. |
comment:142
Works with Sage 4.8.alpha1. |
comment:143
Could you re-export the patch with a username added? Maybe you need to create a |
comment:144
Thank for pointing this out. I wasn't aware, that |
This comment has been minimized.
This comment has been minimized.
Rebased to latest #9138 |
comment:148
Attachment: polybori-0.8.0.p1.2.patch.gz |
Merged: sage-5.0.beta1 |
PolyBoRi 0.8 will come with some changes in the interface (in particular the infamous global settings will be removed)
So there was an extensive alpha phase this time:
https://sourceforge.net/projects/polybori/files/polybori/0.8.alphas/
The final release is here:
https://sourceforge.net/projects/polybori/files/polybori/0.8.0/
Current patches/spkg
Depends on #11574
Depends on #9138
Upstream: None of the above - read trac for reasoning.
CC: @alexanderdreyer @sagetrac-PolyBoRi @kiwifb @burcin @malb @simon-king-jena @jdemeyer
Component: packages: standard
Author: Alexander Dreyer
Reviewer: Martin Albrecht
Merged: sage-5.0.beta1
Issue created by migration from https://trac.sagemath.org/ticket/11575
The text was updated successfully, but these errors were encountered: