Summary: | mysql-cmake.eclass 1.19 version bump undid LDPATH adjustment done in version 1.16 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Gabriel Marcano <gabemarcano> |
Component: | Eclasses | Assignee: | Gentoo Linux MySQL bugs team <mysql-bugs> |
Status: | RESOLVED INVALID | ||
Severity: | normal | CC: | gabemarcano, kroemmelbein |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | Patch adding LDPATH changes removed in mysql-cmake.eclass revision 19. |
Description
Gabriel Marcano
2014-06-01 07:02:15 UTC
Created attachment 377974 [details, diff]
Patch adding LDPATH changes removed in mysql-cmake.eclass revision 19.
This change was intentional as other patches in dev-db/{mariadb,mysql} and the mysql-cmake.eclass moved most of the libraries to /usr/$(get_libdir). The one that was left in /usr/$(get_libdir)/mysql was the libmysqld.so. As jmbsvicetto has stated in bug 508824, this is an amarok problem and he will be taking care of this there. Forgive my ignorance, but how is Amarok being unable to find the path to the libmysqld.so library at runtime an Amarok problem? To my knowledge Amarok uses myslq_config to find the library in question at build-time, as it is my understanding that it should. In my system: # mysql_config --libmysqld-libs -L/usr/./lib64/mysql -lmysqld As things currently stand (I think), there is nothing in the system that would point any packages to this directory at runtime-- so while programs that need to compile against libmysqld.so may compile, they won't run since they won't be able to find the library. Well, this is assuming we don't configure RUNPATH for Amarok. Is this the solution, tweaking RUNPATH at build-time? On a related note, if almost all libraries were moved out of the myslq library folder, why was libmysqld left behind? Is there somewhere online where that discussion was had so that I may catch up on the reasoning? I appreciate the efforts of jmbsvicetto in bug 508824, and I realize this is probably a low priority, but I think this problem is within my abilities to solve, if I were to understand what the problem is. I fail to see Amarok being at fault-- if I run ldd in my system (after undoing my "fix") on the libraries Amarok compiles: # ldd /usr/lib64/kde4/amarok_collection-mysql* | grep mysql /usr/lib64/kde4/amarok_collection-mysqlecollection.so: libmysqld.so.18 => not found Please advise. |