Version française
Home     About     Download     Resources     Contact us    

This site is updated infrequently. For up-to-date information, please visit the new OCaml website at

Browse thread
OCaml compilation
[ Home ] [ Index: by date | by threads ]
[ Search: ]

[ Message by date: previous | next ] [ Message in thread: previous | next ] [ Thread: previous | next ]
Date: 2010-05-28 (10:06)
From: Matthieu Dubuget <matthieu.dubuget@g...>
Subject: Re: [Caml-list] OCaml compilation
Thanks again.

In the meantime, I gone on another way: I really needed to have a 
working development environment on this notebook before leaving!

I just used brute force : copy of c:\cygwin from the working computer to 
the "new" one. My compiled version of ocaml came with this brute force copy.

This allowed me to try again my compilation script:
- ActiveTcl installation was not modified
- and this time, it passed ocamlbrowser compilation.

Now, can anybody confirm the behaviour I observed with a fresh cygwin 

I will (later) investigate the problem (taking your suggestion into 
account) on the virtual machine on which I reproduced the problem.



> Certainly looks correct, I agree. One thought - have you remembered to put C:\Tcl\bin in your PATH on the machines which are failing?
> Is flexlink definitely the same version on each machine? Two other possibilities:
> 1. Try entering the command that's failing manually with -verbose and then do the same with the flexlink command displayed, adding -v -v to see exactly what flexlink is doing.
> 2. Diff your two Cygwin dirs (a tool like ExamDiff Pro is good for this). If your old machine is using Cygwin 1.5 and the new ones 1.7 then that may be the cause. I had some weird issues when upgrading to Cygwin because if the location of Cygwin1.dll is wrong then cygpath returns garbage paths - which confuses the hell out of flexlink! However, I don't think this is what's affecting you because errors owing to that surfaced while linking ocamlc for me.
> Hope something there helps!