Opened 14 years ago
Closed 6 years ago
#297 closed enhancement (duplicate)
Upgrade polymake and/or make it an optional spkg
Reported by: | was | Owned by: | mabshoff |
---|---|---|---|
Priority: | minor | Milestone: | sage-duplicate/invalid/wontfix |
Component: | combinatorics | Keywords: | |
Cc: | sage-combinat, jpflori | Merged in: | |
Authors: | Reviewers: | Karl-Dieter Crisman | |
Report Upstream: | N/A | Work issues: | |
Branch: | Commit: | ||
Dependencies: | Stopgaps: |
Description
It seems much has changed since polymake v 2.2, so this might be difficult. Also, they have interactive scripts, which one has to deal with. Yuck.
I did try just building from scratch and it seemed to work without any funny business with GMP, etc.
If you work on this, email wstein@…
Change History (13)
comment:1 Changed 14 years ago by
- Milestone set to sage-2.9
- Owner changed from was to mabshoff
- Status changed from new to assigned
comment:2 in reply to: ↑ description Changed 14 years ago by
comment:3 Changed 12 years ago by
- Cc sage-combinat added
comment:4 Changed 10 years ago by
- Report Upstream set to N/A
I created packages for a prerelease version of polymake before this workshop:
http://polymake.org/doku.php/workshop0311
The package and its dependencies are here:
http://sage.math.washington.edu/home/burcin/polymake/
These packages were just for convenience. They are not ready for review. :)
I also started writing a python wrapper to libPolymake. It's not useful for anything yet, but I could make it useful and release it if there is interest.
comment:5 Changed 8 years ago by
- Cc jpflori added
- Summary changed from polymake -- create a build package for the optional SAGE package polymake-2.3 to Upgrade polymake and/or make it an optional spkg
There has definitely been interest in this from various people I've spoken to over the years. Also, it would be good to have it be an optional spkg for this. Note the current version is now 2.12 (Burcin's was 2.9).
comment:6 Changed 8 years ago by
- Milestone changed from sage-5.11 to sage-5.12
comment:7 Changed 7 years ago by
- Milestone changed from sage-6.1 to sage-6.2
comment:8 Changed 7 years ago by
- Milestone changed from sage-6.2 to sage-6.3
comment:9 Changed 7 years ago by
- Milestone changed from sage-6.3 to sage-6.4
comment:10 Changed 6 years ago by
- Milestone changed from sage-6.4 to sage-duplicate/invalid/wontfix
- Reviewers set to Karl-Dieter Crisman
comment:11 Changed 6 years ago by
- Status changed from new to needs_review
comment:12 Changed 6 years ago by
- Status changed from needs_review to positive_review
comment:13 Changed 6 years ago by
- Resolution set to duplicate
- Status changed from positive_review to closed
Replying to was:
Ok, I did some investigation. We need to modify support/configure.pl:
Around line 273:
Instead of answer_path($InstallTop?) we just should assign $InstallTop?=getenv($SAGE_LOCAL) (or something alike, my perl is slightly rusty).
We also need to add Sage's gmp to $Libs around line 614 somewhere.
Cheers,
Michael