Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Unsubscribe: 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 Reply-To: From: "Nicholas Codignotto" To: Subject: Shared Libraries Date: Sat, 13 Nov 1999 17:09:38 -0500 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) Importance: Normal In-Reply-To: <382DDDA3.D84AB37E@wanadoo.fr> X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 I've been told that shared libraries under unix can be built with unresolved externals. Thus, if I were to build a shared library with gcc under a unix/cygwin system, I would not need a stub library file containing the routines that I call within my library. The vendor have me a header file and a Win32 library file (.lib) and nothing else. The vendor states that under UNIX, no lib is needed. I can't figure out how to correctly link my shared library as gcc under cygwin still returns an "unresolved reference error". I have a vendor-provided header (vendor.h) defining some structures and functions. I compile my program like so: gcc -c my_module.c -o my_module.o gcc -shared -o my_module.so my_module.o I then get an "unresolved reference" error for each function defined in vendor.h that I call in my_module.c. Thanks (in advance) a MILLION for any help! Nick -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com