From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Original-To: caml-list@sympa.inria.fr Delivered-To: caml-list@sympa.inria.fr Received: from mail2-relais-roc.national.inria.fr (mail2-relais-roc.national.inria.fr [192.134.164.83]) by sympa.inria.fr (Postfix) with ESMTPS id ACDF87FAD2 for ; Thu, 23 Oct 2014 22:14:38 +0200 (CEST) Received-SPF: None (mail2-smtp-roc.national.inria.fr: no sender authenticity information available from domain of szilvasy@gmail.com) identity=pra; client-ip=209.85.215.50; receiver=mail2-smtp-roc.national.inria.fr; envelope-from="szilvasy@gmail.com"; x-sender="szilvasy@gmail.com"; x-conformance=sidf_compatible Received-SPF: Pass (mail2-smtp-roc.national.inria.fr: domain of szilvasy@gmail.com designates 209.85.215.50 as permitted sender) identity=mailfrom; client-ip=209.85.215.50; receiver=mail2-smtp-roc.national.inria.fr; envelope-from="szilvasy@gmail.com"; x-sender="szilvasy@gmail.com"; x-conformance=sidf_compatible; x-record-type="v=spf1" Received-SPF: None (mail2-smtp-roc.national.inria.fr: no sender authenticity information available from domain of postmaster@mail-la0-f50.google.com) identity=helo; client-ip=209.85.215.50; receiver=mail2-smtp-roc.national.inria.fr; envelope-from="szilvasy@gmail.com"; x-sender="postmaster@mail-la0-f50.google.com"; x-conformance=sidf_compatible X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: ApUBAFdhSVTRVdcym2dsb2JhbABcg2JcgwLJfYdNgQwHFgERAQEBAQEGCwsJFC6EGxEdARsPDwMSCQc3AiQBEQEFARYzDogKAQMRDaQmgx5uizGBcoMRiEEKGScNZ4VdGgEBBA6QRoMCgVQFlkuHEpQ4GCmFLTwvgksBAQE X-IPAS-Result: ApUBAFdhSVTRVdcym2dsb2JhbABcg2JcgwLJfYdNgQwHFgERAQEBAQEGCwsJFC6EGxEdARsPDwMSCQc3AiQBEQEFARYzDogKAQMRDaQmgx5uizGBcoMRiEEKGScNZ4VdGgEBBA6QRoMCgVQFlkuHEpQ4GCmFLTwvgksBAQE X-IronPort-AV: E=Sophos;i="5.04,777,1406584800"; d="scan'208";a="102621214" Received: from mail-la0-f50.google.com ([209.85.215.50]) by mail2-smtp-roc.national.inria.fr with ESMTP/TLS/RC4-SHA; 23 Oct 2014 22:14:22 +0200 Received: by mail-la0-f50.google.com with SMTP id s18so1514122lam.23 for ; Thu, 23 Oct 2014 13:14:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=vAZIcNqToQODbljWywR3Zp/9rCI6JZLrIanpBJ9oABE=; b=uDnvFlpy4/NO6uKh+6JRTkF4P5pKtYfaqJyApkBqceWjWZQ5zlpUc4CoJdMGOUjr1S XgtL+qYl4LsMDmC69YsyNbbnzXDUhxaVgpRu1t3g/hMVSoRiGrdevQfCdVuPnI7GSJ8i AeSn/p0TGCg9XBjEijZrp701SUPZXMWjMF6GU1M1EVmmWjht86QHcIcMLTBAvb25wG7k gxN19uWDiM4jhZi7GakQjjvmzTts8bqM9V4g+6HNe0LzaHuQGAeOyu+CvK/bahkndROJ qUMpc+qPB5REuxXU4yCzpwL+V3p76OkyTC+Mv0hO/+iRIqioQ8CAPudQLLp+NVKyygDg NiRA== MIME-Version: 1.0 X-Received: by 10.112.45.228 with SMTP id q4mr224377lbm.35.1414095261348; Thu, 23 Oct 2014 13:14:21 -0700 (PDT) Received: by 10.113.5.133 with HTTP; Thu, 23 Oct 2014 13:14:21 -0700 (PDT) Date: Thu, 23 Oct 2014 21:14:21 +0100 Message-ID: From: Gergely Szilvasy To: caml-list@inria.fr Content-Type: multipart/alternative; boundary=001a11345f6abb3ab305061cb57f Subject: [Caml-list] ocamlbuild on cygwin --001a11345f6abb3ab305061cb57f Content-Type: text/plain; charset=UTF-8 Hello, First of all, as this is my first post ever on this list, to all of you who contribute to ocaml and its "ecosystem": a big thank you (ou encore mieux: merci beaucoup)! It's brilliant stuff. I'm trying to get as much of the ocaml/opam stack working on cygwin as possible (as if there wasn't enough pain and suffering in the world already). Opam compiles without any issues, and I can switch to (let's say) 4.02.1 cleanly. However, ocamlbuild fails for me in "opam install react" with the following error: "Failure: ocamlfind not found on path, but -no-ocamlfind not used." (Note that react is required by utop, for example, so it's a pretty basic requirement.) This is where the exception is thrown: https://github.com/ocaml/ocaml/blob/trunk/ocamlbuild/options.ml#L295 It is the result of Command.search_in_path not finding ocamlfind: https://github.com/ocaml/ocaml/blob/trunk/ocamlbuild/command.ml#L130 Which appears to be caused by file_or_exe_exists not appending ".exe" to the filename when Sys.os_type = "Cygwin" (which is what I see as os_type when compiling on cygwin): https://github.com/ocaml/ocaml/blob/trunk/ocamlbuild/command.ml#L128 I'm not expert on either ocaml or cygwin, so my analysis may be off. -- In any case, I'm pretty sure this fairly simple bug is not a (very) recent regression, so I'm wondering if anybody cares about opam/ocaml on cygwin? I'd really like to use opam, because it looks to me this is the community's preferred way of distributing bits. My question is, really, what is the status of ocaml/opam on cygwin? Is there an alternative environment for Windows + opam that works better? (I know about wodi, but I'd prefer opam.) Is it worth spending time fixing these issues on cygwin? Any thoughts? Regards, Gergely --001a11345f6abb3ab305061cb57f Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hello,

First of all, as this is my firs= t post ever on this list, to all of you who contribute to ocaml and its &qu= ot;ecosystem": a big thank you (ou encore mieux: merci beaucoup)! It&#= 39;s brilliant stuff.

I'm trying to get as muc= h of the ocaml/opam stack working on cygwin as possible (as if there wasn&#= 39;t enough pain and suffering in the world already).=C2=A0

<= /div>
Opam compiles without any issues, and I can switch to (let's = say) 4.02.1 cleanly.

However, ocamlbuild fails for= me in "opam install react" with the following error:
<= br>
"Failure: ocamlfind not found on path, but -no-ocamlfind= not used."

(Note that react is required by u= top, for example, so it's a pretty basic requirement.)

This is where the exception is thrown:

https://github.com/ocaml/ocaml/blob/trunk/ocamlbuild/options.ml#L295

It is the result of Command.search_in_path n= ot finding ocamlfind:


=
Which appears to be caused by file_or_exe_exists not appending ".= exe" to the filename when=C2=A0Sys.os_type =3D "Cygwin" (whi= ch is what I see as os_type when compiling on cygwin):

=

I'm not expert on either ocaml or= cygwin, so my analysis may be off.

--
<= br>
In any case, I'm pretty sure this fairly simple bug is no= t a (very) recent regression, so I'm wondering if anybody cares about o= pam/ocaml on cygwin? I'd really like to use opam, because it looks to m= e this is the community's preferred way of distributing bits. My questi= on is, really, what is the status of ocaml/opam on cygwin? Is there an alte= rnative environment for Windows + opam that works better? (I know about wod= i, but I'd prefer opam.) Is it worth spending time fixing these issues = on cygwin?

Any thoughts?

= Regards,
Gergely

--001a11345f6abb3ab305061cb57f--