From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail1-relais-roc.national.inria.fr (mail1-relais-roc.national.inria.fr [192.134.164.82]) by walapai.inria.fr (8.13.6/8.13.6) with ESMTP id pAOAvFHc020392 for ; Thu, 24 Nov 2011 11:57:15 +0100 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: At8BAJ8izk7RVdy2mGdsb2JhbABEhQKlYQgiAQEBAQEICQ0HFCWBcgEBAQMBEgIPHQEbHgMBCwYFCw8CEQEBEwICIgERAQUBHAY1h2MIl2cKixxHgmaFDz2IcQIFCoEmhhEIAYICgRYElEqNWD2DeA X-IronPort-AV: E=Sophos;i="4.69,564,1315173600"; d="scan'208";a="132423094" Received: from mail-vx0-f182.google.com ([209.85.220.182]) by mail1-smtp-roc.national.inria.fr with ESMTP/TLS/RC4-SHA; 24 Nov 2011 11:57:10 +0100 Received: by vcbfk1 with SMTP id fk1so1342566vcb.27 for ; Thu, 24 Nov 2011 02:57:09 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; bh=TeRERDuVXkG5s0i71KYcU+jISVhkKKdMmOpPLfZbays=; b=whQclX9v/h0BbExI5lZ+nC8ByW34BfV5kyQ/uCHjo7N4+EJxGXW1k+PDmLoNSR/8GO nb4jtQw8Dqnp+1Pxs2iorWiLpAaGC+IzDYWvDyUcvne3QD4J8TVQjqjVqg7PzCAindNF oeU5ZlHJlm8JncEAxxsV8i02eNjZ5dlQyW99g= MIME-Version: 1.0 Received: by 10.182.124.9 with SMTP id me9mr9395956obb.1.1322132227699; Thu, 24 Nov 2011 02:57:07 -0800 (PST) Received: by 10.182.38.165 with HTTP; Thu, 24 Nov 2011 02:57:07 -0800 (PST) In-Reply-To: References: Date: Thu, 24 Nov 2011 12:57:07 +0200 Message-ID: From: Dmitry Grebeniuk To: "Paul A. Steckler" Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by walapai.inria.fr id pAOAvFHc020392 Subject: Re: [Caml-list] Issues with OCaml on Windows, MinGW build Hello. >  - You can't login to the MinGW shell to allow remote builds via ssh. > I can get most of the > required functionality by setting environment variables and calling > the MinGW's sh.exe > explicitly, but it would be useful to have instructions on how this should go. To allow remote builds via ssh, you should install sshd server. Another option is to use some kind of "continuous integration system" which will regularly check your source code repository and build binaries automatically. >  - When trying to build some standard OCaml packages, like cryptokit > and oUnit, the 'configure' > and 'make' steps fail badly. One reason is that 'configure' invokes an > OCaml program which calls > Sys.command, and on my computer, some of the arguments are filenames > with spaces in them. Unix scripts are too sure that there are no spaces in paths, it's easier to install everything in the path without spaces. (I've tried to fight this issue, but our forces were too inequal.) btw, why didn't you took overbld package, which has OCaml/mingw, cryptokit and oUnit already compiled? Here is the list of all "packages" in overbld distribution: http://overbld.hg.sourceforge.net/hgweb/overbld/overbld/file/tip/src > Has anyone had success building standard packages using the MinGW distribution? I had such success, but I didn't want to compile everything manually every time the new version is released or some bug is found and should be fixed as soon as possible (i.e. by me, by writing and applying patch locally), so I wrote some dumb scripts that can apply patches, compile, install "packages", taking into account their internal dependencies.