David MENTRE <[EMAIL PROTECTED]> writes:
> Which process is calling "./cdo2ml"? cduce?
Ok, I've seen your post en CDuce mailing list. This cduce which is
calling cdo2ml. Quite strange indeed.
Yours,
d.
--
pub 1024D/A3AD7A2A 2004-10-03 David MENTRE <[EMAIL PROTECTED]>
5996 CC46 4612 9CA4 3562
Thomas,
Thomas Petazzoni <[EMAIL PROTECTED]> writes:
> For those who want to try the compilation with CDuce 0.3.9, Debian
> packages for stable, testing and unstable are available on my Debian
> repository (http://thomas.enix.org/pub/debian/packages, as usual). I
> have two Lintian warnings left
Thomas Petazzoni <[EMAIL PROTECTED]> writes:
> If the process calling cduce cd'ed into the cduce directory (i.e
> /usr/bin), then calling ./cdo2ml should work, because cdo2ml is in
> /usr/bin ;-)
Ok.
Which process is calling "./cdo2ml"? cduce?
Yours,
d.
--
pub 1024D/A3AD7A2A 2004-10-03 David
Hello,
David MENTRE a écrit :
> A possible explanation: when you run "cduce" directly, the calling
> process cd to the directory where cduce lives and starts ./cduce, which
> does not happen if you give the absolute path.
If the process calling cduce cd'ed into the cduce directory (i.e
/usr/bin)
Thomas Petazzoni <[EMAIL PROTECTED]> writes:
> As I said in the other e-mail, the problem was that the preprocessor to
> use is "cduce --mlstub" instead of "cdo2ml --static".
>
> However, running "cduce --mlstub" doesn't work, because it looks for
> cdo2ml in the current directory. I have found a
Hello,
David MENTRE a écrit :
> A simple solution seems to avoid that path handling at all, assuming
> cdo2ml is in the PATH. So we would have:
Okay, this appears to be a solution. However, I mailed the cduce users
mailing list to raise this issue, and we'll see what solution they prefer.
Since
Thomas,
A simple solution seems to avoid that path handling at all, assuming
cdo2ml is in the PATH. So we would have:
Thomas Petazzoni <[EMAIL PROTECTED]> writes:
> I grepped in cduce source code, and I think the call to cdo2ml is in
> ocamliface/mlstub.ml, around line 550 :
>
> let exe = File
Thomas Petazzoni <[EMAIL PROTECTED]> writes:
> I traced down the issue a bit further, and I come to the conclusion that
> cdo2ml doesn't work the way it worked, or it is buggy. Trying to
> manually run cdo2ml doesn't work (it waits forever). Running it with
If I understood CDuce release notes cor
Hello,
Thomas Petazzoni a écrit :
> I traced down the issue a bit further, and I come to the conclusion that
> cdo2ml doesn't work the way it worked, or it is buggy. Trying to
> manually run cdo2ml doesn't work (it waits forever). Running it with
> strace gives interesting stuff :
I went further
Hello,
[ Sorry for breaking the thread, but my last e-mail didn't reach yet the
demexp-dev mailing-list, for some reason. Maybe because the server is slow ]
Thomas Petazzoni a écrit :
> I traced down the issue a bit further, and I come to the conclusion that
> cdo2ml doesn't work the way it work
Hello,
Thomas Petazzoni a écrit :
> I'm trying to compile DemExp 0.4 with CDuce 0.3.9, but I'm facing a
> compilation problem. The compilation process stalls at:
I traced down the issue a bit further, and I come to the conclusion that
cdo2ml doesn't work the way it worked, or it is buggy. Trying
Hello,
I'm trying to compile DemExp 0.4 with CDuce 0.3.9, but I'm facing a
compilation problem. The compilation process stalls at:
ocamlfind ocamlopt -linkpkg -c -package "rpc str" -package "cduce
pxp-engine pxp-lex-utf8 pcre netstring netclient ulex equeue threads
num" -I srv -I net -I lib -I bi
12 matches
Mail list logo
