From: "Rémi Dewitte" <remi@gide.net>
To: caml-list@inria.fr
Subject: [Caml-list] bin_prot
Date: Tue, 11 Jan 2011 10:59:51 +0100 [thread overview]
Message-ID: <AANLkTinxRApWoSVgbVB4SgdO+BCY7c2VUC7tKtDgigO0@mail.gmail.com> (raw)
Hello,
I am struggling to native compile with bin_prot 1.3.0 because it fails
at link stage :
gcc: lib/libbin_prot.a: No such file or directory
File "caml_startup", line 1, characters 0-1:
Byte compilation works fine.
I have investigated a bit :
- At the end of my /usr/local/lib/ocaml/3.11.2/bin_prot/bin_prot.cmxa,
I can see MG@ 1lib/libbin_prot.a *-lbin_prot@@
- bin-prot source files are in a lib/ directory when building bin-prot
I use the :
- ocaml and ocamlbuild 3.11.2
- gcc 4.4.3
- ocamfind 1.2.5
Do you have any idea ?
To test, create a simple ml :
type a = A | B of int
with bin_io
My _tags contains :
<*> : syntax_camlp4o,pkg_bin_prot.syntax
Use a generic myocamlbuild.ml from
http://brion.inria.fr/gallium/index.php/Using_ocamlfind_with_ocamlbuild#Generic_plugin
Then:
ocamlbuild truc.native
Many thanks,
Rémi
reply other threads:[~2011-01-11 10:00 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=AANLkTinxRApWoSVgbVB4SgdO+BCY7c2VUC7tKtDgigO0@mail.gmail.com \
--to=remi@gide.net \
--cc=caml-list@inria.fr \
--cc=remi.dewitte@gide.net \
/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