On 20.07.2008 17:13 CE(S)T, Stephen Gran wrote:
> On Sun, Jul 20, 2008 at 12:14:27PM +0200, Yves Goergen said:
>> Yet I don't know why Exim is the only application that has this problem.
>> ProFTPd for example also links to the same MySQL client library and
>> still runs without the ld.so.conf change. Yet other applications
>> (courier-authlib) find and use the MySQL client library entirely alone
>> without anybody telling them where to find it. Do they know where to
>> find the library when MySQL is installed from source? Are they able to
>> tell ld at runtime (or compile time) from where to link the shared
>> library file and Exim is not? Should that be changed?
>
> objdump -x /path/to/binary | grep RPATH
>
> It's frequently the case for autoconf-built applications that libtool
> 'helpfuly' adds an rpath when you have libraries outside of standard
> search paths. I personally dislike rpath, as it makes it harder to
> relocate libraries later, but YMMV.
I see.
Exim doesn't have an RPATH line.
ProFTPd and PHP have one that points to where the library is. As I see
from my configure arguments for them, I have at least pointed them in
the right direction, if not to the exact directory where to find the
library. Seems I didn't compile Exim for a very long time and some
things have changed in the system since then... ;)
Courier's authdaemond even points to its own directory where it has some
kind of copy of a MySQL client library
(/usr/courier/lib/courier-authlib/libauthmysql.so). This could explain
why it requires no sort of indication where to find the "official"
installed libmysqlclient.
Thanks for the explanation.
--
Yves Goergen "LonelyPixel" <nospam.list@???>
Visit my web laboratory at
http://beta.unclassified.de
