Does "no luck" mean that despite you have installed the package mpfr-devel you still get the same error, or that no package with this or similar name exists? I don't have a RedHat machine at hand, so unfortunately I can't tell for sure how the package could be called else. If you fail to f...

This looks indeed dramatic. I'll try to reproduce this on the coming weekend. Sorry for the endless mess...

Oh... probably my last suggestion was not the best one. I've never tried this myself. Indeed, trying to load graph.so too early (as one of the pre-requisit shared modules for your program) can lead to all kinds of nastiness. Please try the following: remove graph.so from the linker command line and ...

... Does this mean that something with my polymake installation is wrong? No, but you are the first pioneer trying to call a function residing in an application shared module directly from an external program. The usual compiler/linker flags are not sufficient in this case. You should add the modul...

perl::Object is an appropriate receptacle for 'big' polymake objects only, not for their properties like FACES. The easiest and most straightforward way to work with a face lattice in a C++ program is to load it all at once in an object of class graph::HasseDiagram. The class is defined in applicati...

A special situation occurs if the vertices of the two polytopes in 4-space are in convex position. Then one could introduce an artificial extra facet to project a Schlegel diagram on. Actually, one could take the union of both polytopes and draw its Schlegel diagram, adding the skeleton of the inte...

There is a user-function placing_triangulation wrapping the beneath-beyond algorithm. It allows to specify any order of points. If you store the outcome as the FACETS property of a new SimplicialComplex object, you can then ask any possible questions about the triangulation, provided that applicatio...

Exactly, the shortest path algorithms were not maintained for a while. Now Julian is looking into reviving them. Hopefully he will submit the fixes soon.

The most (and only) relevant lines in the protocol are the following: socket(PF_INET, SOCK_STREAM, IPPROTO_TCP) = 5 bind(5, {sa_family=AF_INET, sin_port=htons(30000), sin_addr=inet_addr("127.0.0.1")}, 16) = -1 EACCES (Permission denied) It looks like your machine either does not have an IP...

This look really eerily. polymake usually does not try anything forbidden, it's an innocent kid. It just needs an unused port in the range 30000-65534, which is normally freely accessible for all programs, bound to the local address 127.0.0.1, where it listens for jreality or javaview data requests....