FS#54393 - [clingo] 5.2.0 compilation with gcc leads to opam solver error
Attached to Project:
Community Packages
Opened by David Udelson (dudelson) - Friday, 09 June 2017, 23:45 GMT
Last edited by Alexander F. Rødseth (xyproto) - Monday, 10 July 2017, 16:11 GMT
Opened by David Udelson (dudelson) - Friday, 09 June 2017, 23:45 GMT
Last edited by Alexander F. Rødseth (xyproto) - Monday, 10 July 2017, 16:11 GMT
|
Details
Description: After updating clingo to version 5.2.0-2,
invoking the opam external solver produces the following
error:
$ opam install core [WARNING] External solver failed with inconsistent return value. Request saved to "/home/vagrant/.opam/log/solver-error-712-1.cudf" [ERROR] External solver failure, please fix your installation and check /home/vagrant/.opam/config and variable $OPAMEXTERNALSOLVER. You may also retry with option --use-internal-solver While I am completely clueless as to the source of this bug, it appears to be a regression of a bug already solved in this issue on the opam bugtracker: https://github.com/ocaml/opam/issues/2203 . That is, adding the option "-DCMAKE_CXX_COMPILER=clang++" to the cmake command in the PKGBUILD resolves the issue. Additional info: - clingo 5.2.0-2 - aspcud 1.9.1-1 - opam 1.2.2-3 Steps to reproduce: 1) Using the package versions given above, attempt to install or upgrade any ocaml package using opam (e.g. `opam install core`). 
solver-error-761-1.cudf
(1.16 MiB)
|
This task depends upon
Closed by Alexander F. Rødseth (xyproto)
Monday, 10 July 2017, 16:11 GMT
Reason for closing: Implemented
Additional comments about closing: Compiling with clang++ for x86_64. i686 works neither with clang++ nor with gcc.
Monday, 10 July 2017, 16:11 GMT
Reason for closing: Implemented
Additional comments about closing: Compiling with clang++ for x86_64. i686 works neither with clang++ nor with gcc.
"opam reinstall core" worked fine here, with the same versions of clingo, aspcud and opam as you have.
Does "opam reinstall core" work for you?
~ ❯❯❯ pacman -S opam
resolving dependencies...
looking for conflicting packages...
error: unresolvable package conflicts detected
error: failed to prepare transaction (conflicting dependencies)
:: aspcud and clingo are in conflict
@dudelson, du you still get the issue above when running "opam install core", after reinstalling opam?
It has been reported on https://github.com/ocaml/opam/issues/2203#issuecomment-307526541 and https://discuss.ocaml.org/t/opam-insists-on-downgrades-because-of-ocamlfind/389/7.
Direct and stable repro is difficult because the local opam state needs to fill up with a few packages for this to manifest, the behavior is volatile, and the opam package repo is changing at a rapid pace. The linked github discussion contains at least two cudf logs that aspcud fails to solve with clingo as presently packaged, but succeeds when clingo is recompiled with clang.