caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Adrien <camaradetux@gmail.com>
To: Sylvain Le Gall <sylvain@le-gall.net>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Re: Issues with OCaml on Windows, MinGW build
Date: Thu, 24 Nov 2011 09:08:00 +0100	[thread overview]
Message-ID: <CAP5QFJ=qw9jRf=iXEz1m1yQQDcEzYx1S6jiGxUSqn6kZsgEzNQ@mail.gmail.com> (raw)
In-Reply-To: <slrnjcrrii.9th.sylvain@gallu.homelinux.org>

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

  reply	other threads:[~2011-11-24  8:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-24  6:25 [Caml-list] " Paul A. Steckler
2011-11-24  7:12 ` [Caml-list] " Sylvain Le Gall
2011-11-24  8:08   ` Adrien [this message]
2011-11-24  8:06 ` [Caml-list] " Török Edwin
2011-11-24  8:23 ` Jonathan Protzenko
2011-11-24 10:57 ` Dmitry Grebeniuk

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAP5QFJ=qw9jRf=iXEz1m1yQQDcEzYx1S6jiGxUSqn6kZsgEzNQ@mail.gmail.com' \
    --to=camaradetux@gmail.com \
    --cc=caml-list@inria.fr \
    --cc=sylvain@le-gall.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).