Mailing list for all users of the OCaml language and system.
 help / color / mirror / Atom feed
From: David Allsopp <dra-news@metastack.com>
To: Gerd Stolpmann <info@gerd-stolpmann.de>,
	"Soegtrop, Michael" <michael.soegtrop@intel.com>
Cc: "caml-list@inria.fr" <caml-list@inria.fr>
Subject: RE: [Caml-list] ocamlfind on mingw: .exe extensions missing in findlib.conf
Date: Sat, 24 Oct 2015 12:08:39 +0000	[thread overview]
Message-ID: <E51C5B015DBD1348A1D85763337FB6D9E9FB6D0D@Remus.metastack.local> (raw)
In-Reply-To: <1445686847.4567.73.camel@e130.lan.sumadev.de>

Gerd Stolpmann wrote:
> Am Samstag, den 24.10.2015, 10:21 +0000 schrieb Soegtrop, Michael:
> > Dear Ocaml users,
> >
> >
> >
> > I found that ocamlfind (findlib) builds fine for mingw on Cygwin, but
> > it doesn’t work. The issue is that the .exe extensions are missing in
> > the findlib.conf file. This has the effect that most calls to
> > ocamlfind end up in an error message like:
> >
> > $ ocamlfind ocamlc
> >
> > Uncaught exception: Unix.Unix_error(20, "create_process",
> > "ocamlc.opt")
> 
> This is surprising. Windows used to add .exe if missing, so far the
> command is looked up via PATH (see https://msdn.microsoft.com/en-
> us/library/windows/desktop/ms682425(v=vs.85).aspx but I admit this page is
> highly confusing).

I'm not sure it would ever have added it to ocamlc.opt? The .opt extension I think would have always prevented CreateProcess from trying ocamlc.opt.exe.


David 

  reply	other threads:[~2015-10-24 12:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-24 10:21 Soegtrop, Michael
2015-10-24 11:40 ` Gerd Stolpmann
2015-10-24 12:08   ` David Allsopp [this message]
2015-10-24 11:46 ` David Allsopp
2015-10-25 12:51   ` Gerd Stolpmann
2015-10-26  8:57     ` Soegtrop, Michael

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=E51C5B015DBD1348A1D85763337FB6D9E9FB6D0D@Remus.metastack.local \
    --to=dra-news@metastack.com \
    --cc=caml-list@inria.fr \
    --cc=info@gerd-stolpmann.de \
    --cc=michael.soegtrop@intel.com \
    /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