From: "Christoph Höger" <christoph.hoeger@tu-berlin.de>
To: caml users <caml-list@inria.fr>
Subject: [Caml-list] opttoploop.ml
Date: Fri, 07 Nov 2014 16:09:40 +0100 [thread overview]
Message-ID: <545CE0B4.6020409@tu-berlin.de> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Dear Ocaml-users (and developers),
is the compiled toploop still supported? It does not compile in the
recent ocaml tarball:
choeger@daishi ~/uebb/ocaml.4.02.1/ocaml-4.02.1 % make ocamlnat
boot/ocamlrun ./ocamlopt -nostdlib -I stdlib -I otherlibs/dynlink
- -strict-sequence -w +33..39+48 -warn-error A -bin-annot -safe-string
- -I utils -I parsing -I typing -I bytecomp -I asmcomp -I driver -I
toplevel -c toplevel/genprintval.ml
boot/ocamlrun boot/ocamlc -nostdlib -I boot -strict-sequence -w
+33..39+48 -warn-error A -bin-annot -safe-string -I utils -I parsing
- -I typing -I bytecomp -I asmcomp -I driver -I toplevel -c
toplevel/opttoploop.mli
boot/ocamlrun ./ocamlopt -nostdlib -I stdlib -I otherlibs/dynlink
- -strict-sequence -w +33..39+48 -warn-error A -bin-annot -safe-string
- -I utils -I parsing -I typing -I bytecomp -I asmcomp -I driver -I
toplevel -c toplevel/opttoploop.ml
File "toplevel/opttoploop.ml", line 86, characters 39-47:
Error: Signature mismatch:
...
Values do not match:
val eval_path : Path.t -> Obj.t
is not included in
val eval_path : Env.t -> Path.t -> valu
File "toplevel/opttoploop.ml", line 82, characters 6-15:
Actual declaration
make: *** [toplevel/opttoploop.cmx] Fehler 2
- --
Christoph Höger
Technische Universität Berlin
Fakultät IV - Elektrotechnik und Informatik
Übersetzerbau und Programmiersprachen
Sekr. TEL12-2, Ernst-Reuter-Platz 7, 10587 Berlin
Tel.: +49 (30) 314-24890
E-Mail: christoph.hoeger@tu-berlin.de
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iEYEARECAAYFAlRc4LQACgkQhMBO4cVSGS/fSwCaAn2Og/MAQEDwCWyru7uRMI6d
wZIAoLCfPdA2IgIkq3jPRjU05ZBP4KMq
=aI5/
-----END PGP SIGNATURE-----
reply other threads:[~2014-11-07 15:09 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=545CE0B4.6020409@tu-berlin.de \
--to=christoph.hoeger@tu-berlin.de \
--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