caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: David Allsopp <dra-news@metastack.com>
To: "picflo_2@web.de" <picflo_2@web.de>,
	"caml-list@inria.fr" <caml-list@inria.fr>
Subject: RE: [Caml-list] Building OCaml 4.03.0 from source
Date: Wed, 27 Jul 2016 09:04:39 +0000	[thread overview]
Message-ID: <E51C5B015DBD1348A1D85763337FB6D9011EA7C962@Remus.metastack.local> (raw)
In-Reply-To: <trinity-e882fad3-6bab-4a8e-96b3-5ba39b70ebe8-1469609044437@3capp-webde-bs13>

[-- Attachment #1: Type: text/plain, Size: 2380 bytes --]

When I updated the documentation, I expected FlexDLL 0.35 would appear soon after the release of OCaml 4.03.0, but that hasn’t yet happened!

In order to build with Visual Studio 2015, you must recompile the FlexDLL objects from sources. You can either clone https://github.com/alainfrisch/flexdll.git and do make CHAINS=msvc support to get VC14 versions of flexdll_msvc.obj and flexdll_initer_msvc.obj (or CHAINS=msvc64 if you’re building the 64bit version) or you can follow the instructions for bootstrapping, which should be (the extra git checkout master pulls in the very latest FlexDLL, rather than the version tagged in 4.03.0, which is optional):

·        git clone https://github.com/ocaml/ocaml.git

·        cd ocaml

·        git checkout 4.03.0

·        git submodule update --init

·        cd flexdll

·        git checkout master

·        cd ..

·        do the usual stuff in config/

·        make -f Makefile.nt flexdll world world.opt install

I think you can build 4.03.0 with FlexDLL 0.34, the key thing is that you must build the support objects from sources. Off the top of my head, I can’t remember if I had to patch anything in flexlink for VS2015…


David

From: caml-list-request@inria.fr [mailto:caml-list-request@inria.fr] On Behalf Of picflo_2@web.de
Sent: 27 July 2016 09:44
To: caml-list@inria.fr
Subject: [Caml-list] Building OCaml 4.03.0 from source

Hi,

i am trying to build OCaml 4.03.0 from source on windows 7. At first i tried to build it with VC140, which
failed due to unresolved symbols, __iob_func and sprintf.The workaround mentioned in the mantis ticket 7263
didn't help. The quite recent comment there that it is a bug (of sorts) in FlexDLL sounded reasonable, but the
Flexdll verison 0.35 which is mentioned in the install readme for OCaml 4.03 does not exist on alain frisch github
page.
Compiling with VC110 worked fine except for the point where i tried to link my source files which were build with
different vc versions. This time the list of unresolved symbols is longer,
__iob_func
_environ
_vscprintf
_vsnprintf
fprintf
printf
sscanf

Should the new FlexDLL version fix the problem, so i can recompile everything with VC140? Has someone successfully
compiled OCaml 4.03 with VC140 on a windows 7 machine with flexdll 0.34?

Best regards,

Florian

[-- Attachment #2: Type: text/html, Size: 18274 bytes --]

      reply	other threads:[~2016-07-27  9:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-27  8:44 picflo_2
2016-07-27  9:04 ` David Allsopp [this message]

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=E51C5B015DBD1348A1D85763337FB6D9011EA7C962@Remus.metastack.local \
    --to=dra-news@metastack.com \
    --cc=caml-list@inria.fr \
    --cc=picflo_2@web.de \
    /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).