Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Date: Fri, 23 May 2003 07:18:22 -0700 From: Dario Alcocer To: cygwin@cygwin.com Subject: Re: Cygwin GCC linking Python extensions issue Message-ID: <20030523071822.C5309@ns.helixdigital.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: ; 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@helixdigital.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/