I do use the native O'Caml and Cygwin Emacs. I do this because MinGW Caml seems to be using "ar" instructions that are meant for the Cygwin version of "ar" (meaning they have an ampersand preceding the DOS path of the temporary file, which MinGW's "ar" doesn't understand).
It looks to me as if MinGW Caml is actually built with Cygwin, using "gcc -mno-cygwin". Maybe I'm mistaken? So, I use MinGW Caml with Cygwin.
Apparently, there is an issue in the ptys. I would say that's an apt description. I'll have to try the "ocamlmktop -custom".
I really don't want to use a Cygwin version of Caml. I don't like it when projects (Cygwin, Berkeley DB) tell me that I have to license my source code a certain way when I link to their libraries. I aknowledge and respect their wishes, but I'm also free not to use those projects (and therefore, not to contribute my bugfixes and experience to their product). I'm happy to use the shell and the tools, but I want my binaries to be unmistakenly mine.
Jeremy
On 2/20/06, Igor Peshansky <pechtcha@cs.nyu.edu> wrote:
On Mon, 20 Feb 2006, Matthieu Dubuget wrote:
> Igor Peshansky a écrit :
>
> > On Mon, 20 Feb 2006, Matthieu Dubuget wrote:
> >
> > > Igor Peshansky a écrit :
> > >
> > > > On Sun, 19 Feb 2006, Jeremy Shute wrote:
> > > >
> > > > > Hi,
> > > > >
> > > > > When I fire up Tuareg mode under native Windows emacs and run an
> > > > > inferior-caml, I get what I expect (Caml running in an emacs
> > > > > buffer). When I do so with Cygwin's Emacs, I get an empty buffer
> > > > > and a process "
ocamlrun.exe" dressed in new window trim, which
> > > > > seems completely detached from the inferior-caml buffer (meaning
> > > > > C-c C-e does NOT send commands to this new process).
> > > > >
> > > > > I asked Albert Cohen, Tuareg-mode's creator, but he didn't know
> > > > > much about Windows, and suggested I ask here.
> > > > >
> > > > > What magic Elisp incantation will shackle invocations of "ocaml"
> > > > > in a buffer, when using Cygwin emacs? I also tried "sh -c
> > > > > ocaml" to no avail...
> > > > >
> > > > > Jeremy
> > > >
> > > > Hi, Jeremy,
> > > >
> > > > This sounds like either a Cygwin emacs bug or a bug in the
> > > > commands Tuareg uses to start the ocaml process that manifests
> > > > only in Cygwin's emacs. Since this is likely not a problem with
> > > > ocaml itself (but rather with either the Cygwin ocaml package or
> > > > Cygwin emacs), the main Cygwin list (<cygwin at cygwin dot com>)
> > > > would be a better place to discuss it and track down the culprit.
> > > >
> > > > Unfortunately, I don't use emacs, and haven't tested the Cygwin
> > > > O'Caml package under emacs (and wouldn't know how). Thus, another
> > > > reason to move this to the main Cygwin list, since there are many
> > > > emacs experts there.
> > > >
> > > > One thing that would help is following the Cygwin problem
> > > > reporting guidelines at <http://cygwin.com/problems.html
> when
> > > > re-posting this to the main Cygwin list (particularly attaching
> > > > the output of "cygcheck -svr").
> > > >
> > > > See you on the Cygwin list, :-)
> > > >
> > > > Igor Peshansky, the Cygwin O'Caml volunteer maintainer
> > >
> > > Last time I had a similar problem, I discovered that recompiling the
> > > ocaml toplevel was solving the problem.
> > >
> > > Maybe this will work for you ?
> >
> > Hmm, indeed. Though don't forget, Matthieu, that Cygwin is still at
> > version 3.08.1...
> >
> > Jeremy, if recompiling works for you, please let me know, and I'll
> > release a rebuit version of ocaml for Cygwin. You can download the
> > ocaml source package using Cygwin setup and run the packaging script
> > to build (use the "--help" option for a list of possible steps).
> >
> > Igor Peshansky, the Cygwin O'Caml volunteer maintainer
>
> I would have describe my problem the same way as Jeremy.
> I do use one standard native distribution of Ocaml, and cygwin version
> of emacs.
> I did not used the right term though: I did not meant re-compiling the
> toplevel. Just creating a new one with
> ocamlmktop -custom ...
Ah. If you use a native ocaml, it may not work with Cygwin emacs, as it
won't understand the ptys that emacs uses to communicate with it (and thus
will pop up a console). I forgot to ask Jeremy whether he uses the Cygwin
version of ocaml, or the Windows native one. A quick test of this outside
emacs is to try using rxvt -- if your ocaml works inside that, it probably
will work inside emacs too.
I don't know why remaking the toplevel helped you (since that didn't
create a Cygwin version of it). Rebuilding under Cygwin would most likely
help, as would installing the pre-built Cygwin ocaml package that is part
of the Cygwin distribution.
Igor Peshansky, Cygwin O'Caml volunteer maintainer
--
http://cs.nyu.edu/~pechtcha/
|\ _,,,---,,_ pechtcha@cs.nyu.edu | igor@watson.ibm.com
ZZZzz /,`.-'`' -. ;-;;,_ Igor Peshansky,
Ph.D. (name changed!)
|,4- ) )-,_. ,\ ( `'-' old name: Igor Pechtchanski
'---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow!
"Las! je suis sot... -Mais non, tu ne l'es pas, puisque tu t'en rends compte."
"But no -- you are no fool; you call yourself a fool, there's proof enough in
that!" -- Rostand, "Cyrano de Bergerac"
_______________________________________________
Caml-list mailing list. Subscription management:
http://yquem.inria.fr/cgi-bin/mailman/listinfo/caml-list
Archives: http://caml.inria.fr
Beginner's list:
http://groups.yahoo.com/group/ocaml_beginners
Bug reports: http://caml.inria.fr/bin/caml-bugs