minizinc and all mzn-* command crash

[PierfrancescoArdino]

I'm using the minizinc-ide from the aur repositoty on arch linux and everytime I try to use minizinc it gives me a seg fault, even when i run only minizinc command without any params.

Basically this is the standard error that I got each time
*** Mercury runtime: caught segmentation violation *** cause: address not mapped to object address involved: 0xffffffffff600000 This may have been caused by a stack overflow, due to unbounded recursion. exiting from signal handler Segmentation fault (core dumped)

[Dekker1]

Hi @PierfrancescoArdino,

This is a known issue for newer versions of linux (#202). The minizinc command in 2.1.7 package is a old mercury binary that we patched every release; however we did not maintain it. On the development branch and in the next release a new version of minizinc is included that will replace this old binary.

The MiniZinc package in the arch linux repository is, to my knowledge, not maintained by anyone in the MiniZinc team, but will hopefully be updated soon after the next release.

[PierfrancescoArdino]

So, if I compile minizinc from the develop branch I will solve the problem?

[Dekker1]

Yes, that will give you a working version of the minizinc binary. Do note that the driver is quite different and is intended to be used using solver configurations.

[PierfrancescoArdino]

Ok, what do you mean with solver configurations? I've have to download and link by myself the solvers? How can I do that and where I can find new solver? For example the g12mip

[Dekker1]

If you are unfamiliar with compiling MiniZinc you might be better off waiting for the release.

• Solver configurations are files that tell the compiler how a solver works, what options it supports and what library to use.
• See the MIP readme's regarding the linking with other solvers.
• g12mip could still be used by keeping the flatzinc executable from the last release