On Thu, Feb 20, 2014 at 06:40:16PM -0500, Michael K. Johnson wrote: > Unfortunately, it looks like is built against the private > sqlite but linked against the system sqlite, and they are not > quite the same... > > Now working on fixing that.
Previously, conary had a soname dependency on libsqlite3.so.0 from the system. This was due to code in the conary recipe intended to support building against a private conary. The fix removed a -L that pushed system libraries to the front of the link list and thus system libsqlite showed up ahead of the internal sqlite. http://lists.foresightlinux.org/pipermail/fedora-import-commits/2014-February/000874.html $ conary rq conary=f20s1.flnx.org@f:20s-c/2.5.1-6-1[bootstrap] --deps | grep 'ELF64/libsqlite3' soname: ELF64/libsqlite3.so.0(SysV x86_64) $ conary rq conary=f20s1.flnx.org@f:20s-c/2.5.1-7-1[bootstrap] --deps | grep 'ELF64/libsqlite3' $ This resulted in a successful rmake build of acl! http://lists.foresightlinux.org/pipermail/fedora-import-commits/2014-February/000878.html That said, it's not clear that conary really needs to use an internal sqlite library any more. _______________________________________________ Foresight-devel mailing list [email protected] https://lists.foresightlinux.org/mailman/listinfo/foresight-devel
