tech-pkg archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: python and sqlite3 packages
On Apr 27, 2015, at 8:30 AM, Greg Troxel wrote:
> It would help to give more details.
Yes, it would, but I wasn't sure which details to even start with. Your points below help in that regard; thanks.
> Probably the issue is -L/-R for /usr/pkg not being ahead of the /usr
> ones in some link line. Probably it should be /usr/pkg first to prefer
> the pkgsrc stuff that it found. However that kind of change probably
> has unintended consequences so we should be careful.
>
> $ ldd /usr/pkg/lib/python2.7/lib-dynload/_sqlite3.so
> /usr/pkg/lib/python2.7/lib-dynload/_sqlite3.so:
> -lsqlite3.1 => /usr/lib/libsqlite3.so.1
> -lgcc_s.1 => /usr/lib/libgcc_s.so.1
> -lc.12 => /usr/lib/libc.so.12
> -lpython2.7.1.0 => /usr/pkg/lib/libpython2.7.so.1.0
> -lutil.7 => /usr/lib/libutil.so.7
> -lm.0 => /usr/lib/libm.so.0
> -lpthread.1 => /usr/lib/libpthread.so.1
My installation has pretty much the same paths. Clearly, the /usr/lib/libsqlite3.so.1 is the critical piece leading to my problem.
> This is perhaps not broken, because py-sqlite3 does not depend on the
> sqlite3 package. Perhaps you need PREFER_PKGSRC for that.
In fact, my (pretty recent cvs checkout of pkgsrc-2015Q1) databases/py-sqlite3/Makefile does include databases/sqlite3/buildlink3.mk. Thus, I would have expected it to depend on it, but pkg_info indicates that it does not; it only depends on python.
Thus, I'm still confused about the way forward. Why is the dependency not happening? Thanks for any help.
Cheers,
Brook
Home |
Main Index |
Thread Index |
Old Index