Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
X-BigFish: VP
Date: Wed, 22 Dec 2004 14:54:56 -0700
From: Isaac Foraker <isaac DOT foraker AT xilinx DOT com>
Subject: Bug: link.exe
To: cygwin AT cygwin DOT com
Message-id: <41C9ED30.6000709@xilinx.com>
Organization: Xilinx, Inc.
MIME-version: 1.0
Content-type: text/plain; charset=ISO-8859-1; format=flowed
Content-transfer-encoding: 7BIT
User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206)
X-IsSubscribed: yes

The recent change of installing coreutils with `link.exe' has introduced 
a *new* problem with configurations using Microsoft Visual C++ with 
Cygwin's GNU `make'.  Previously, one could specify "LD=link" in a 
Makefile, but now the corutils `link' will supplant Microsoft's linker, 
breaking builds.  Specifying "LD=link" worked with all versions of 
Cygwin for at least the last two years, so this is a new problem.  Since 
developers tend to install their tools in different locations, but 
always have these tools in their path, using "LD=link" has always been 
acceptable.

The coreutils `link' appears to reproduce the hard-link functionality of 
`ln', and should probably not be a part of the base installation.

My temporary fix for my developers is to remove coreutils `link' from 
our systems, but if it is reinstalled every time coreutils is upgraded, 
this will cause an ongoing problem.

IF

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/