From: Mohamed Iguernlala <iguer.auto@gmail.com>
To: "caml-list@inria.fr" <caml-list@inria.fr>
Subject: [Caml-list] Loading of dynamic code works with older OCaml versions, but fails with recent versions (>= 4.02.0)
Date: Mon, 31 Jul 2017 18:37:57 +0200 [thread overview]
Message-ID: <05deee1e-ef15-daa7-80df-16e214bb9ea3@gmail.com> (raw)
Hello,
I'm facing an issue[1] with OCaml versions >= 4.02.0 when
building/using dynamically loaded plugins for/with Alt-Ergo. I
think this is probably due to module aliases. In fact, I'm able
to install and use Alt-Ergo + satML-plugin on OCaml 4.01.0, but
not on OCaml 4.02.0 (or higher).
$ opam sw 4.01.0
$ eval `opam config env`
$ opam remove alt-ergo satML-plugin
$ opam install alt-ergo satML-plugin
$ echo "goal g: 1 + 1 = 2" > foo.why
$ alt-ergo -sat-plugin satML-plugin.cmxs foo.why
File "foo.why", line 1, characters 9-18:Valid (0.0000) (0 steps)
$ opam sw 4.02.0
$ eval `opam config env`
$ opam remove alt-ergo satML-plugin
$ opam install alt-ergo satML-plugin
$ echo "goal g: 1 + 1 = 2" > foo.why
$ alt-ergo -sat-plugin satML-plugin.cmxs foo.why
...
>> Failure message: implementation mismatch on Options
Is this a known issue (or is it an issue) ? I know that if I
build the binary and the plugin from the same compiled files,
things work well. I was wondering if there is a better solution
that allows to build things separately.
Regards,
Mohamed.
[1] https://github.com/OCamlPro/alt-ergo/issues/22
--
Mohamed IGUERNLALA
Senior R&D Engineer, OCamlPro SAS
Research Associate, VALS team, LRI
Webpage: http://www.iguer.xyz
LinkedIn: https://fr.linkedin.com/in/mohamed-iguernlala-71515979
next reply other threads:[~2017-07-31 16:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-31 16:37 Mohamed Iguernlala [this message]
2017-08-01 9:15 ` François Bobot
2017-08-01 9:58 ` Fabrice Le Fessant
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=05deee1e-ef15-daa7-80df-16e214bb9ea3@gmail.com \
--to=iguer.auto@gmail.com \
--cc=caml-list@inria.fr \
/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