unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Julien Lepiller <julien@lepiller.eu>
To: help-guix@gnu.org,divoplade <d@divoplade.fr>
Subject: Re: OCaml: incompatible ppx drivers (ppxlib and ocaml-migrate-parsetree)
Date: Wed, 30 Dec 2020 13:28:39 -0500	[thread overview]
Message-ID: <64694B22-34EE-4EB0-9736-13D3E171B0DF@lepiller.eu> (raw)
In-Reply-To: <9fba565a28399f9db338b1ccab6777d8a66a98ce.camel@divoplade.fr>

Looking at the opam repo, ppxlib 0.20.0 requires ocaml-parse-tree >= 2.1.0, which is the latest. You have version 1.8.0.

Le 30 décembre 2020 11:55:11 GMT-05:00, divoplade <d@divoplade.fr> a écrit :
>Dear guix,
>
>I am trying to build js-of-ocaml. I have created an updated version of
>ocaml-compiler-libs, ocaml-migrate-parsetree and ocaml-ppxlib, and
>tried to build the latest js_of_ocaml with that, but I get the
>following error when building the updated ppxlib:
>
>starting phase `build'
>File "_build/default/.ppx/0224ad3443a846e54f1637fccb074e7d/ppx.exe",
>line 1, characters 0-0:
>Error: Failed to create on-demand ppx rewriter for ppxlib.metaquot; too
>many
>incompatible ppx drivers were found: ppxlib and ocaml-migrate-
>parsetree.
>File "_build/default/.ppx/3134a5298fb2c80808cc94dd434856cb/ppx.exe",
>line 1, characters 0-0:
>Error: Failed to create on-demand ppx rewriter for ppxlib.traverse; too
>many
>incompatible ppx drivers were found: ppxlib and ocaml-migrate-
>parsetree.
>File "traverse/dune", line 7, characters 13-48:
>7 |  (preprocess (pps ppxlib_metaquot ppxlib.runner)))
>                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>Error: Too many incompatible ppx drivers were found: ppxlib and
>ocaml-migrate-parsetree.
>File "ast/ast_helper_lite.mli", line 18, characters 0-17:
>18 | open Ocaml_common
>     ^^^^^^^^^^^^^^^^^
>Error (warning 33): unused open Ocaml_common.
>command "dune" "build" "@install" failed with status 1
>builder for `/gnu/store/k7wfvxqbp07f8idjsbzi699v5y163j24-ocaml-ppxlib-
>0.20.0.drv' failed with exit code 1
>
>Why are these two packages "incompatible"? Do you understand what is
>happening?

  reply	other threads:[~2020-12-30 18:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-30 16:55 OCaml: incompatible ppx drivers (ppxlib and ocaml-migrate-parsetree) divoplade
2020-12-30 18:28 ` Julien Lepiller [this message]
2020-12-30 19:30   ` divoplade

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=64694B22-34EE-4EB0-9736-13D3E171B0DF@lepiller.eu \
    --to=julien@lepiller.eu \
    --cc=d@divoplade.fr \
    --cc=help-guix@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).