caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Gabriel Scherer <gabriel.scherer@gmail.com>
To: rixed@happyleptic.org
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Compiler can't find a stub anymore
Date: Mon, 22 Oct 2012 10:49:14 +0200	[thread overview]
Message-ID: <CAPFanBGzwUOx=ofxkjpB3kEp5M0xZEPG=1f16yJuwe+BrkypWA@mail.gmail.com> (raw)
In-Reply-To: <20121022070357.GA3222@ombreroze.happyleptic.org>

ocamlbuild's `-documentation` option is useful for these kind of things.

$ ocamlbuild -documentation | grep custom
flag {. byte, custom, library, link, ocaml .} "-custom"
flag {. byte, custom, link, ocaml, program .} "-custom"

On Mon, Oct 22, 2012 at 9:03 AM,  <rixed@happyleptic.org> wrote:
> Answering my own question for my old days:
> the problem was that parmap library was not compiled with -custom
> while it's META file does not set any linkopts. I fixed it using
> -custom since I find it easier, but I wonder what's the prefered
> way to add these link flags between custom or linkopts?
>
> BTW, I couldn't find where to add -custom in ocamlbuild. Hopefully
> parmap wraps ocamlbuild into Makefile so I could work around it. Any doc
> on how to add -custom flag?  I tried with -lflag but for some reason the
> flag was also added to ocamlopt invocations.
>
> Anyway, much ado about nothing as usual.
>
> --
> Caml-list mailing list.  Subscription management and archives:
> https://sympa.inria.fr/sympa/arc/caml-list
> Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
> Bug reports: http://caml.inria.fr/bin/caml-bugs

      reply	other threads:[~2012-10-22  8:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-15 12:21 rixed
2012-10-22  7:03 ` rixed
2012-10-22  8:49   ` Gabriel Scherer [this message]

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='CAPFanBGzwUOx=ofxkjpB3kEp5M0xZEPG=1f16yJuwe+BrkypWA@mail.gmail.com' \
    --to=gabriel.scherer@gmail.com \
    --cc=caml-list@inria.fr \
    --cc=rixed@happyleptic.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 NNTP newsgroup(s).