Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm Sender: cygwin-owner@sourceware.cygnus.com Delivered-To: mailing list cygwin@sourceware.cygnus.com Message-Id: <4.1.19990223071134.0170d1c0@mail.club-internet.fr> X-Sender: sbarre@mail.club-internet.fr X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Tue, 23 Feb 1999 07:12:22 +0100 To: "Suhaib M. Siddiqi" From: Sebastien Barre Subject: Re: no acceptable ld Cc: "Julian Kinraid" , "gnu-win32 mailing list" In-Reply-To: <000d01be5ece$7d491cd0$3768d1d0@hunda> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" At 20:47 22/02/99 -0500, Suhaib M. Siddiqi wrote: >>> At least for some configure scripts this has been the problem for not >>> recognizing ld in my experience. >> >>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. >> > >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. might be worth reporting the pb to the automake list ? ______________________________________________________________ Sebastien Barre http://www.hds.utc.fr/~barre/ -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe@sourceware.cygnus.com