From: Dmitry Bely <dmitry.bely@gmail.com>
To: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] Statically linked win32 libcamlrun.lib?
Date: Fri, 16 Apr 2010 00:06:03 +0400 [thread overview]
Message-ID: <z2x90823c941004151306jf936f97fk9ba089539d3c1913@mail.gmail.com> (raw)
In-Reply-To: <u2r3b3449e01004151216td66901f1y569c1c9347dd3ede@mail.gmail.com>
On Thu, Apr 15, 2010 at 11:16 PM, Lally Singh <lally.singh@gmail.com> wrote:
> On Thu, Apr 15, 2010 at 2:59 AM, Dmitry Bely <dmitry.bely@gmail.com> wrote:
>> On Thu, Apr 15, 2010 at 3:39 AM, Lally Singh <lally.singh@gmail.com> wrote:
>>
>>> Is it possible to statically link libcamlrun.lib, so it'll work with
>>> libcmtd.lib instead of msvcrt.dll? I've tried:
>>>
>>> FLEXLINK=flexlink -merge-manifest -link /nodefaultlib:msvcrt.lib -link
>>> libcmtd.lib
>>
>> Please don't use "brute force" methods. If you need statically linked
>> MSVC runtime, just replace /MD with /MT (or /MTd) in config/Makefile.
>
> Thanks, I've tried this instead, and I can't get through make -f
> Makefile.nt bootstrap without:
> ../../boot/ocamlrun ../../ocamlc -nostdlib -I ../../stdlib -w s -c
> -warn-error A -g -I ../win32unix bigarray.mli
> File "bigarray.mli", line 384, characters 4-19:
> Error: Unbound type constructor Unix.file_descr
> make[2]: *** [bigarray.cmi] Error 2
>
> I guess using the flexlink hack just moved whatever underlying problem
> I'm having to a later stage.
Why boostrap? Does simple "make -f Makefile.nt world" succeeds? Please
use the clean distribution with minimal changes in config/Makefile; I
suspect you have already broken something during your experiments.
- Dmitry Bely
next prev parent reply other threads:[~2010-04-15 20:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-14 23:39 Lally Singh
2010-04-15 6:59 ` [Caml-list] " Dmitry Bely
2010-04-15 19:16 ` Lally Singh
2010-04-15 20:06 ` Dmitry Bely [this message]
2010-04-15 20:16 ` Dmitry Bely
2010-04-20 15:48 ` Lally Singh
2010-04-20 16:31 ` Dmitry Bely
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=z2x90823c941004151306jf936f97fk9ba089539d3c1913@mail.gmail.com \
--to=dmitry.bely@gmail.com \
--cc=caml-list@yquem.inria.fr \
/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).