Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , 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: "Dave Korn" Cc: "'Cygwin List'" Subject: RE: Building DLL Date: Wed, 7 Jul 2004 17:55:07 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit In-Reply-To: <441249594902.20040707183519@familiehaase.de> Message-ID: X-OriginalArrivalTime: 07 Jul 2004 16:55:07.0218 (UTC) FILETIME=[2822EB20:01C46443] > -----Original Message----- > From: cygwin-owner On Behalf Of Gerrit P. Haase > Sent: 07 July 2004 17:35 > Maarten wrote: > which needs to > > be built as a shared library. Dbh uses libtool in its build process. > > > Of course this complains with > > > libtool: link: warning: undefined symbols not allowed in > > i686-pc-cygwin shared libraries > > > As far as I know, to get this to build I need to create a > .def file, and > > somehow include this in the libtool invocation. > > > Are there some general hints to determine which > functions/symbols need > > to be included in this .def file, and how to modify the libtool > > invocation to use this file? > > You don't need .def files on Cygwin. Just add -no-undefined to > libxyz_LDFLAGS. Do you perhaps mean "--allow-shlib-undefined"? A quick glance at the ld --help output suggests that's more like what's needed, isn't it? cheers, DaveK -- Can't think of a witty .sigline today.... -- 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/