From: "Soegtrop, Michael" <michael.soegtrop@intel.com>
To: David Allsopp <dra-news@metastack.com>,
"caml-list@inria.fr" <caml-list@inria.fr>
Subject: [Caml-list] Flexdll circular dependency fix uses system provided flexdll.h [was: opam-cross-windows]
Date: Sat, 25 Jun 2016 14:09:49 +0000 [thread overview]
Message-ID: <0F7D3B1B3C4B894D824F5B822E3E5A172CF1B3BA@IRSMSX102.ger.corp.intel.com> (raw)
Dear David,
I just managed now to test the flexdll dependency fix in 4.03.0 you mentioned in your post from March 15th:
> 1. Ensure FlexDLL sources are in flexdll/ in the OCaml build tree
> 1a. If you're building from a git clone, issue git submodule update --init
> 1b. If you're building from a sources tarball, issue git clone > https://github.com/alainfrisch/flexdll.git
> 2. Follow usual configuration steps in config/
> 3. make -f Makefile.nt flexdll world opt opt.opt install
It is much better than it was, but I think there is still a minor flaw in it. When compiling byterun/win32.c (from asmrun) in the make opt phase, it doesn't find flexdll.h because gcc doesn't have an -I ../flexdll. If I copy flexdll.h to a system include directory it works fine. Is it possible that you had a flexdll.h somewhere and the build took it from there rather than from the flexdll subfolder when you tried this?
Also I think specific versions of OCaml should copy specific versions of flexdll. A git clone of the trunk version might lead to unexpected effects in the future and it might be hard to reconstruct older OCaml versions later.
Best regards,
Michael
Intel Deutschland GmbH
Registered Address: Am Campeon 10-12, 85579 Neubiberg, Germany
Tel: +49 89 99 8853-0, www.intel.de
Managing Directors: Christin Eisenschmid, Christian Lamprechter
Chairperson of the Supervisory Board: Nicole Lau
Registered Office: Munich
Commercial Register: Amtsgericht Muenchen HRB 186928
next reply other threads:[~2016-06-25 14:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-25 14:09 Soegtrop, Michael [this message]
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
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=0F7D3B1B3C4B894D824F5B822E3E5A172CF1B3BA@IRSMSX102.ger.corp.intel.com \
--to=michael.soegtrop@intel.com \
--cc=caml-list@inria.fr \
--cc=dra-news@metastack.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