From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Original-To: caml-list@sympa.inria.fr Delivered-To: caml-list@sympa.inria.fr Received: from mail2-relais-roc.national.inria.fr (mail2-relais-roc.national.inria.fr [192.134.164.83]) by sympa.inria.fr (Postfix) with ESMTPS id E6C327EEBF for ; Wed, 22 Jul 2015 18:23:27 +0200 (CEST) X-IronPort-AV: E=Sophos;i="5.15,523,1432591200"; d="scan'208";a="171264590" Received: from ec-ap-2-13-07.rocq.inria.fr (HELO [192.168.1.3]) ([128.93.40.21]) by mail2-relais-roc.national.inria.fr with ESMTP/TLS/AES128-SHA; 22 Jul 2015 18:23:27 +0200 Mime-Version: 1.0 (Apple Message framework v1283) Content-Type: text/plain; charset=us-ascii From: Damien Doligez In-Reply-To: Date: Wed, 22 Jul 2015 18:23:26 +0200 Cc: OCaml List Content-Transfer-Encoding: quoted-printable Message-Id: <9D19EF28-A045-4F63-961C-E1EEAEA6ACB0@inria.fr> References: <003401d0be52$320d6a00$96283e00$@metastack.com> <55A646CA.8050605@lexifi.com> To: David Allsopp X-Mailer: Apple Mail (2.1283) Subject: Re: [Caml-list] Building MSVC ports: coreutils link conflict On 2015-07-17, at 17:42, David Allsopp wrote: > Given that this conflict is only over link.exe - all the other tools in t= he Microsoft toolchain are sensibly, or at least moderately uniquely, named= - would a patch to the compiler (and to flexlink) which searches the vario= us directories in PATH in order and identifies the first link.exe which is = actually a Microsoft Linker be welcomed (i.e. merged) - an ML-equivalent to= [1], but only used if the linker has been specified given as "link" (i.e. = with no directory)? I'm happy to patch it, but only if it would be wanted. = I don't see a case for doing it for other commands, but with a conflict in = something in coreutils it seems OK to make an exception, at least to me? Yuck. IMO it would be better to add a configure-time option to give the abs= olute path to the link executable. In the meantime, what you can do is: - create an empty directory (for example, /usr/local/bin/ms-tools) - put a copy of (or a symlink to) Microsoft's link.exe into it - add it in front of your path -- Damien