Skip to content
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

Getting PolymakeInterface to work #17

Open
olexandr-konovalov opened this issue Jun 4, 2018 · 5 comments
Open

Getting PolymakeInterface to work #17

olexandr-konovalov opened this issue Jun 4, 2018 · 5 comments

Comments

@olexandr-konovalov
Copy link
Member

polymakeinterface package is not loadable now:

gap> Filtered(RecNames(GAPInfo.PackagesInfo),n->LoadPackage(n)=fail);
[ "polymakeinterface", "itc", "linboxing", "xgap" ]
gap> 
@olexandr-konovalov
Copy link
Member Author

What do we need for that @sebasguts ? Having it runnable would be indeed a useful addition to the Docker container.

@olexandr-konovalov
Copy link
Member Author

First off, we install polymake in this container.

This is supposedly enough to make polymaking package working, and @fingolfin points that https://github.com/gap-packages/polymaking now has runnable tests in https://travis-ci.org/gap-packages/polymaking. However, I still see errors when I run tests from polymaking 0.8.2, see e.g. https://travis-ci.org/gap-infra/gap-docker-pkg-tests-master-staging/jobs/497837386. Could that be because polymaking tests on travis use a fresh install of polymake, and we here use already installed one, made for https://hub.docker.com/r/gapsystem/gap-docker-base/ 5 months ago?

Second, I have added to https://github.com/gap-system/gap-docker-master packages libpolymake-dev and libxml2, so now PolymakeInterface compiles there. However, the package now segfaults while loading, see e.g. https://travis-ci.org/gap-infra/gap-docker-pkg-tests-master-staging/jobs/497851996 with

terminate called after throwing an instance of 'std::runtime_error'
  what():  polymake::Main - weird callable library path /usr/lib/libpolymake.so.3.2

so I will now revert those commits to undo these changes.

olexandr-konovalov pushed a commit to gap-system/gap-docker-master that referenced this issue Feb 24, 2019
Doing that causes runtime error while loading PolymakeInterface:

terminate called after throwing an instance of 'std::runtime_error'
  what():  polymake::Main - weird callable library path /usr/lib/libpolymake.so.3.2

See gap-system/gap-docker#17
@mohamed-barakat
Copy link
Member

@sebasguts Shall we close this issue? This also means that we should delete PolymakeInterface from homalg_project. Any thoughts?

@olexandr-konovalov
Copy link
Member Author

@mohamed-barakat what do you mean by closing this issue - giving up on loading PolymakeInterface in the GAP Docker container? But why? I don't know what the problem was, and it may be that it healed by itself over a year - we may try again with most recent versions to check that first...

@zickgraf
Copy link
Contributor

I think PolymakeInterface and Convex are supposed to be replaced by NConvex and CddInterface. That's why probably PolymakeInterface will not be fixed for recent versions of polymake (I think it compiles with Polymake 3.4 but does not run) and will be dropped sooner or later.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants