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: <42F2134E.59A5E50F@dessent.net> Date: Thu, 04 Aug 2005 06:08:30 -0700 From: Brian Dessent MIME-Version: 1.0 To: Cygwin-L Subject: Re: Trouble making .so (undefined symbols) References: <42F02793 DOT 8080109 AT etr-usa DOT com> <42F07A02 DOT 4040308 AT familiehaase DOT de> <42F20ACF DOT 8050309 AT etr-usa DOT com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Spam-Report: -5.5/5.0 ---- Start SpamAssassin results * -3.3 ALL_TRUSTED Did not pass through any untrusted hosts * -2.6 BAYES_00 BODY: Bayesian spam probability is 0 to 1% * [score: 0.0000] * 0.4 AWL AWL: From: address is in the auto white-list ---- End SpamAssassin results X-IsSubscribed: yes Reply-To: cygwin AT cygwin DOT com Warren Young wrote: > I would rather continue with my present scheme, which is using an import > library for the native build's DLL. This is, in effect, a "shared > libmysqlclient library", but I have a feeling that you mean a > Cygwin-built .so file instead. That's not a good idea. The MySQL native builds are going to be linked against MSVCRT. You can't combine MSVCRT and cygwin1.dll because they both provide differing and incompatible C runtime libraries. Just build a Cygwin libmysqlclient. It's not hard. There are 2 or 3 things you have to patch and they're all summarized by Gerrit in postings to this list. Brian -- 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/