Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Date: Fri, 23 May 2003 07:18:22 -0700
From: Dario Alcocer <alcocer AT helixdigital DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: Cygwin GCC linking Python extensions issue
Message-ID: <20030523071822.C5309@ns.helixdigital.com>
References: <u7k8hojup DOT fsf AT boost-consulting DOT com> <Pine DOT GSO DOT 4 DOT 44 DOT 0305230954200 DOT 26092-100000 AT slinky DOT cs DOT nyu DOT edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <Pine.GSO.4.44.0305230954200.26092-100000@slinky.cs.nyu.edu>; from pechtcha@cs.nyu.edu on Fri, May 23, 2003 at 09:55:46AM -0400

On Fri, May 23, 2003 at 09:55:46AM -0400, Igor Pechtchanski wrote:
> Isn't there a --verbose option to the linker that tells you where it's
> getting the symbols from?

I know if you generate a map file (-Wl,-M) on a successful link, you'll
see this information. This might work when the link is incomplete.

The other thing to try is to dump out the symbols in your object files
using nm(1). You'll have more data to sift through, but it should
provide the answers the original poster was after.

-- 
Dario Alcocer -- Sr. Software Developer, Helix Digital Inc.
alcocer AT helixdigital DOT com -- http://www.helixdigital.com

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/