From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail3-relais-sop.national.inria.fr (mail3-relais-sop.national.inria.fr [192.134.164.104]) by sympa.inria.fr (Postfix) with ESMTPS id 0D4BB7FAD3 for ; Fri, 24 Oct 2014 16:54:43 +0200 (CEST) Received-SPF: None (mail3-smtp-sop.national.inria.fr: no sender authenticity information available from domain of modlfo@gmail.com) identity=pra; client-ip=209.85.213.176; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="modlfo@gmail.com"; x-sender="modlfo@gmail.com"; x-conformance=sidf_compatible Received-SPF: Pass (mail3-smtp-sop.national.inria.fr: domain of modlfo@gmail.com designates 209.85.213.176 as permitted sender) identity=mailfrom; client-ip=209.85.213.176; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="modlfo@gmail.com"; x-sender="modlfo@gmail.com"; x-conformance=sidf_compatible; x-record-type="v=spf1" Received-SPF: None (mail3-smtp-sop.national.inria.fr: no sender authenticity information available from domain of postmaster@mail-ig0-f176.google.com) identity=helo; client-ip=209.85.213.176; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="modlfo@gmail.com"; x-sender="postmaster@mail-ig0-f176.google.com"; x-conformance=sidf_compatible X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AqsDACJnSlTRVdWwlGdsb2JhbABcg2JYuUEGgnWQZwqHTQKBBxYBEQEBAQEHCwsJEjCEAgEBAQMBAQIPKAYBGxILAQMBCwYFCwMKDSEjEQEFAQoEAQ0GExICBgiICQEDCQkFCKhCbo0lgxGIawoZJwMKZ4VRAQEBAQEBAQEBAQEBAQEBAQEBARMBBQ6GF4oAMweDLYEeBYUVBYZJimiHEoFthX+MTEGFSU6CSwEBAQ X-IPAS-Result: AqsDACJnSlTRVdWwlGdsb2JhbABcg2JYuUEGgnWQZwqHTQKBBxYBEQEBAQEHCwsJEjCEAgEBAQMBAQIPKAYBGxILAQMBCwYFCwMKDSEjEQEFAQoEAQ0GExICBgiICQEDCQkFCKhCbo0lgxGIawoZJwMKZ4VRAQEBAQEBAQEBAQEBAQEBAQEBARMBBQ6GF4oAMweDLYEeBYUVBYZJimiHEoFthX+MTEGFSU6CSwEBAQ X-IronPort-AV: E=Sophos;i="5.04,780,1406584800"; d="scan'208";a="84549077" Received: from mail-ig0-f176.google.com ([209.85.213.176]) by mail3-smtp-sop.national.inria.fr with ESMTP/TLS/RC4-SHA; 24 Oct 2014 16:54:42 +0200 Received: by mail-ig0-f176.google.com with SMTP id hn18so511935igb.3 for ; Fri, 24 Oct 2014 07:54:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=references:mime-version:in-reply-to:content-type :content-transfer-encoding:message-id:cc:from:subject:date:to; bh=eegzhyHgIj1kRvgtNtn6ezG7jI++G770ArVpYepzJL8=; b=BQOh5VeXrZr2BnW9AOMWpf/2SVkLQY3zR3jESMJ7cGL1xjFxKddDHqwSIgiwt+v46T wQAKHVVNi8aWzr3mfovZzioa/HGMc6ED4HnMLXo4NCkquiSZNRGVUufUnTS9FaWkLr+G P/TgJFqJuBS249kJX8EMkBJNmX4Iv2hd0Pt7nKQjis72KBqWDQ5L9wnmTfFTSUQJbyk5 DyHjgE9TqM5gt6ciE8l3evvbNM/hHRLRmOpaY2plsW6pmBHDJ1x70Bwvx2k2UDS2e8nY XrqZfxz61L8xFPhsym7flD3bA1GTM6TaEnw4Ie9FYYSyArptEOomqgNtiaJrVWdhYIWD XOCw== X-Received: by 10.50.83.97 with SMTP id p1mr4198669igy.19.1414162480979; Fri, 24 Oct 2014 07:54:40 -0700 (PDT) Received: from [192.168.9.97] (173-165-7-125-Illinois.hfc.comcastbusiness.net. [173.165.7.125]) by mx.google.com with ESMTPSA id qk10sm983479igc.12.2014.10.24.07.54.39 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 24 Oct 2014 07:54:39 -0700 (PDT) References: Mime-Version: 1.0 (1.0) In-Reply-To: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Message-Id: <57F9E0AC-4397-48B0-BCA8-094ACE49A4A7@gmail.com> Cc: "caml-list@inria.fr" X-Mailer: iPod touch Mail (12A405) From: Leonardo Laguna Ruiz Date: Fri, 24 Oct 2014 09:54:36 -0500 To: David Allsopp Subject: Re: [Caml-list] ocamlbuild on cygwin I found the same problem. The reason why I'm trying to use the cygwin port = is because in the other ports debugging is very bad and compiling most of t= he libraries is a pain. But at the end, it is not possible to make commerci= al applications with cygwin. So I end up using the three ports when working= on windows. Leonardo > On 23 okt 2014, at 18:16, David Allsopp wrote: >=20 > Gergely Szilvasy wrote: >> I'm trying to get as much of the ocaml/opam stack working on cygwin as p= ossible >> (as if there wasn't enough pain and suffering in the world already). >=20 > That's some pain! Not that it affects the bug you describe, but do you ha= ve a specific reason to use the Cygwin build, and not the MinGW/MSVC ports? >=20 >> Opam compiles without any issues, and I can switch to (let's say) 4.02.1= cleanly. >>=20 >> However, ocamlbuild fails for me in "opam install react" with the follow= ing error: >>=20 >> "Failure: ocamlfind not found on path, but -no-ocamlfind not used." >>=20 >> (Note that react is required by utop, for example, so it's a pretty basi= c requirement.) >>=20 >> This is where the exception is thrown: >>=20 >> https://github.com/ocaml/ocaml/blob/trunk/ocamlbuild/options.ml#L295 >>=20 >> It is the result of Command.search_in_path not finding ocamlfind: >>=20 >> https://github.com/ocaml/ocaml/blob/trunk/ocamlbuild/command.ml#L130 >>=20 >> Which appears to be caused by file_or_exe_exists not appending ".exe" to= the filename when Sys.os_type =3D >> "Cygwin" (which is what I see as os_type when compiling on cygwin): >>=20 >> https://github.com/ocaml/ocaml/blob/trunk/ocamlbuild/command.ml#L128 >=20 > This test is weak, and the behaviour is a bug (=3D> raise a report in Man= tis). ocamlbuild should query the Config module from the compiler libs and = do one of the following: >=20 > 1. Add an extra value ext_exe : string which would be ".exe" for Windows = builds (*including* Cygwin) and "" for everything else. > 2. Instead of detecting Sys.os_type =3D "Cygwin", instead do Filename.che= ck_suffix Config.default_executable_name ".exe" (I can't check on this mach= ine, but I'm fairly sure that ocamlc -config will shows the normal camlprog= .exe for default_executable_name?) >=20 >> In any case, I'm pretty sure this fairly simple bug is not a (very) rece= nt=20 >> regression, so I'm wondering if anybody cares about opam/ocaml on cygwin= ?=20 >> I'd really like to use opam, because it looks to me this is the communit= y's=20 >> preferred way of distributing bits. My question is, really, what is the= =20 >> status of ocaml/opam on cygwin? Is there an alternative environment for= =20 >> Windows + opam that works better? (I know about wodi, but I'd prefer=20 >> opam.) Is it worth spending time fixing these issues on cygwin? >=20 > Cygwin is a targeted platform, so bugs in it are important - but I think = that the small number of Windows OCaml users use the MinGW or MSVC ports so= they may take a while to be noticed! >=20 > Opam status on Windows is partially recorded in https://github.com/ocaml/= opam/issues/246. >=20 > HTH, >=20 >=20 > David >=20 > --=20 > Caml-list mailing list. Subscription management and archives: > https://sympa.inria.fr/sympa/arc/caml-list > Beginner's list: http://groups.yahoo.com/group/ocaml_beginners > Bug reports: http://caml.inria.fr/bin/caml-bugs