From mboxrd@z Thu Jan  1 00:00:00 1970
Received: (from majordomo@localhost) by pauillac.inria.fr (8.7.6/8.7.3) id VAA00255; Thu, 11 Sep 2003 21:02:23 +0200 (MET DST)
X-Authentication-Warning: pauillac.inria.fr: majordomo set sender to owner-caml-list@pauillac.inria.fr using -f
Received: from nez-perce.inria.fr (nez-perce.inria.fr [192.93.2.78]) by pauillac.inria.fr (8.7.6/8.7.3) with ESMTP id VAA03431 for <caml-list@pauillac.inria.fr>; Thu, 11 Sep 2003 21:02:22 +0200 (MET DST)
Received: from tallman.kefka.frap.net (adsl-64-162-212-212.dsl.snfc21.pacbell.net [64.162.212.212])
	by nez-perce.inria.fr (8.11.1/8.11.1) with ESMTP id h8BJ2LT18845
	for <caml-list@inria.fr>; Thu, 11 Sep 2003 21:02:21 +0200 (MET DST)
Received: by tallman.kefka.frap.net (Postfix, from userid 1000)
	id AF309AED2E; Thu, 11 Sep 2003 12:02:20 -0700 (PDT)
Date: Thu, 11 Sep 2003 12:02:20 -0700
From: kknowles@uclink.berkeley.edu
To: caml-list@inria.fr
Subject: [Caml-list] Re: mod_caml + dynlink + parsing
Message-ID: <20030911190220.GA2479@tallman.kefka.frap.net>
References: <20030911183932.GA2057@tallman.kefka.frap.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20030911183932.GA2057@tallman.kefka.frap.net>
User-Agent: Mutt/1.4i
X-Loop: caml-list@inria.fr
X-Spam: no; 0.00; dynlink:01 sanity:01 hashtbl:01 misuse:01 dynlink:01 3.06:01 usr:01 ocaml:01 caml:01 caml:01 0700,:01 handler:01 interfaces:01 sep:01 linking:02 
Sender: owner-caml-list@pauillac.inria.fr
Precedence: bulk

Just an update, I've done a few more sanity checks with other parts of the
standard library, and a module using Array, Hashtbl, List, Random works... so
I'm convinced it is a specific issue, rather than a general misuse of Dynlink.

On Thu, Sep 11, 2003 at 11:39:32AM -0700, kknowles@uclink.berkeley.edu wrote:
> 
> I've got mod_caml up and running in my apache2 installation, the examples work
> fine, but I'm having a bit of trouble with dynamic loading of my handler (ocaml
> 3.06), and I think it is a Dynlink issue rather than a mod_caml one.
> 
> My modules uses a lot of the standard library, and mod_caml did not expose Array
> in its call to Dynlink.add_interfaces.  In fact, I added Str, Array, Parsing,
> and Lexing to this list.  But the module still fails to load, with the following
> error:
> 
> Failure("error while linking /usr/local/apache2/modules/mod_aspcc.cma.
> Reference to undefined global `Parsing'")
> 
> When an interface is not exposed through Dynlink, the error message is along the
> lines of "An implementation for module XXX is not available" (Sorry I don't have
> the exact message), so I think this is something else.  Can anyone help with
> this?
> 
> -Kenn

-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners