Yaakov,
On Tue, Sep 09, 2008 at 09:24:29AM -0400, Jason Tishler wrote:
> On Tue, Aug 26, 2008 at 08:04:02PM -0400, Jason Tishler wrote:
> > On Fri, Aug 08, 2008 at 05:23:37PM -0500, Yaakov (Cygwin Ports) wrote:
> > > Jason Tishler wrote:
> > > | Since the following is still open:
> > > |
> > > | http://bugs.python.org/issue1706863
> > > |
> > > | I didn't realize that this problem was resolved in Python 2.5.2.
> > >
> > > Actually, it was working with 2.5.1 also, so it must have been
> > > something else.
> >
> > OK, I'll try again.
>
> [snip]
> Any insight as to why your build is successful would be greatly
> appreciated.
I believe I figured out why your build was successful. You built
against a sqlite3 that provided a static library (i.e., libsqlite3.a):
$ tar -tvjf libsqlite3-devel-3.5.9-1.tar.bz2 | fgrep usr/lib/libsqlite3
-rw-r--r-- Yaakov/None 403280 2008-05-22 00:52 usr/lib/libsqlite3.a
-rwxr-xr-x Yaakov/None 102334 2008-05-22 00:52 usr/lib/libsqlite3.dll.a
-rwxr-xr-x Yaakov/None 909 2008-05-22 00:52 usr/lib/libsqlite3.la
So, now we have two approaches to solve this problem:
1. release a sqlite3 with a static library
2. change Python to build against the import library
Does sqlite3 have a maintainer? If so, then please release a new
package with the static library included. This is an easy, short term
fix that can be used, while I pursue the other (harder, more long term)
approach.
Thanks,
Jason
--
PGP/GPG Key: http://www.tishler.net/jason/pubkey.asc or key servers
Fingerprint: 7A73 1405 7F2B E669 C19D 8784 1AFD E4CC ECF4 8EF6
--
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/
