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 Message-ID: <00ef01c46443$b813fa80$5308a8c0@robinson.cam.ac.uk> From: "Max Bowsher" To: "Dave Korn" Cc: "'Cygwin List'" References: Subject: Re: Building DLL Date: Wed, 7 Jul 2004 17:59:03 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Dave Korn wrote: >> -----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? No. -no-undefined is what is required here, and it is a libtool flag, not a ld flag. Windows simply doesn't allow for undefined symbols in shlibs, and there is nothing ld can do about it. Max. -- 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/