caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Conglun Yao <yaoconglun@gmail.com>
To: Gerd Stolpmann <gerd@gerd-stolpmann.de>
Cc: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] Dynlink and ocamlfind for camlp4 3.11?
Date: Mon, 5 Oct 2009 16:17:36 +0100	[thread overview]
Message-ID: <f7b50d2a0910050817x58ffcc82u1053cb3915a2170e@mail.gmail.com> (raw)
In-Reply-To: <1254749754.1870.12.camel@flake.lan.gerd-stolpmann.de>

[-- Attachment #1: Type: text/plain, Size: 1701 bytes --]

Thanks for all of your help.

Unfortunately, it still does not work. It is really nightmare to use camp4
in a windows machine.  I try to reinstall plain OCaml without using GODI, if
the same error happens, I have to go back to Ubuntu.

Thanks.

Conglun

On Mon, Oct 5, 2009 at 2:35 PM, Gerd Stolpmann <gerd@gerd-stolpmann.de>wrote:

>
>
>
> While cygwin cannot load shared libraries from bytecode, it still can
> load pure bytecode dynamically. It is reasonable that there is a
> dynlink.cma for this case, and that camlp4lib.cma depends on it.
>
> findlib has a special mode for platforms that cannot load shared
> libraries dynamically. This mode seems to be broken  - it calls a script
> safe_camlp4 instead of camlp4, and safe_camlp4 produces ad hoc a new
> camlp4-type executable that includes the required C libraries - without
> that trick you couldn't use json-static at all on these platforms:
>
> https://godirepo.camlcity.org/svn/lib-findlib/trunk/tools/safe_camlp4
>
> The question is now whether the error is in this script (does it have to
> add dynlink.cma anyway?) or whether mkcamlp4 is broken.
>
> Can you try to change safe_camlp4 so the line
>
> mkcamlp4 -o $tmp_camlp4 $cp4_mods || exit
>
> reads
>
> mkcamlp4 -o $tmp_camlp4 dynlink.cma $cp4_mods || exit
>
> ? (I don't have a cygwin ocaml at hand.) safe_camlp4 should be in the
> bin/ directory.
>
> Gerd
> --
> ------------------------------------------------------------
> Gerd Stolpmann, Bad Nauheimer Str.3, 64289 Darmstadt,Germany
> gerd@gerd-stolpmann.de          http://www.gerd-stolpmann.de
> Phone: +49-6151-153855                  Fax: +49-6151-997714
> ------------------------------------------------------------
>
>

[-- Attachment #2: Type: text/html, Size: 2391 bytes --]

  reply	other threads:[~2009-10-05 15:17 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-04 14:22 Conglun Yao
2009-10-04 14:24 ` Conglun Yao
2009-10-04 19:05 ` [Caml-list] " Richard Jones
2009-10-04 19:32   ` Conglun Yao
2009-10-04 19:37     ` Richard Jones
2009-10-04 19:53       ` Conglun Yao
2009-10-04 20:06         ` Conglun Yao
2009-10-04 20:33         ` Richard Jones
2009-10-04 20:35           ` Richard Jones
2009-10-04 21:14             ` David Allsopp
2009-10-04 21:40               ` Conglun Yao
2009-10-05  7:39                 ` David Allsopp
2009-10-05 10:14                   ` Conglun Yao
2009-10-05 13:35         ` Gerd Stolpmann
2009-10-05 15:17           ` Conglun Yao [this message]
2009-10-05 17:28             ` David Allsopp
2009-10-05 17:55           ` Alain Frisch

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=f7b50d2a0910050817x58ffcc82u1053cb3915a2170e@mail.gmail.com \
    --to=yaoconglun@gmail.com \
    --cc=caml-list@yquem.inria.fr \
    --cc=gerd@gerd-stolpmann.de \
    /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).