Yaakov,
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.
I did some more investigation and I still don't see how you were able to
build this module without some kind of workaround. Empirically, I
determined that setup.py is trying to find one of the following files:
libsqlite3.dll
libsqlite3.dylib
libsqlite3.a
in typical library locations (e.g., /usr/lib).
However, sqlite3 only installs the following in /usr/lib:
libsqlite3.dll.a
libsqlite3.la
So, setup.py fails for me in exactly the same way as documented in the
above bug report.
I was able to (temporarily) workaround the problem with the following
hack:
$ ln -s libsqlite3.dll.a /usr/lib/libsqlite3.dll
Obviously, a better solution is to change setup.py to use the libraries
provided by sqlite3 directly. I will try to affect this change.
Any insight as to why your build is successful would be greatly
appreciated.
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/
