From: Jiten Pathy <jpathy@fssrv.net>
To: caml-list@inria.fr
Subject: Re: [Caml-list] ocsigen static linking
Date: Tue, 4 Nov 2014 18:54:32 -0800 [thread overview]
Message-ID: <CAL2Z3DDLUrVr_FSQ2A8v=agHUTnQbtjasL2Ss_kx1fDen48nFw@mail.gmail.com> (raw)
In-Reply-To: <CAL2Z3DBXtGx__=p+DoXToXh2r7sYKv69Wg8o6p4-JJfm1xVMpQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 615 bytes --]
By looking into the ocsigenserver a bit it appears the extension is
registered with name ocsipersist. However changing to extension name in
configuration to ocsipersist raised exception Not_found again.
linking package eliom.server also doesn't work for extension name "eliom".
On Tue, Nov 4, 2014 at 6:26 PM, Jiten Pathy <jpathy@fssrv.net> wrote:
> Trying to link packages statically as per
> http://ocsigen.org/ocsigenserver/2.5/manual/staticlink
> .
>
> Getting errors while running
> main: Fatal - While loading named module ocsipersist-sqlite
>
> Any ideas? Also any document on how ocaml dynlink works?
>
[-- Attachment #2: Type: text/html, Size: 1903 bytes --]
prev parent reply other threads:[~2014-11-05 2:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-05 2:26 Jiten Pathy
2014-11-05 2:54 ` Jiten Pathy [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='CAL2Z3DDLUrVr_FSQ2A8v=agHUTnQbtjasL2Ss_kx1fDen48nFw@mail.gmail.com' \
--to=jpathy@fssrv.net \
--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;
as well as URLs for NNTP newsgroup(s).