From: "David Allsopp" <dra-news@metastack.com>
To: "OCaml List" <caml-list@inria.fr>
Subject: [Caml-list] Building MSVC ports: coreutils link conflict
Date: Tue, 14 Jul 2015 17:28:38 +0100 [thread overview]
Message-ID: <003401d0be52$320d6a00$96283e00$@metastack.com> (raw)
It's a while since I've last needed to build the MSVC port of OCaml, but
this issue rang some vague bells in my memory of it.
The Microsoft Linker is called link.exe which, annoyingly, is also the name
of a coreutils utility. When building OCaml (from bash, therefore), if
/usr/bin is in PATH before the Microsoft C Compiler's Bin directory, OCaml
will attempt to use the wrong link and choke.
As far as I'm aware, when started in the usual way as a login shell,
Cygwin's bash will always prefix PATH /usr/local/bin:/usr/bin:$PATH ... so I
was surprised to find no mention of this issue in the build instructions -
is it simply that everyone who builds the MSVC port just curses at this
point, alters their PATH and carries on, or is there an alternate, better
way of setting up the build environment?
David
next reply other threads:[~2015-07-14 16:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-14 16:28 David Allsopp [this message]
2015-07-15 11:40 ` Alain Frisch
2015-07-17 15:42 ` David Allsopp
2015-07-17 17:12 ` Alain Frisch
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='003401d0be52$320d6a00$96283e00$@metastack.com' \
--to=dra-news@metastack.com \
--cc=caml-list@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