From: Erick Tryzelaar <erickt@dslextreme.com>
To: Ashish Agarwal <agarwal1975@gmail.com>
Cc: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] error building native code with ocamlbuild
Date: Mon, 03 Dec 2007 21:00:37 -0800 [thread overview]
Message-ID: <4754DEF5.20403@dslextreme.com> (raw)
In-Reply-To: <d8be5ae20712031256i214a3dccu1bbcdd641360f7f@mail.gmail.com>
Ashish Agarwal wrote:
> Using ocamlbuild on the following example to build native code
> includes a library twice, causing an error, but byte-code works fine.
> Am I doing something wrong or is it a bug? Thanks for any help.
It looks like you're getting the unix library added twice, which
ocamlopt doesn't like. In your case, I don't think you even need the
myocamlbuild.ml file. ocamlbuild already has the unix library set up for
it, so the _tags file should be enough for you.
next prev parent reply other threads:[~2007-12-04 5:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-03 20:56 Ashish Agarwal
2007-12-04 5:00 ` Erick Tryzelaar [this message]
2007-12-04 15:31 ` [Caml-list] " Ashish Agarwal
2007-12-05 2:19 ` Erick Tryzelaar
2007-12-06 17:28 ` Nicolas Pouillard
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=4754DEF5.20403@dslextreme.com \
--to=erickt@dslextreme.com \
--cc=agarwal1975@gmail.com \
--cc=caml-list@yquem.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