Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sourceware DOT cygnus DOT com Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com Message-ID: <20000126230512.29550.qmail@web118.yahoomail.com> Date: Wed, 26 Jan 2000 15:05:12 -0800 (PST) From: Earnie Boyd Reply-To: earnie_boyd AT yahoo DOT com Subject: RE: Linking problems To: Andre Oliveira da Costa , Cygwin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Note-from-DJ: This may be spam --- Andre Oliveira da Costa wrote: > (please refer to previous email for the explanation of the problem) > > Hi, > > making some more tests, I realized that some -L directives for the linker > were missing, and this obviously explains why the linker was unable to link > the application. But, the strange thing is: the linker does not spit any > warning like "cannot find symbol xxx (foo.c)". I'm not sure this is the > default behavior, but I'm sure I had this kind of output on my Linux box > (older version of gcc, though). > > Also, I cannot seem to be able to pass parameters directly to the linker via > the -Xlinker [param] scheme. It doesn't work with -Wl,[parm] either. > However, if I try to use the linker directly (i.e. "ld -o foo.exe ..." > instead of "gcc -o foo.exe ..."), I do see some reaction to parameters > like -M. It looks like gcc is ignoring it... Is anybody else also > experiencing this? > > (using gcc 2.95.2, ld 2.9.4, uname -a = "CYGWIN_NT-4.0 COSTA > 22.0(0.16/3/2) 1999-11-23 09:38:16 i586 unknown") > This is a known bug of your version of collect2. Regards, ===== Earnie Boyd Cygwin Newbies, please visit __________________________________________________ Do You Yahoo!? Talk to your friends online with Yahoo! Messenger. http://im.yahoo.com -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com