Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sourceware DOT cygnus DOT com>
List-Archive: <http://sourceware.cygnus.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sourceware DOT cygnus DOT com>
List-Help: <mailto:cygwin-help AT sourceware DOT cygnus DOT com>, <http://sourceware.cygnus.com/ml/#faqs>
Sender: cygwin-owner AT sourceware DOT cygnus DOT com
Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com
From: "Andre Oliveira da Costa" <costa AT cade DOT com DOT br>
To: "Richard Stanton" <stanton AT Haas DOT Berkeley DOT EDU>,
        <cygwin AT sourceware DOT cygnus DOT com>
Subject: RE: gcc - no messages re unresolved symbols
Date: Thu, 24 Feb 2000 13:04:25 -0300
Message-ID: <000301bf7ee0$d2185f90$8400000a@costa.cadenet.com.br>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0
Importance: Normal
In-Reply-To: <000a01bf7e60$a5f2dba0$524b2080@berkeley.edu>
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4

Hi Richard,

this matter was discussed on the list some time ago. Apparently there's a
problem with collect2.exe that makes it swallow any error output from the
linker and don't send it back to stderr. I had this same problem, and the
gurus gave me a couple of suggestions:

[1] rename collect2.exe to something else (e.g. _ collect2.exe) - OR -
[2] edit the specs file of gcc and change the line that refers to collect2
so that it refers to ld directly

I went for option [2]. I'm not fully aware of the consequences of that
(performance loss, maybe?), but seemed more like TheRightThing (TM) to do.
Anyway, things are working ok for me now. My installation is a snapshot of
19991123, so there might be a chance that this has already been fixed on
recent snapshots. Can anybody confirm that?

(OBS.: collect2.exe and the specs file are on
/cygnus/cygwin-b20/H-i586-cygwin32/lib/gcc-lib/i586-cygwin32/2.95.2 on my
system)

HTH.

Regards,

Andre
--
André Oliveira da Costa
(costa AT cade DOT com DOT br)


> -----Original Message-----
> From: cygwin-owner AT sourceware DOT cygnus DOT com
> [mailto:cygwin-owner AT sourceware DOT cygnus DOT com]On Behalf Of Richard Stanton
> Sent: Wednesday, February 23, 2000 9:47 PM
> To: cygwin AT sourceware DOT cygnus DOT com
> Subject: gcc - no messages re unresolved symbols
>
>
> I'm having an odd problem with gcc (cygwin version 2.95) on my NT machine.
> If I compile/link a program that has some unresolved symbols, the linker
> doesn't tell me about them, which makes tracking them down more than a
> little hard...
>
> For example, here's what happens when I compile a program that
> has a missing
> main():
>
> [c:\miscprog]gcc -o amput amput.c
> collect2: ld returned 1 exit status
>
> For comparison, here's what happens when I do the same thing on a unix
> (SunOS 5.6) machine:
>
> socrates% gcc -o ttt amput.c -lm
> Undefined                       first referenced
>  symbol                             in file
> main
> /usr/local/egcs-1.1.2/lib/gcc-lib/sparc-su
> solaris2.6/egcs-2.91.66/crt1.o
> ld: fatal: Symbol referencing errors. No output written to ttt
> collect2: ld returned 1 exit status
> socrates%
>
> Any idea what's wrong? I'm pretty sure this used to work at one point.
>
> Thanks a lot for any suggestions.
>
> Richard Stanton
>
>
> --
> Want to unsubscribe from this list?
> Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com
>


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