Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
Sender: cygwin-owner AT sourceware DOT cygnus DOT com
Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com
Message-ID: <009801be5f2e$6dc82480$29acdfd0@InspirePharm.Com>
From: "Suhaib M. Siddiqi" <Ssiddiqi AT InspirePharm DOT Com>
To: "Gary V. Vaughan" <gvaughan AT oranda DOT demon DOT co DOT uk>
Cc: <automake AT gnu DOT org>, "Sebastien Barre" <Sebastien DOT Barre AT utc DOT fr>,
        "cygwin" <cygwin AT sourceware DOT cygnus DOT com>
Subject: Re: [PB] "no acceptable ld" : cywin32 pb, way to handle win path ?
Date: Tue, 23 Feb 1999 08:14:22 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="Windows-1252"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.0810.800
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.0810.800



>>
>> If I remember correctly; Geoffrey Noer mentioned last month, that it
was
>> a Cgywin issue not automake.  Perhaps the problem will be fixed in
the
>> next release of Cygwin.
>>
>> Suhaib
>
>Yes,  the root of the problem is that 'gcc --print-prog-path=ld' gives
a
>win32 path (under cygwin), and I think it is this that the cygwin folks
>plan to fix.
>


Yes, you are correct.  That is what Geof also mentioned. For now
hard-coding the ld path
in configure scripts work.

Suhaib

>Cheers,
> Gary.
>


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com