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
From: Karl Robillard <krobillard AT cox DOT net>
To: cygwin AT cygwin DOT com
Subject: DLL vs. shared object linking behavior
Date: Sat, 3 Jan 2004 17:53:32 -0800
User-Agent: KMail/1.5.3
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200401031753.32396.krobillard@cox.net>

I have a shared library which has undefined references to functions.  On Linux 
I can build and use the library without problems, but when I build it as a 
DLL using Cygwin the undefined references are link errors.  Can the Windows 
loader handle unresolved symbols in DLLs at runtime?  Is there some magic 
compiler option I can use to allow this?


-Karl


--
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/