From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mail4-relais-sop.national.inria.fr (mail4-relais-sop.national.inria.fr [192.134.164.105])
	by walapai.inria.fr (8.13.6/8.13.6) with ESMTP id pAO888nE010866
	for <caml-list@sympa-roc.inria.fr>; Thu, 24 Nov 2011 09:08:08 +0100
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AnABAOv6zU5KfVM2kWdsb2JhbAAqGqpjCCIBAQEBCQsLBxQEIYFyAQEBBBICLAEbHQEDDAYFCw0uIgERAQUBHAYTCBMHh2sjl0cKi2OCZoUIPYhxAgEECopYBI0ihyiNWD2Ddw
X-IronPort-AV: E=Sophos;i="4.69,564,1315173600"; 
   d="scan'208";a="120665004"
Received: from mail-ee0-f54.google.com ([74.125.83.54])
  by mail4-smtp-sop.national.inria.fr with ESMTP/TLS/RC4-SHA; 24 Nov 2011 09:08:02 +0100
Received: by eekc13 with SMTP id c13so155542eek.27
        for <caml-list@inria.fr>; Thu, 24 Nov 2011 00:08:02 -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
         :cc:content-type;
        bh=4Fi626rBHr6X/oeNSrJ6fwNw0CwyPM14J67GOz1mBFA=;
        b=u8wk90wjcUcE75C54QpCPXQuQh3btQuvEgsRPwayHhfMSSdVxjocIbWBUQdIpSriaA
         kxd1w6lAh/yzVJGdb8H3UB7fZv7ZcbFML42s49mudKGpaJxcRlCbAW9+ULwLCK0elsad
         1hH5PSfs6Yg2aeZfTfeoMAj/bE08TMeLqn9uc=
MIME-Version: 1.0
Received: by 10.213.113.6 with SMTP id y6mr27241ebp.76.1322122080881; Thu, 24
 Nov 2011 00:08:00 -0800 (PST)
Received: by 10.213.8.136 with HTTP; Thu, 24 Nov 2011 00:08:00 -0800 (PST)
In-Reply-To: <slrnjcrrii.9th.sylvain@gallu.homelinux.org>
References: <CAMSKV5dobggNWAdCCu_DsN99MBkgE7kVP2PuwKKxCydVAgdKPQ@mail.gmail.com>
	<slrnjcrrii.9th.sylvain@gallu.homelinux.org>
Date: Thu, 24 Nov 2011 09:08:00 +0100
Message-ID: <CAP5QFJ=qw9jRf=iXEz1m1yQQDcEzYx1S6jiGxUSqn6kZsgEzNQ@mail.gmail.com>
From: Adrien <camaradetux@gmail.com>
To: Sylvain Le Gall <sylvain@le-gall.net>
Cc: caml-list@inria.fr
Content-Type: text/plain; charset=ISO-8859-1
Subject: Re: [Caml-list] Re: Issues with OCaml on Windows, MinGW build

Hi,

On 24/11/2011, Sylvain Le Gall <sylvain@le-gall.net> wrote:
> On 24-11-2011, Paul A. Steckler <steck@stecksoft.com> wrote:
>>
>>  - 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.
>>
>
> These one are bugs from oasis:
> https://forge.ocamlcore.org/tracker/index.php?func=detail&aid=941&group_id=54&atid=291
>
> I am working on it for the next version.
>
> Though, you should be warned that part of the compilation chain doesn't
> deal well with spaces in command. AFAIR, maybe something related to
> ocamlbuild and/or passing include paths for C library.
>

One solution is to put the ocaml toolchain somewhere else and set the
OCAMLLIB environment variable to the new PATH.
While you're at it, you can also use forward-slashes in paths: c:/foo/bar/baz.
This issues mostly happen with shell scripts and not programs which
have been made with greater care (actually they're probably the same
class of bugs as SQL injections).

Hope this helps.

Adrien Nader