Subject: Re: no acceptable ld
From: "Suhaib M. Siddiqi" <[email-masked]>
To: "Stipe Tolj" <[email-masked]>, "Alex" <[email-masked]>
Cc: "gnu-win32 mailing list" <[email-masked]>
Date: Mon, 22 Feb 1999 20:44:07 -0500

This problem also occurs with LessTif and many other codes.  It is because
Cygwin has a different style.

I usually search the configure script for something like "LD="$...." and
replace all those occurances with
LD="/usr/cygwin-b20/H-i586-cywgin32/bin/ld.exe"  This hard codes the ld.exe
path and also include at your ./configure --with-gnu-ld if this option is
available (check with ./configure --help).  Hard coding ld.exe path in
configure script always has worked at least in my hands.

-----Original Message-----
From: Stipe Tolj <[email-masked]>
To: Alex <[email-masked]>
Cc: gnu-win32 mailing list <[email-masked]>
Date: Monday, February 22, 1999 5:59 PM
Subject: Re: no acceptable ld

>> i tried to compile CILK ( http://supertech.lcs.mit.edu/cilk/ )
>> and i got this error message:
>>
>> checking for ld used by GCC... no
>> configure: error: no acceptable ld found in $PATH
>>
>> though ld.exe is in the bin directory, what can i do to solve this
>> problem ?
>
>check out the configure script itself where the test is performed, i.e.
>search for "checking for ld used by" and you may see that you'll need to
>add Win32 path style to match certain conditions within the configure
>script so ld is recognized.
>
>At least for some configure scripts this has been the problem for not
>recognizing ld in my experience.
>
>Hope this helps.
>
>Regards,
>Stipe
>
>--
>Stipe Tolj <[email-masked]>
>
>Cygwin Porting Project -- "We build UNIX on top of Windows"
>http://www.student.uni-koeln.de/cygwin/
>
>Department of Economical Computer Science
>University of Cologne, Germany
>
>
>
>
>--
>Want to unsubscribe from this list?
>Send a message to [email-masked]
>
>

--
Want to unsubscribe from this list?
Send a message to [email-masked]