From: Alain Frisch <alain.frisch@lexifi.com>
To: David Allsopp <dra-news@metastack.com>, OCaml List <caml-list@inria.fr>
Subject: Re: [Caml-list] Building MSVC ports: coreutils link conflict
Date: Fri, 17 Jul 2015 19:12:06 +0200 [thread overview]
Message-ID: <55A93766.9000503@lexifi.com> (raw)
In-Reply-To: <E51C5B015DBD1348A1D85763337FB6D9E9D1D91F@Remus.metastack.local>
On 07/17/2015 05:42 PM, David Allsopp wrote:
> would a patch to the compiler (and to flexlink)
The compiler doesn't often call "link.exe" directly. As far as I can
tell, it does it only in case of partial linking to support module
packing in native code. And ocamlmklib can create static libraries by
calling the linker directly. I'm wondering whether it would be a good
occasion to tell flexlink how to do these two operations (for all
supported toolchains), so that ocaml itself doesn't ever talk to the
linker directly anymore, but only through flexlink. This would mean
that the logic to find the correct link.exe would only be in flexlink.
Do you think it would be a good idea?
Alain
next prev parent reply other threads:[~2015-07-17 17:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-14 16:28 David Allsopp
2015-07-15 11:40 ` Alain Frisch
2015-07-17 15:42 ` David Allsopp
2015-07-17 17:12 ` Alain Frisch [this message]
2015-07-22 16:23 ` Damien Doligez
2015-07-22 16:34 ` David Allsopp
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=55A93766.9000503@lexifi.com \
--to=alain.frisch@lexifi.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;
as well as URLs for NNTP newsgroup(s).