Bug#637147: Confirming bug

2011-08-16 Thread Gerd Stolpmann
Hi,

I confirm this problem in the documentation.

I've chosen a more radical approach for a permanent resolution: The next
version of Ocamlnet will support the additional directive NetcgiRequire.
It works like "#require" in a findlib-enabled toploop. All the
NetcgiLoad directives can then be replaced by a single
"NetcgiRequire netcgi2-apache". The release will be soon.

Gerd
-- 
----
Gerd Stolpmann, Darmstadt, Germanyg...@gerd-stolpmann.de
Creator of GODI and camlcity.org.
Contact details:http://www.camlcity.org/contact.html
Company homepage:   http://www.gerd-stolpmann.de
*** Searching for new projects! Need consulting for system
*** programming in Ocaml? Gerd Stolpmann can help you.





-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org



Bug#564816: libpostgresql-ocaml-dev: Monothreaded toplevel requires module Mutex.

2010-01-12 Thread Gerd Stolpmann

Am Dienstag, den 12.01.2010, 08:57 +0100 schrieb Stéphane Glondu:
> severity 564816 normal
> tags 564816 + upstream
> thanks
> 
> Guillaume Yziquel a écrit :
> > META file seems incorrect. Here's a toplevel session with findlib:
> > [...]
> > # #require "postgresql";;
> > /usr/lib/ocaml/unix.cma: loaded
> > /usr/lib/ocaml/postgresql: added to search path
> > # #require "postgresql";;/postgresql.cma: loaded
> > Error: Reference to undefined global `Mutex'
> 
> I think this is quite common for libraries depending on threads. I guess
> this is because there are multiple implementation of them, so they are
> always explicitly given (on command line, at least).

No, the reason is that the bytecode threading implementation is partly
done within the standard library, and if you say -vmthread a different
version of the standard library is loaded. For native threads this would
not be necessary, but I think ocaml does it the same way (requiring the
switch -thread) for symmetry with the bytecode case.

The existence of these switches (-vmthread, -thread) extends to findlib
in so far multi-threading is handled specially, and you cannot simply
create a dependency on threads.{cma,cmxa}.

> Sure, there is not much choice in the toplevel so I guess we could tweak
> the META file so that #require "postgresql;;" works out of the box. For
> example, we could just load an additional module that would do
> "#thread;;" inside a toplevel. I'm not sure this is the idiomatic way,
> though, nor do I know the guidelines for this.

No, the idiomatic way is to signal an error when the library is loaded
without having enabled threads beforehand:

error(-mt) = "This library requires multi-threading support"

(read: if multi-threading is not enabled, fail with this error message)

Gerd
-- 

Gerd Stolpmann, Bad Nauheimer Str.3, 64289 Darmstadt,Germany 
g...@gerd-stolpmann.de  http://www.gerd-stolpmann.de
Phone: +49-6151-153855  Fax: +49-6151-997714





--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org



Bug#450903: libocamlnet-ssl-ocaml: segfault on custom ssl bindings

2008-03-04 Thread Gerd Stolpmann

Am Samstag, den 09.02.2008, 13:36 +0100 schrieb Stéphane Glondu:
> Stefano Zacchiroli a écrit :
> >> While playing with the ssl_client.ml example, I ended up correcting two
> >> issues:
> >> * ssl_client.ml must use:
> >> let cl_ctx = Ssl.create_context Ssl.TLSv1 Ssl.Client_context  in
> >>   to use the correct function from ocaml-ssl
> >> * The example segfaulted..
> > 
> > Can you please provide the example, so that we can test the fix?
> 
> The example is in ocamlnet source, at location:
> examples/equeue/ssl/ssl_client.ml
> 
> I reproduced the bug, and checked that the fix works. I contacted Gerd
> Stolpmann about this (he is CC of this mail, and I also talked to him in
> real life). Meanwhile, I've commited it in the svn.

The fix is now incorporated in Ocamlnet, and will be included in the
next release. Many thanks for tracking it down and fixing it!

Gerd
-- 

Gerd Stolpmann * Viktoriastr. 45 * 64293 Darmstadt * Germany 
[EMAIL PROTECTED]  http://www.gerd-stolpmann.de
Phone: +49-6151-153855  Fax: +49-6151-997714