Summary: | dev-lisp/cl-sql-5.0.3 cannot load clsql_uffi.so | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Carlos Konstanski <ckonstanski> |
Component: | [OLD] Development | Assignee: | Common Lisp Bugs <common-lisp> |
Status: | RESOLVED WONTFIX | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 337963 |
Description
Carlos Konstanski
2010-02-12 16:24:31 UTC
clsql was updated to 5.0.4 this morning, and the bug remains. I am going to build clsql manually when I get the chance to see if the problem exists with the makefiles, or if it's the ebuild that is at fault. I tried a manual clsql installation. The file clsql_uffi64.so was properly built. I suspect the ebuild simply fails to copy the file to /usr/lib64/clsql/. This should be an easy fix. Just use the same methodology in src_install() as you use in install_clsql_pkg() for discovering all .so files to be copied. Or even use a kludge like: cp clsql_uffi*.so /usr/lib64/clsql/ I've included this fix in -r2, please try it OK, this is an improvement. Both clsql_uffi.so and clsql_uffi64.so make it into /usr/lib/clsql. But clsql_mysql.so fails because of this: ld -shared -soname=clsql_mysql clsql_mysql.o -L/lib32 -L/usr/lib32 -melf_i386 -lmysqlclient -lz -lc -o clsql_mysql.so ld: skipping incompatible /usr/lib/libmysqlclient.so when searching for -lmysqlclient ld: cannot find -lmysqlclient make: [clsql_mysql.so] Fehler 1 (ignoriert) Why are we looking for a 32 bit mysql build? This is bad; it'll never work on an amd64 system. It appears that this happens in the clsql makefile in db-mysql. Looks like the makefile tries to build both 64 and 32 bit libraries. The uffi makefile does this too. The difference is that the uffi makefile does not define LDFLAGS32 with "-L/lib32 -L/usr/lib32 -melf_i386", so the i386 build succeeds. Not sure why clsql builds 32 bit libraries on a 64 bit system anyway. At any rate, this looks like their bug, not yours. RESOLVED, WONTFIX. Package removed from the main tree. For more information, please see bug #337963 . |