caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: David Allsopp <dra-news@metastack.com>
To: "Soegtrop, Michael" <michael.soegtrop@intel.com>,
	"caml-list@inria.fr" <caml-list@inria.fr>
Subject: RE: [Caml-list] Flexdll circular dependency fix uses system provided flexdll.h [was: opam-cross-windows]
Date: Sun, 26 Jun 2016 18:04:01 +0000	[thread overview]
Message-ID: <E51C5B015DBD1348A1D85763337FB6D9F065EE3B@Remus.metastack.local> (raw)
In-Reply-To: <0F7D3B1B3C4B894D824F5B822E3E5A172CF1B5FB@IRSMSX102.ger.corp.intel.com>

Michael Soegtrop wrote:
> > This isn't a great way - better is to override the detection of
> > FLEXDIR a few lines later (the FLEXDIR:= line):
> 
> > sed -I "s|FLEXDIR:=.*|FLEXDIR=|" config/Makefile
> 
> I thought about this, but I wonder if this would use the correct
> flexdll.h, but still the wrong flexlink. I thought it would be safer to
> point it to the right flexlink and derive the flexdll.h location from
> there.

If it's working correctly, each individual Makefile.nt selects flexlink based on the presence of flexdll/Makefile (e.g. https://github.com/ocaml/ocaml/blob/trunk/Makefile.nt#L24-L30). I think what's happened here is a piece of laziness/regression, because it's hard for config/Makefile to know what level it's been included at (the use of ROOTDIR, for example in https://github.com/ocaml/ocaml/blob/trunk/otherlibs/Makefile#L18, is not consistent across the entire build tree).

However, I was going to verify that it never picks up the wrong one by putting a dummy flexlink.exe into PATH which simply does `exit 2`.

> The mingw cross compiler + standard library builds fine, but then when I
> use it, it doesn't find pervasives, although the pervasives.cmx is in the
> folder ocamlc -config says it should be. I guess something went wrong with
> the flexlink process. Is there some way to see from ocamlc - config if
> flexlink support is there? Or is there another way to check if flexlink is
> the problem?

They should be identical, but possibly worth checking ocamlopt -config, rather than ocamlc -config. Being unable to find a .cmx is unlikely to be a flexlink problem (flexlink handles .o files, not .cmx).

Running ocamlopt -verbose allows you to see the flexlink command invocation and, IIRC, adding -ccopt -v should cause flexlink to display the commands it's running too.


David


  reply	other threads:[~2016-06-26 18:04 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-25 14:09 Soegtrop, Michael
2016-06-25 16:13 ` David Allsopp
2016-06-25 16:31   ` Soegtrop, Michael
2016-06-25 16:52     ` David Allsopp
2016-06-25 18:13       ` Soegtrop, Michael
2016-06-25 18:35         ` David Allsopp
2016-06-26 12:57           ` Soegtrop, Michael
2016-06-26 15:17             ` David Allsopp
2016-06-26 17:26               ` Soegtrop, Michael
2016-06-26 18:04                 ` David Allsopp [this message]
2016-06-27 11:15                   ` Soegtrop, Michael
2016-06-27 11:26                     ` David Allsopp
2016-06-27 12:01                       ` 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=E51C5B015DBD1348A1D85763337FB6D9F065EE3B@Remus.metastack.local \
    --to=dra-news@metastack.com \
    --cc=caml-list@inria.fr \
    --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;
as well as URLs for NNTP newsgroup(s).