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: <4.1.19990223073206.0175a7d0@mail.club-internet.fr>
X-Sender: sbarre AT mail DOT club-internet DOT fr
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1
Date: Tue, 23 Feb 1999 07:41:04 +0100
To: automake AT gnu DOT org
From: Sebastien Barre <Sebastien DOT Barre AT utc DOT fr>
Subject: [PB] "no acceptable ld" : cywin32 pb, way to handle win path ?
Cc: cygwin AT sourceware DOT cygnus DOT com
In-Reply-To: <d9btilixqo.fsf@han.cs.umn.edu>
References: <Bob Friesenhahn's message of "Mon, 22 Feb 1999 21:28:12 -0600 (CST)">
 <Pine DOT SO4 DOT 4 DOT 05 DOT 9902222125010 DOT 25431-100000 AT scooby DOT simple DOT dallas DOT tx DOT us>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"

Here are some excerpts of a problem discussed in the cywin32 mailing list.
I thought it might be interesting for the automake people too (this message
is also crossposted CC: to the cywin32 list for information).

http://www.cygnus.com/ml/gnu-win32/
http://sourceware.cygnus.com/ml/cygwin/1999-02/msg00702.html

It seems related to the way configure script handles path (many of use
encoutered the pb with different configure scripts) :

 Alex <alexl AT i-france DOT com> :

>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 ?


Tolj <tolj AT uni-duesseldorf DOT de> :

>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.


Julian Kinraid <jkinraid AT clear DOT net DOT nz>

>I had the same problem, but if you just set the LD enviroment variable,
>you mightn't need to change the configure script -
>
>export LD=/cygwin/cygwin-b20/H-i586-cygwin32/bin/ld.exe
>
>Just make sure the path is correct.


"Suhaib M. Siddiqi" <Ssiddiqi AT InspirePharm DOT Com> :

>>export LD=/cygwin/cygwin-b20/H-i586-cygwin32/bin/ld.exe
>>
>>Just make sure the path is correct.
>>
>
>Theoretically it supposed to work.  But; it does not awlays by doing
>export... before using configure script.  Many Configure scripts apprantly
>ignore it and seach for LD="$..." whatever.  Hardcoding the ld.exe path in
>configure works at least always in my hands.


"Suhaib M. Siddiqi" <Ssiddiqi AT InspirePharm DOT Com> :

>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.


Any help frop the automake people would be really appreciated, sorry if it
has been discussed before...

Thanks a lot


______________________________________________________________
Sebastien Barre                  http://www.hds.utc.fr/~barre/

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